
This market is conditional on my deploying the thing at all. So it resolves to "yes" if we deploy it universally, "no" if we deploy it only to a limited number of people and then decide not to expand it to everyone, and "N/A" if we don't deploy it at all.
I had an idea: I live in my Beeminder dashboard all day, and I want the goals to update more often to keep in sync with the server and get new data that's come in from other sources. I'm going to add a refresh to the toggle function so that when you expand a goal we check the server for any updates. Seems like a nice compromise to user-me, so it's only changing stuff when I tell it to, but there's an easy way to freshen the goal without reloading the whole page. Also I don't have to put in a new/separate button somewhere, and there's a certain logic to it, as expanding the goal is an explicit interaction with that goal, so seems like a good time to refresh it.
It's possible, however, that some people will virulently hate this, or that it turns out to be frustrating when you're rushing to enter data as a deadline approaches or something, and we won't like it afterall. Or, also possible that we don't deploy it all.
🏅 Top traders
# | Name | Total profit |
---|---|---|
1 | Ṁ123 | |
2 | Ṁ112 | |
3 | Ṁ20 | |
4 | Ṁ3 |
Conclusion: Bee liked it as a user, Danny didn't. Also a user (I'm forgetting who now) pointed out that when you expand the goal and the infinibee is buzzing, ie, indicating that it's refreshing the goal, it feels like you need to wait for it to finish before entering data. You don't but it feels like you do.
So we decided it wasn't deployable the way Bee liked it.
Then I had the idea that we could make double-click trigger a refresh. That's dumb in that it's totally undiscoverable, but also zero downside. No one will bump into it and be annoyed by it. Basically it's an easter egg. So that version is deployed and some tiny number of users find it handy.
The right answer is probably to add a new explicit button.