Augmented Reality with HTML5
But you could just as easily have written the whole application in Dalvik, so what is the advantage of writing part in HTML5? Here are the advantages:
If you were writing a real application, the HTML5 part would be (relatively) portable to other platforms. You wouldn't have to rewrite it to port to, say, the iPhone. In the example, the HTML5 part is pretty small, but in principle, it could be much larger.
You could have kept the HTML5 part of the application on a remote HTTP server, to be updated whenever the app is run, without requiring the user to download an update.
If your application displayed information from the Web, it could be argued that HTML5 is a more natural place for Web interaction than Dalvik.
Compass card graphics adapted from commons.wikimedia.org/wiki/File:Compass.svg.
Rick Rogers has been a professional embedded developer for more than 30 years. Now specializing in mobile application software, when Rick isn't writing software for a living, he's writing books and magazine articles like this one. He welcomes feedback on the article at firstname.lastname@example.org.
Rick Rogers has been a professional embedded developer for more than 30 years. Now specializing in mobile application software, when Rick isn't writing software for a living, he's writing books and magazine articles like this one.
- Machine Learning Everywhere
- Own Your DNS Data
- Understanding OpenStack's Success
- Dynamic Kernels: Modularized Device Drivers
- Choosing a GUI Library for Your Embedded Device
- Understanding Firewalld in Multi-Zone Configurations
- Natalie Rusk's Scratch Coding Cards (No Starch Press)
- Hack and / - Linux Troubleshooting, Part I: High Load
- Returning Values from Bash Functions
- The Weather Outside Is Frightful (Or Is It?)