I want to create an HTML5 app for iPhones and Androids that is based on an HTML5 app framework. The app will do nothing but monitor the network activity (only cellular not WIFI) of the device.
I have been searching for how to do this for a few hours now, but haven't been able to find out how to do this, or even if it is possible or not.
Is it possible to monitor iPhones/Androids network activity in an HTML5 app built on an HTML5 app framework? And if so, how?
(I'd prefer to find a framework that exposes the network data usage of iPhones and Androids to the app instead of coding my own if possible)
If you built the application container for your HTML5 app then yes with the new Web Inspector for Safari, this works as well if your building a mobile html5 app on a server.
Chrome also has a similar debugging feature for Android.
http://webdesign.tutsplus.com/tutorials/workflow-tutorials/quick-tip-using-web-inspector-to-debug-mobile-safari/
https://developers.google.com/chrome-developer-tools/docs/remote-debugging
Related
Our app is built on Qt-C++ which acts as a backend. For front end, we invoke browser command in a given platform (Windows, Mac, Linux). Now the Javascript of browser and the C++ of backend communicate via WebSockets. All the rendering happens fine and app works well.
[Note: It turns out that, Qt's Web-engine is not a good option due to its size and inflexibility.]
However in the case of mobile apps there are few concerns.
We cannot invoke the chrome browser as we do in Desktops, because the main app goes in background and brings the "Google Chrome" (browser) app in foreground
The default choice is Webview, but there are few limitations of it as noted here
Our app is not heavy in rendering. Though it requires playing of video and webrtc (which is available with some of the Android webviews).
What is the best solution when the android app requires the features of Google chrome browser app?
Related: Are there any ways to embed a browser in Android app?
I have a medium size project on React+Nodejs and I need to choose best suitable technology for the mobile part. I am considering React Native or Web Progressive Apps for that. I want to ask you guys what is your experience so far about performance of "native-like" React Native versus WPA based apps.
I need to put into consideration:
1. Making it as easy as possible to make a transfer from ReactJS code into mobile.
2. Hardware support on mobile devices. Such as Barcode reading and NFC.
3. Push notifications.
4. Function well on both Android and iOS.
Biggest question is whether WPA technology has already become mature enough to trust it or not.
I had to make the same decision couple of months back and we chose PWA (not the answer for everyone yet).
Here is why we chose PWA,
1) Performance - Web can now perform 60fps - The magic number needs for native like smooth transitions.
2) Cost - Its fast and easy to build a product for both as a mobile app and web using PWA with no learning curve for existing web developers.
3) Proven - Starting from Twitter lite to Flipkart, there are so many success stories on PWA. No doubt its reliable. With iOS support coming couple of months back, now all major browsers support it.
PWA limitations and workarrounds,
1) Hardware - PWAs are limited to what web can do today. So there are hardwares like bar-code scanner we don't have any scope of support anytime soon and there are some hardware which very limited support and some hardware like Bluetooth with average support(in terms of % of browser versions supporting today) We had to build a small Android Native application to interact with these hardware and pass on the info to PWA suing web sockets. Say, when a barcode is scanned, this native Android service will listen for and receive it and pass on to our PWA. Same thing goes to NFC.
2) Packing and deploying - There is no official way to generate an APK and distribute in corporate environment. We were able to extract the APK after adding the PWA app to home screen using some file explorer and use that to distribute though. Havent tried on iOS. Hope for latest versions for any mobile OS, we can use cordova(not pure PWA but we get most of the benefits like Service Worker) to package and distribute as well.
I'm developing a Point-of-Sale solution to be deployed on an iPad. The application will be engineered as a web application. I've seen some great info on how to lock down the iPad to a specific application and so this gets me halfway to my solution; the application I lock down to will be the browser.
Lock-down iPhone/iPod/iPad so it can only run one app
Now, can I take this one step further? Can I lock down the browser to disallow ad-hoc browsing? I'd like to do this because I want to ensure that the user is constrained to the confines of the POS application at all times.
(If I can't do this, I'll need to write a small shim application to host my web application and I don't want to do this, because this violates the zero-install architecture we're trying to achieve.)
Alternatively, is there a way to achieve this with an Android tablet? As the application is constructed with HTML5, we are relatively agnostic as to the client device.
Thanks for your advice!
You could add the Website to the Homescreen. Then it appears as an app - maybe you can then lock it down with the mechanism you mentioned.
I wrote an HTML5 web application which is intended to run for a long time (on Android and iOS).
I would like to lower the battery consumption by turning off the display without locking the phone.
Is it possible to achieve this functionality using a web application or only by using a native application?
Thanks,
Buenon
i am currently a mobile web application with jquery mobile. Is there a way of testing the application with an emulator that works for ipad, ios, blackberry, android, symbian and other major os on my local machine without connecting to the internet or using a real phone or hardware.
You may be interested in the ripple project. Currently its a chrome extension for emulating different devices. Sure it has shortcomings but it can be very useful for certain situations.
http://ripple.incubator.apache.org/
To avoid connecting to the internet: run your server on localhost
To avoid using actual hardware, use the emulators that come with the SDKs for the platforms you're interested in. But at first, just use the computer browser; I'd recommend Safari, as it is based on WebKit, like iOS and Android use.
One thing I tend to do is use FireFox with user agent switcher plugin. This allows you to configure a series of user-agent identifiers in your browser to 'fool' your jQuery mobile website into thinking it's dealing with particular devices.
if all you want is to load a mobile url and see how it looks on different phones you could try this site
http://www.synthphone.com/