Chidiebere Okwudire of SMash ICT Solutions just
released version 3.0 of the parse4cn1 library.
The biggest feature of which is support for the open source Parse server which should work with some of the
parse alternatives that popped up to fill the void left by Facebook.
This is great news. In a way I’m more optimistic about the future of Parse than most other MBaaS
(mobile backend as a service) solutions (e.g. Firebase). Now we have competition and options within
the Parse space which aren’t as common for other MBaaS solutions.
Having worked with Parse4cn1 in the past I’m pretty excited about this update.
I hope to have a blog post in the near future detailing the migration to new parse servers and working with the
API in the post Facebook era.
New Windows Servers & UWP Docs
One somewhat undocumented pleasant result of the new UWP (Universal Windows Platform) support is the fact
that we needed new Windows based build servers to provide support for UWP. As part of that need we now have
better (faster and more reliable) servers for Windows desktop builds which should hopefully spend less time in
the building queue.
While we are on the subject of the UWP support Steve is working on making this target more seamless. There
are still some issues in the current version when targeting phones and we will probably need to do some work
to get this to the smoothness enjoyed by other platforms. We will also need to release a new plugin as the
settings for UWP builds have become far more challenging.
This level of complexity justified a new developer guide section dedicated to UWP, this is still under active
development but you can follow it on our website here or in the
that hosts the entire developer guide (which you can
help us write/edit !).
HI Shai, thanks for promptly sharing the parse4cn1 update!
I also agree with you that Parse Server is actually a blessing in disguise. More on that in the upcoming article that you referred to 😉
Looking forward to that blog post about parse migration