New App - Beeminder Widgets for iOS

[sahl]

I made a free app to show Beeminder goals on the home screen. You can also press a button to add +1 to a goal.

‎Beeloved

[krugerk]

Congratulations on the release and thanks for sharing!

[dustinglendinning]

Very cool! Thanks!

I’m probably doing something wrong, but it’s not able to find my data. “Failed to fetch graph” is all it shows. I put in my credentials fine and I can pick my account when editing the widget but I can’t pick my goals, I’m just typing them in; do I need the slash before the name or is it the whole URL? Thanks

[dustinglendinning]

Got it, sorry. Didn’t realize my username was different from my login, and that the x next to the account names in the app meant the connection wasn’t working, thought it was an x to remove that account.

Thanks again!

[sahl]

Next build I’ll make it more clear. I appreciate the feedback!

[aad]

Thanks for this!

I also experienced the confusion about x around next to the account name.

Although I have it configured and running well, I frequently see an error message: “couldn’t fetch the graph.” Let me know if I can help troubleshoot!

[sahl]

I currently don’t cache old graphs, so when I make a request for a new graph and it fails, I display that error directly. Are you on an unstable internet connection? If you go to the app and refresh it, then come back out, can you see the graph again?

[aad]

Yeah if I open the app then they load with a small delay, feels like low priority networking by the system.

I find it unlikely that unstable connection the culprit is. I’m mostly on high quality wireless or on medium quality 5G (somewhat slow but good coverage and otherwise no noticeable lag in internet use),

[philip]

For those who typed ‘beeloved’ into the app store and were deluged with dating apps, here’s a direct link: ‎Beeloved on the App Store (because I apparently missed seeing the prominent link that sahl posted originally!)

[sahl]

I’m not sure why the widget is failing to request the graph from the API, the solution I could think of is caching graph (and maybe showing an icon meaning “not up to date”). I’ll do that next build.