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. Parse4CN1 was created and is maintained by Chidiebere Okwudire from SMash ICT Solutions.
Migrating away from Parse.com
On January 28th 2016, Facebook-owned backend-as-a-service (BaaS) provider, Parse.com announced that their service will be retired on January 28th 2017. In its place, they released the open source Parse Server which is a Parse.com look-alike (but definitely not a clone!). Furthermore, according to the migration guide, users of Parse.com should have set up their Parse Server backend and released a new version of their app that points to it by the end of July 2016. This update of parse4cn1 empowers CodenameOne apps using the library to meet this target.
Are you still undecided about what direction to take with your migration? A self-hosted Parse Server, a Parse Server hosting service or perhaps even switching to an entirely different BaaS? We at SMash ICT Solutions will be glad to help you figure out what best suits your needs. Get in touch!
Push notification support
Note that parse4cn1 version 3.0 does not yet include push notification support. If you’re interested in push notification support after migrating to Parse Server, kindly fill the following short survey.
What a way to set off! Congrats on this big news and your very first blog!