3 ms·

I wouldn't write off Parse's value because one client was rough around the edges. I suspect the SDKs will become much more stable and usable now that the commun

by evv 11y ago

I wouldn't write off Parse's value because one client was rough around the edges. I suspect the SDKs will become much more stable and usable now that the community can help contribute to them. If you can find a part-time engineer that can build and maintain a backend with all of Parse's features, you should absolutely do that.

GeneralTspoon 11y ago
Now that it's open source it's possible to fix, but it wasn't back then. We couldn't ship an app that locked up a user's phone. Combined with all the other issues (mentioned at the top of this thread), we had to write-off Parse. > If you can find a part-time engineer that can build and maintain a backend with all of Parse's features, you should absolutely do that. Most likely, you're not going to be using all of Parse's features; probably just a small subset of them. So I think it's easily doable. In fact, if you were intending to use Cloud Code, you could probably do it yourself with the time you'd save by not having to deploy to production to test your code!