This is my number one peeve with apps ported from iOS and highly annoying. The AccountManager system already knowns my credentials and can provide the necessary access tokens - there is no need for your app to have yet another crappy username and password prompt. My passwords are also excruciating to enter on mobile devices because they are long and varied.
There seems to be some sort of fetish over repeatedly entering passwords and usernames on iOS. Am I the only one who noticed? https://plus.google.com/110166527124367568225/posts/Xdnbu4RP...
I'll agree it's not ideal.
There are many things like this. Developers whine that "it doesn't work well on Android" because they don't bother to learn how it should work on Android and just port their iOS app are surprised that it doesn't work well. iOS and Android are pretty darn different when it comes down to the details that matter in applications.
(IE: Instragram on Android is almost silly, whereas it seems nearly necessary to make the camera in iOS worthwhile).
- web 2.0
- "I have an idea for an iphone app"
The headline is bullshit click-bait.
It would definitely be cool if they open-sourced the platform, but, in the meantime, you might be interested in this project:
Personally, though, I don't mind paying for a service like Parse. If someone is willing to not only build the features I need but also to wear a pager and get up at 3am just to keep my users happy, I'm more than happy to give them some of my money.
My only wish was that I could place an easy API layer between Parse and my app, because I would want more fine grained control over how data is mutated (even with ACLs, someone with write permission could mutate data and corrupt it if desired).
There's a REST API, but I don't think I would want to use that as much.
Here's some data I exported from one of my Parse accounts: https://gist.github.com/2475461.
Deploying APIs in the cloud for primary use in mobile apps is an oft-repeated/able task, and it doesn't seem like there's anywhere near enough value in the Parse API on top of what you get from the native SDKs and a solid combination of open source stack software supported by an enterprise track record more promising than a Series A round a few months ago.
Also, as the comments here suggest, there are a lot of slight modifications to the default use case that reward having solidly built a stack not built on yet high-level PaaS abstraction. Sorry, but a JSON representation of your data is the low bar, not some instant proof that the product is magic.
In terms of value ... I'm really not sure how you lose - if your app is a flop you're going to coast along on the free plan, if it's a success you can focus on your app rather than your stack, and you can migrate away from them when you feel like it.
I'm not advocating Parse open source anthing, it's entirely up to them but open source does not mean $0.
> Ultimately, you want to have the whole thing in a
> UIScrollView (or a UITableView) to avoid such problems.
You'd think the framework would do that (or at least offer that), but nope.