So after too many searches I decided to ask this question.
First of all I'm building a mobile app using angularjs in my website (Online) not localhost. The app is a kind of a CRM based (CRUD mostly).
I have the cordova mobile application ready. I have a few questions here.
Is it acceptable, if I use the website URL directly in the inappbrowser URL (Like an iframe)?
Or. Should I need to put the angularjs files inside the www directory of the cordova app and access the server functions via API?
Which way is preferable? Why?
Will there be any performance differences?
If the No.1 is not a best practice, what is the major drawback on using the inappbrowser?
You can build Hosted Web App in an Apache Cordova:
For this scenario, you use a thin Cordova client (think of it as a web
browser embedded in a native app) that automatically redirects to your
Web site.
See also: Wrapping an existing web application in Cordova.
Other option: PWA.
From Wiki:
Progressive web applications (PWAs) are web applications that load
like regular web pages or websites but can offer the user
functionality such as working offline, push notifications, and device
hardware access traditionally available only to native applications.
PWAs combine the flexibility of the web with the experience of a
native application.
Related
I am trying to build for website so I need to know that.what is progressive web app? and all devices or only moniter.
Progressive web apps are web apps that can look and act like native apps.
django-progressive-web-app may be a good place to start your research about using Django for your project. I've never used it myself, but it looks promising.
Is there a significant advantage of creating a mobile app as opposed to a web application?
I pose this question from the following perspective, which is biased towards my lack of knowledge of the mobile phone architecture.
You can build a web application with pure javascript, css, and html.
You don't have to write different code for iOS, Android, etc.
The user simply goes to a url, and that's your app, served right there from the server.
I would like someone to highlight some of the advantages of writing specific code for a mobile web application.
What does a mobile app fundamentally have a significant advantage over a web application?
Mobile apps have some advantages:
Assets are packaged on the phone - you only need to load data from
the server, not your layout.
Users are familiar with the conventions of their chosen mobile OS,
which your app will follow.
Trends show users are spending more time in Apps than web on mobile
Can work offline (even if limited)
Mobile apps have access to native features like push notifications,
GPS, Camera, etc
There are also hybrid apps - which are web apps running in a native container. You may have heard of Cordova, which is a platform for acheiving this. You basically create your app as a web app, and it runs inside a native WebView - with this you can use a javascript API to access some native features, but you don't get many of the other benefits of a native app.
Easy to use
Use native mobile design
Don't take long time to load just load data and images but web load (data/images/css/js)
I am not very experienced with this topic, but these are some fundamentals of using mobile apps:
They are accessible offline. (but that is restrictable)
The assets of the downloaded app are stored on the phone itself, thus the main content loads much faster.
As stated before, they have access to the hardware of the device (GPS, camera, etc, sensors etc.)
You can store as much data on the device as you want (opposed to, let's say 5mb using the HTML5's Local Storage).
They have access to push notifications (such as in Android or iOS)
They can put all the powerful hardware of the phone to use.
I am interested in using Ionic to build a web app. The tabs, form stuff, integration with angular.js... everything looks like it should work great.
However, Ionic also looks to be geared towards creating native apps for Android and IOS. It relies on node.js for services. I'll just be hosting it on my client's shared hosting account - I won't be able to get node.js working for it. I don't intend to develop the app to use any services, so I don't think I need node.js. I'll plan to communicate with my DB via http post.
I am interested to know - is there any reason I wouldn't do this? If I am not using any other means of communicating with a server, will I be okay without node.js? Is there a better option for creating an html5 mobile 1 page web app?
I also don't intend to access the camera, accelerometer, or any of that kind of thing, so I don't think I'll need cordova, either.
ionic uses node.js only for development, things like build, test and deploy
not necessarily for back-end proposes
i want to know what is the best backend (database) for a jquery mobile web app and if you have any tutorials and tips that i could use? What is the best database to support a jquery mobile web app?
Thanks
Backends for mobile apps is a completely different concept altogether when it comes to the context of market. There's a new revolution of mBaaS providers - mobile Backend as a Service. Instead of having your own backend, writing your own web services and exposing them to your app, I would suggest trying a mBaaS, unless the situation is demanding to go by the traditional ways.
I want to try using trigger.io.
We have a Web App and using GAE.
How can we test our Web App with trigger.io?
I see that on the "WEB" section of the toolkit there's only a spot for "Heroku".
Is it possible?
Do we need to migrate?
How can i test our web app with android? I couldn't find a place to direct it to our index.html.
Thanks a lot.
The web section in the Toolkit basically lets you deploy your mobile app as a mobile website, based on Node.js.
If you have an existing web app that you'd like to use as the backend for a mobile app, then it's a case of exposing some sort of HTTP API which your mobile app then interacts with.
Having the mobile app just receive JSON from GAE, build its HTML views and present them to the user works really well.