Right now I'm building an app that relies heavily on Parse.com's products. The app uses nearly all of their features:

  • Data storage
  • User management
  • Push messages
  • Analytics
  • Crash reporting

There are of course upsides

  • Very very fast development: less time to market
  • Service reliability
  • Free of cost (to a certain extent)
  • No server setup

and downsides

  • the risk of BAAS shutting down: that would render the app worthless
  • what happens to my data

What do you think?

  • With regard to losing data, do they have a backup mechanism? If you run that every so often, you would hopefully be able to switch to a different vendor if they shut down. – Andrew Feb 12 '15 at 19:29

I am hesitant to provide an answer to your question, since it has a side of general micro economy question that is not really on-topic here at Programmers SE. But, since the site also allows questions of professional interest to programmers (as far as I remember), I think your question falls into the scope.

I would answer that the general problem you are talking about is called Vendor lock-in, and the usual solution is to establish standards in the market.

In a more specific, technical sense, you could establish your own "market standardization" by decoupling your software from the BAAS' services through your own API abstraction library.

| improve this answer | |
  • I agree with answer, just reminded me of classic xkcd :) xkcd.com/927 – Matt Klinker Feb 12 '15 at 19:42
  • @mklinker: you are right. Let me remark I meant to "create your own mini-standard and use it while there is no prevalent one", but not "propose your own standard to the world" ... unless you want people throwing that particular XKCD strip to your head :) – logc Feb 13 '15 at 11:56

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.