How to proceed with Hybrid Mobile Application Idea? [closed]

Question

We have monetizable Mobile Application Idea, and will be building our first mobile Hybrid application.

I looked into few things and figured out that to achieve my end-to-end goal I would need:

1. Front End UI Framework : possible options: Ionic / AngularGap [but documentation seems parse].

2. Then I think we need to wrap it up with PhoneGap for various platforms.

3. Have a BackEnd framework - Loopback / Parse

I have yet to look into specific documentations, but it would be very helpful to have a experienced suggestion if the path is right.

What I don't know right now:

A. What I am thinking is right and how I should proceed.

B. Ionic is an UI framework and how do I connect it with Phonegap, like how to access native features. I think I have to use angular to call Phonegap apis ?

C. If I get the front end part set, how do I call backend apis like that of loopback? through REST calls? or there are other more efficient ways to do that?

Are there simpler ways to achieve this?

Answer 1

I am also working on mobile app for last few months. Tried lot many UI frameworks for hybrid app developmet, tried lot many server side and NOSQL DB technologies and below is my learning for UI frameworks from my experience.

• Sencha Touch - Early entrant in hybrid app space, most known till date, best cross device support but steep learning curve as they have their own framework rules. Moreover app is bulky and run all JS to build HTML at run time which hits performance to some extent. Surely not a good idea to build whole app IN JS, if compared to HTML5.

• jQueryMobile - Poor performance on mobile

• BootStrap - Good UI but poor performance on mobile. It was not dev at first place with mobile in mind

• PhoneJS - Neat / clean UI but not free for non-open-source apps.

• Chocolate-chip UI - Light weight, native look and feel, but not well supported in cross device cases, new player and not much adoption. Surely the work done is good and hopefully it will improve in future as its backed by company.

• Ionic Framework - Great UI framework in dev. As of now in alpha and I would not recommend or prod apps. Did some quick tests and found few issues on Android like slider does not work properly, you need to tweak something. I think, its developing fast (recently got investors funding too), so hopefully it will soon be a matured UI framework and best out of lot, but till then its just good for prototyping not prod apps.

• LungoJS - Light-weight UI framework. Good transition, native look and feel, Good cross-phone support (Android + iPhone), Bad tab support (have UI issues on tab), Not actively maintained as developer is busy creating some new framework.

For my app, I picked up LungoJS and will eventually move to Ionic once it get matured and have decent adoption.

All of these can be used with PhoneGap / Cordova to access native device APIs and package it as mobile app.

Advice on jQuery vs Angular - Surely Angular is better option over jQuery, it makes performance (UI transitions) faster on mobile app when compared with jQuery implementation.

Hope it help.

Gaurav

http://www.linkedin.com/in/gauravdhiman

Answer 2

I am also trying to study Ionic framework to use with an Android app. Ionic seems to be a very good framework, but the lack of documentation is blocking me from advancing.

From what I have seen so far, it looks like Ionic+Angular already integrates Cordova. So you don't need to create a Cordova app anymore, just create an Ionic app and it has Cordova underneath it:

Did it using Ionic CLI, which uses ionic-angular-cordova-seed

About the backend, Angular provides $http and $resource for AJAX requests, take a look at the Angular documentation, I assume Ionic didn't change the way Angular makes these calls.

My conclusion: I think when Ionic becomes a more mature framework (which won't take long) with better documentation, it will be the best UI framework. From what I have seem, it looks very native with very good performance. And I still plan to keep going with it for having no better option, although it is taking me some time because there are things I still can't understand.