Which browsers are supported in phone gap & which databases are supported by phone gap ?
Straight from Phonegap website -
PhoneGap is an HTML5 app platform that allows you to author native
applications with web technologies and get access to APIs and app
stores.
What this means is it is not browser dependent. The code compiles to native application. You don't need a browser to run it.
Related
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 thinking develop a web portal with a desktop. This portal will be used in mobile phones and as one of its requirements is to work offline and when you are online, synchronize data, I think it must be a native version for Android and iOS. What is the framework that advise to develop one application and generate an Android application and other iOS?
The idea is to try to enjoy the same logic of development for desktop and mobile. I have experience with AngularJS but do not know whether it will help in the mobile.
Is there an important difference between native mobile apps and mobile browserbased webapps according to the connection to a server which e.g. calculate stuff and sends it back to the mobile device?
The reason i ask is that there is a wide range of mobile app frameworks for serverside like vert.x, node.js, spring and many more. Isnt it just regardless of which framework I use to build a server for communication with mobile devices, no matter if they use a native app or a browser-based app - assuming they are totally equal in user-interaction?
I know there are differences in "what kind of information" is transacted between server and client according to performance, speed, scalability. My question aims only to the differences of native and browserbased web apps.
I just read this post: Server-side architecture for mobile web applications but i guess its not satisfying my lack of knowledge because author and question-resolver both refered to UI frameworks for mobile web applications. My idea is to have one server technology which is used by a mobile browser web app and the same app as native app at the same time with the same performance results. Is that something to worry about?
greetings
You can do the client side with browser and mobile apps with the one server side stack. Choose the server side depending on your skill set or those of your partners/employees and taking account of the nature of the task including volumes.
I would go for a server side that will support restful communication as that can be used by browser or mobile apps quite easily.
I am installing Flurry into a Phonegap application so that I might collect better in app analytics. I've seen numerous cordova plugins allowing you to use Flurry's iPhone and Android SDKs with Phonegap
e.g. https://github.com/jfpsf/flurry-phonegap-plugin
However Flurry has released a Mobile Web SDK. I assume the Mobile Web SDK is easier to integrate with a phonegap application, however I'm concerned that it is not as full featured or ill suited for working with phonegap. Can anyone comment on which SDK should be used in this situation? Many thanks.
Posing the question to Flurry's support team I received the following reply:
"The Mobile Web SDK tracks devices on the basis of cookies. The native SDK's track it on the basis of device id.
Apart from that, the mobile web SDK doesn't provide metrics like carrier, device and OS metrics. The native SDK provides those.
Crash reporting is not supported on the Mobile Web SDK. The native iOS and Android SDK's provide that."
Ergo, the SDKs are not created equally. One should use the native SDKs whenever they have the opportunity.
For Vellamo Mobile Benchmark, the HTML5 Chapter evaluates mobile web browser performance.
When running the benchmark, does it test using the default browser?
If there are several browsers installed on the Android device, how are other browsers configured to test on Vellamo?
The Vellamo HTML5 Chapter benchmarks the WebView component. It's the web engine used in the "Browser" APP as well as thousands of other APPS, which use it as layouting engine or to render online content.
Because of a limitation in the Android framework, Vellamo cannot test other Browsers. In Android 4.0 (I believe), the framework was adapted so that users could be able to switch to different web engines (for example Chrome), but afaik there is no simple way to activate this new behavior. I believe that in the future, Android will allow to select different web engines and if that happens Vellamo will probably offer the option to benchmark them.