120 likes | 243 Vues
With over 234 million wireless subscriptions in the USA, the mobile device market is rapidly evolving. As smartphones acquire faster processors and improved wireless networks, developing device-independent mobile web applications becomes crucial. This development must address challenges such as consistent user experience, variable mobile displays, and data storage options. Utilizing WebKit as the rendering engine enhances compatibility across platforms. By ensuring proper viewport management and optimizing speed through reduced requests and data compression, developers can create robust applications beneficial to users on any device.
E N D
Device-independent Mobile Web Application Development ArchanaMandape
Importance of Mobile devices • 234 million Wireless subscriptions in USA. • Many players in the smart phone market. • Apple iPhone OS, RIM BlackBerry OS and Android OS are operating systems. • Mobile devices are getting faster processors • Improved Wireless Network. • An important platform for Web Applications
Device Independent Mobile Web Application challenges • Consistent user experience • Mobile Device Display • Data Storage • Speed
WebKit Browser Engine • WebKit is an open source web content engine for browsers and applications. • WebKit is used as the rendering engine within iOS, Android , Safari on Windows and also in Mac OS X. • WebKit has a smaller footprint – less memory and CPU requirement. • It is ideal for the mobile environments. • It can be used for desktop and mobile web page development.
Mobile Device Display • Mobile Device Display • The size of the viewport and scale of the web page • The device's screen density • Using Viewport Metadata <meta name="viewport" content="width=800" /> • Automatic sizing • <meta name="viewport" content="width=device-width" />
Mobile Device Display • Defining the viewport scale. Its • initial-scale • minimum-scale • maximum-scale • user-scalable • Defining the viewport target density. Its values can be. • device-dpi • high-dpi • medium-dpi • low-dpi • <value>
Data Storage • Cookies • Stored on device memory • Not suitable for large data • Not reliable • Client-Side Storage • No Access for Web Apps • HTML5 provides few capabilties • Database on the Server • Best available option • Common technique - JASON
Speed • Reduce number of requests and amount of data transferred • Avoid multiple file requests • Data Compression • Eliminate redirects
Conclusion Developing Device Independent Mobile Web Applications can be achieved to some extent!!
References • Advance css By: Joseph R. Lewis; MeitarMoscovitz • Programming the Mobile Web By: MaximilianoFirtman • Towards a uniform web application platform for desktop computers and mobile devices By TommiMikkonen and Antero Taivalsaari