Parse and CodenameOne

How I chose my Parse.com replacement (Part 2/2): 3 Parse Server-based solutions worth considering

You probably recently received the “Next Steps from the Parse Team” newsletter in your inbox in which you were urged to take immediate action as it pertains to migrating your Parse.com-hosted apps. Or at least, you’re aware of the ultimate January 28, 2017 deadline for migrating your apps. While you should take such reminders seriously, there’s no need to panic. In this article, I share my experience with different Parse Server hosting backends and my choice after applying the principles outlined in Part 1 of this series. Read on!

Parse and CodenameOne

How I chose my Parse.com replacement (Part 1/2): 5 things you should consider while choosing yours

By now, the imminent shutdown of Parse.com must have hit home for you as well: You wish it was merely a bad dream but unfortunately it’s a stark reality. You’ve got just a few months left to migrate your existing apps and obviously do not want to face another shutdown. Nearly every major MBaaS vendor is brandishing a banner that directly or indirect says “Parse.com let you down but you’re safe with us”. However, whom can you trust? Or maybe you should just host your own Parse Server? How about migrating away from anything Parse-like and settling for a completely different MBaaS. In this post, I share some important points to consider while deciding on your replacement for Parse.com.

Parse and CodenameOne

Parse4CN1 is now Parse Server-ready!

We’re happy to announce the release of parse4cn1 version 3.0! With this version of parse4cn1, CodenameOne apps using the library can now specify the Parse backend URL. Parse4CN1 is a port of Parse’s REST API to CodenameOne (and by extension to Java) enabling apps built using CodenameOne to access a lot of the functionality provided by Parse in a cross-platform manner.