First off, there are many projects running under the “open source” label today, but not all open source projects are created equal. In the past, open source initiatives were often driven by community-focused philosophies centered on transparency, accessibility, and collective growth. Today, however, some open source projects are backed by investors with profit expectations, which can influence both their evolution and longevity.
Parse Platform is a prime example of a community-funded open source project, sustained by the dedication of developers and users who genuinely believe in its capabilities and long-term value. In contrast, investor-funded open source projects like Supabase, which has raised hundreds of millions in venture capital, will eventually need to generate returns. Investors don’t give money away for free. Supabase may one day face pressures to monetize or pivot, potentially positioning it closer to Firebase in terms of strategy and monetization.
The Parse community has managed to maintain its independence and open-source integrity since Facebook transitioned it to us. While our community may be smaller, that closeness is an advantage, offering more meaningful contributions from people who are genuinely invested in its future. Parse’s “maintenance mode” is a reliable, stable base. Though it may not boast a flashy marketing presence, it provides powerful features for developers. Saying it’s “only in maintenance mode” overlooks the ongoing efforts by contributors who are enhancing features, adding new ones, and resolving bugs.
That being said, it’s true that there’s room for improvement - and we’re working on it. From redesigning the website to attract new developers, to rewriting the documentation for an improved developer experience, to modernizing and unifying the Parse client SDKs for streamlined development, to updating Parse Dashboard with a new framework, and fixing open issues across all Parse repositories. We introduced the Parse Bounty Program to incentivize contributions, but some changes are significant and require a broader community collaboration.
We’re always open to suggestions on how we can improve Parse’s future and expand its reach - every idea helps us shape a better experience for developers, so I appreciate you opening this topic.