I agree completely (I wrote the app). The next version will be much more user friendly in the install/signup stage. Timing the app approval/launch was the issue that prevented it at initial release.
There is like a big list of minor annoyances. For example I get multiple notifications, but when I start the app there is nothing shown in the notification center till you pull the top down and release it. That's a bit counter-intuitive. If I were you I'd get someone on odesk for $30 an hour to rework the client while you focus on marketing your business and developing the backend.
notifications are auto-fetched when you open the app, they just have to load from the server (all iphone apps must abide by this for now, until background apps are allowed). the "pull down to refresh" is there for obsessive people who feel like they must constantly refresh to get info.
I know there are a bunch of unpolished aspects, but that is part of the "release early" mentality. This app will get tons of iteration.
Comments
I agree completely (I wrote the app). The next version will be much more user friendly in the install/signup stage. Timing the app approval/launch was the issue that prevented it at initial release.
There is like a big list of minor annoyances. For example I get multiple notifications, but when I start the app there is nothing shown in the notification center till you pull the top down and release it. That's a bit counter-intuitive. If I were you I'd get someone on odesk for $30 an hour to rework the client while you focus on marketing your business and developing the backend.
notifications are auto-fetched when you open the app, they just have to load from the server (all iphone apps must abide by this for now, until background apps are allowed). the "pull down to refresh" is there for obsessive people who feel like they must constantly refresh to get info.
I know there are a bunch of unpolished aspects, but that is part of the "release early" mentality. This app will get tons of iteration.