In 2011, developers building native mobile apps also needed storage, user accounts and server logic. AWS supplied infrastructure, while web frameworks and hosting services still left developers responsible for connecting and operating much of the backend. For a team focused on the mobile client, that work could consume time without distinguishing its app. PA1
Parse
Parse made mobile backends easier to build, but depended on a parent with different priorities
Arena: Market Conditions Before Parse
What shaped the outcome
Step 1 of 4 · 2011–13
A mobile-oriented backend removed work outside the app
Parse connected native app code to common backend functions through client SDKs. Sukhar contrasts that starting point with deploying a web application on Heroku or assembling infrastructure on AWS. Wired’s contemporaneous reporting includes a developer who had used Parse before the acquisition and saw value in the broader platform. PA1 PA2
The appeal depended on the customer’s job. A mobile team could spend less effort on infrastructure that did not make its app distinctive. An experienced backend team might prefer control over its own stack. Treating these as different buyers explains why adoption could be real without implying that Parse was universally better than lower-level cloud services.
Rivals Heroku hosted an application the developer still built; AWS exposed lower-level components. Compare the work remaining for an iOS-focused team.
Step 2 of 4 · 2011–13
A generous entry offer created a difficult service obligation
Sukhar recalls a large free audience, paying games and agency customers, and unusually responsive early support. He also describes the difficulty of funding reliability and support while keeping prices attractive compared with AWS. PA1
A developer’s ability to start cheaply did not eliminate the supplier’s work. Growth added varied workloads and support requests. The company had to decide which usage should pay for those obligations and when. This is a plausible constraint on independent scale, not proof that Parse was unprofitable in every segment or could never have supported a standalone business.
Rivals The relevant ceiling was the cost and effort of using cloud infrastructure directly once a customer had enough scale or engineering skill.
Step 3 of 4 · 2013–16
The acquisition changed who decided which work was worth funding
Facebook acquired Parse in 2013 and initially gave it visible support. Sukhar later said the proposed developer business lost internal priority as Facebook’s mobile advertising business succeeded. A competing infrastructure founder also questioned the fit between app hosting and Facebook’s business. PA1 PA2 PA3 PA6
The sale moved Parse into a different comparison. Its next engineer could be weighed against work on advertising as well as against rival backend products. A parent can rationally reduce a service that customers value when its alternatives have greater returns. That mechanism fits the sequence, but the interviews do not reveal the actual internal budgets or prove that another owner would have kept the service alive.
Rivals Compare an independent backend company seeking service revenue with a parent choosing among hosting and advertising investments.
Step 4 of 4 · 2016–17
Open source preserved software while returning operating work to customers
The official migration archive records the hosted service shutting down on January 30, 2017. It instructs customers to run Parse Server on their own computer and hosting provider, with MongoDB hosted separately, and documents compatibility work. PA5
The code’s survival did not preserve the original purchase: a backend someone else operated. Developers regained options for hosting, but also had to arrange infrastructure and migration. This makes continuity a distinct part of the product value. Code reuse and an active open-source successor cannot be treated as uninterrupted delivery of the old hosted service.
Rivals Compare continued use of a managed backend with operating compatible software or choosing another managed supplier.
Key dates
- 2011An iOS data library defines the entry
- 2013The backend grows beyond storage
- 2013-04Facebook acquires Parse
- 2013-09-12Public backing continues
- 2015Internal priorities diverge
- 2017-01-30The hosted service ends
Sources
Oldest first.
- PA6 Parse after the completed acquisition. Transaction reporting
- PA2 Facebook buys its way into the heart of the app world. Contemporaneous interviews
- PA3 Facebook never wanted to host your app. Outside analysis
- PA5 Parse migration guide (archive). Primary documentation
- PA1 Facebook Parse acquisition: Ilya Sukhar transcript. Founder interview