Applicasa As Your BaaS

The New Comer – Applicasa

Last month I wrote a quick review of the two BaaS providers that I had used, StackMob and Parse. A few days later I received an email from Tzvi Kopetz, COO and co-founder of Applicasa, a backend solution provider who, even in it’s infancy, is filling in some of the feature gaps that Parse and StackMob have left open. Three of the biggest ones are managing AdHoc builds, a dedicated CMS and custom app framework.

Adhoc Builds

Seeing Applicasa getting closer and closer to provide the Adhoc capabilities of HockeyApp or TestFlight is an evolution that all mobile developers should pay attention to. I currently, have to manage my data/backend api with another provider while managing adhoc builds with TestFlight. Having everything centrally located would be a huge win.


I am a developer and really don’t want to worry about creating content. At a minimum someone could talk me into writing a script that populates schemas via script or upload. However, most other platforms don’t provide the necessary environment for a content editor role and a CMS that doesn’t have the unnecessary bloat of a traditional CMS.

With Applicasa you are able to create content editors that have a completely separate role from developers so they have an easy and intuitive console for managing the content. Both Parse and StackMob have content consoles with some management capabilities, but they aren’t as featured and you can tell they want you to populate your data via the API.

You can use backend service to send versions (updates) to different clients, use our CMS. I think our CMS is quite a > different approach from the other providers. We actually give you a complete solution so you don’t have to build a CMS, you don’t have to build a complete system for your clients (users). You can actually invite clients to use the system with the developers. – Lior Malenboim, CEO


Custom Framework

When it came time to actually integrate their framework into my test app I kept looking for a github repo or direct framework download from their site, but couldn’t find it. The reason being is that the framework is generated, by the developer on the fly based upon your database schemas and relationships. This is a feature that I never really thought about. Probably because I haven’t seen anyone do this. Parse and StackMob do a great job with their frameworks in regards to abstracting models on the client, however, they don’t give this fine grained control. The ability to have this type of control over the framework, particularly the models, is because the Applicasa framework is generated by the developer and stubbed out based upon your exact data structure.


Applicasa is a great backend provider with amazing features and support who is truly shaping up to be a “one stop shop”. I have talked with their founders and developers a few times over the past month and they have answered all my support questions promptly and notified me of fixes to any issues I discovered. Over the past month they have rolled out and/or updated their customized objects and iOS SDK, CMS, Webservice with code snippet, Push Notifications, Ad Hoc beta versions, Users management and tickets management system. I am looking forward to seeing what they come out with next.

I Will Not Ride the Dell Lightning

Being that my passion for development and design are usually centered around mobile apps I am always interested in any new platforms and handsets that poised to make any impact on the current market.  As such I was really interested in the article posted over at Engadget yesterday: Dell Lightning: the ultimate Windows Phone 7 device leaks out. However, my enthusiasm faded after the first sentence and twindled down to zero by the end of the first paragraph.

"Hot damn, people. The mother of all Dell leaks just dropped into our laps, and the absolute highlight has to be the Lightning, a Windows Phone 7 portrait slider."

I can overlook the fact that the device is running Windows and some of the on screen usability issues because I haven't used one, but what bothers me the most is that handset manufactures can't seem to understand handset design.  This phone is presented as having a "revolutionary" device design, but once again you have the same tired, inefficient slide-the-handset to show the qwerty keyboard.  Really?! That is the best you have. That is NO different from all the other handset designs that are offered by ever manufacturer in the world for the past 5 - 10 years.  Dell and Microsoft combined have more money than most European countries.  Why they don't or can't find/recruit/steal the BEST designers and developers to come out with a real competitor to the iPhone is beyond me?  However, what this does mean that within 6 months of this device launching you will see it sitting next to the Dell MP3 player that was supposed to be so great.

Looking over some of the other features that the device offers, once again there is nothing that I can't get, and probably better, with an iPhone or Nexus One.


When I was attempting to find a link to the dell jukebox from their website it didn't come up.