This post originated from an RSS feed registered with Java Buzz
by Fred Grott.
Original Post: Difference between Native and Webkit Web Based
Feed Title: ShareMe Technologies LLC-The Mobile Future
Feed URL: http://www.jroller.com/shareme/feed/entries/rss
Feed Description: A Weblog about Java programming and digital convergence on mobile devices in such areas as P2P and collaborative technology.
So what is different about writing Android Apps using web technologies than using native Java on Android? One, you have to plan how to handle mobile webkit quirks. For example in mobile webkit we have blocking javascipt downloads which means until that script is fully downloaded the rendering of web paes stops in mid-sequence.
Another difference is where the processing lives. In my Xspot app because I am processing dynamic stuff a UI js library such as iUI or CiUI where they use javascript power to do animations such as page slides and etc by actually recreating the pages in DOM on the fly wil not work as it conflicts with the processing have to do using javascript so that I have to change that so that we use webkit trasnofrmatiosn avery little js code for the iPhone like page effects and UI effects.
And there are more points of failure not covered by automatic tests and frameworks such as junit as CSs really canno tb e tested in such a manner. But, I think that is balanced out in that with the exception of the PhoenGap native libs the entire web code base of Xpost can be run on any mobile webkit platform which is sort of the promsie thart Nokia, Motorola, Opea and etc were attempting to accompiish with their widget efforts with the exception that in this way we are not switching form html, css, javascript, and etc tosoem new widget syntax and language.
Previous Topic
