Hybrid apps provide the best of both worlds by combining aspects of native apps and mobile web apps. They allow developers to create an app-like experience for users while reusing web technologies and avoiding platform-specific SDKs. However, hybrid apps also have drawbacks like less seamless interactions between web and native aspects, as well as lacking certain native features and capabilities. The recommendation is to first consider a mobile web app using web technologies, and only create a hybrid or native app if specific professional features are needed that cannot be delivered through the mobile web.
Everybody wants an app today, but do you really need an app? The need for mobile solutions is growing and there are many ways to accomplish this. There is no "silver bullet" that fits every situation. As usual you need to first look at what problem you need to solve, what are the needs and then pick a technology. Responsive design, mobile website, web app, HTML5, hybrid, mixed hybrid, custom runtime, native, mobile platform, there are a lot of technical terms floating around in mobile development. Lets go thru each one and look at the benefits as well as the drawbacks, when they fit and when not to use them. We look at a couple of real world examples, what technology they use and why. Finally we end the presentation with a new interactive model that can give you a helping hand when choosing technology for your next mobile project.
This document discusses options for taking SharePoint mobile and applying a rich vs reach spectrum. It outlines two main architecture options: 1. Extend existing SharePoint sites to be more mobile-friendly through techniques like responsive design, conditional CSS, and jQuery Mobile. This allows reaching the broadest audience but with tradeoffs to user experience. 2. Build new mobile sites that leverage SharePoint data and services through APIs and the client object model. This provides a richer focused experience for mobile but requires building sites for specific devices and platforms. The document provides examples and best practices for each approach to help understand how to implement a mobile strategy for SharePoint.
The document discusses the history and current state of mobile application development. It begins with definitions and a brief history starting from the early 1990s. It then covers major platforms and operating systems that have emerged over time like Palm OS, Java ME, Symbian, Android, iOS, BlackBerry, and Windows Phone. Current development approaches including native frameworks and non-native alternatives like PhoneGap and Titanium are also summarized. The document concludes with a discussion of emerging areas like wearable technology and devices like Google Glass and Samsung Galaxy Gear.
Orange Partner HTML5 Day : un évent sur la découverte du HTML5 et son potentiel pour ouvrir un nouveau monde de possibilités...
The document discusses building mobile web apps using ASP.NET MVC, HTML5, and jQuery Mobile. It introduces ASP.NET MVC and its design goals of embracing the web and being extensible. jQuery Mobile is presented as a touch-optimized web framework for developing mobile web apps that work across devices. The document demonstrates building a sample mobile web app with ASP.NET MVC and jQuery Mobile that reviews restaurants. It concludes that this is a flexible full-featured framework for mobile web development.
The document discusses different approaches to developing mobile apps, including native apps, web apps, and hybrid apps. Native apps are developed specifically for a single platform using that platform's tools and programming languages. They have full access to device features but have high development and maintenance costs. Web apps are developed with web technologies like HTML, CSS, and JavaScript and run in a mobile browser, allowing cross-platform use but more limited access to device features. Hybrid apps combine native and web technologies by wrapping web views in a native container, giving them full device access and lower costs than native apps. The document explores the characteristics and tradeoffs of each approach.
BlackBerry Experience Forum 2013 Toronto, Ontario Developer Track, Session 2 Migrating Apps to BlackBerry 10 Jim Ing (@jim_ing)
CREDITS / REFERENCE: =================== http://www.themechrome.net/Images/Original/aaa.jpg http://activatedrinks.com/#/press http://www.webmedia-solutions.com/web-development-blog/wp-content/uploads/2009/01/web-2-0-logos.gif http://yiku.co/wp-content/uploads/2011/01/67bf1bb2g94361366956f690.jpg http://sixrevisions.com/web_design/the-evolution-of-web-design/ http://www.148apps.com/wp-content/uploads/2011/02/rdio.jpg http://www.desktopexchange.com/gallery/Widescreen-Wallpaper/evolution_1280x768 http://www.blogcdn.com/www.engadget.com/media/2010/12/bmw-connected-ios-app.jpg http://cdn.synthtopia.com/wp-content/uploads/2010/10/moog-filtatron.jpg http://venturebeat.files.wordpress.com/2011/09/gazelle-iphone-app.jpg http://phonerpt.com/wp-content/uploads/iOS-game-Cut-the-Rope-iPhone-iPad.jpg http://www.techtickle.com/wp-content/uploads/2010/11/facebook-app-iphone.jpg http://www.artofflightmovie.com/ http://makenetbg.com/wp-content/uploads/2011/06/servicios-makenet1.jpg http://charliecowan.files.wordpress.com/2011/08/noticeboard.jpg http://www.elipseagency.com/agency.html http://www.nikebetterworld.com/ http://2.bp.blogspot.com/_dCJEsq5nTZA/TJfyIHC87QI/AAAAAAAAAR4/S1hz8ltJY6U/s1600/Bel+Air+Split.jpg http://www.moodsofnorway.com/#/home http://www.ozoneeleven.com/wp-content/uploads/2010/05/Iron-Man-I-II_06.jpg http://www.netmagazine.com/opinions/mobile-apps-must-die http://www.mobileawesomeness.com http://upload.wikimedia.org/wikipedia/commons/thumb/a/a7/Web_2.0_Map.svg/800px-Web_2.0_Map.svg.png http://www.devirtuoso.com/2009/05/html-vs-flash-websites-which-is-better/ http://www.webdesignshock.com/wp-content/uploads/2011/08/responsive00.jpg http://www.ri.gov/img/responsive/banner.jpg slide related marks or contents are owned by individuals, or their related entities. This slide is neither endorsed by nor affiliated with any of these entities :)
Techday7, Cross platform application development using Appcelerator Titanium event's Keynote on Appcelerator Titanium By Sivakumar Veerappan, CEO and Founder of Anubavam Technologies
WebSphere is a platform for developing mobile apps across different platforms and devices. It allows creating web apps using open web technologies like HTML5 and JavaScript that can run on mobile browsers, as well as hybrid and native mobile apps. WebSphere provides tools for building apps targeting different mobile requirements and capabilities. It also offers server-side capabilities for integrating mobile apps with back-end systems and managing mobile apps across devices and platforms.
This document discusses hybrid mobile application development. It describes the hybrid approach as using a native mobile application container with embedded web technologies. This allows leveraging existing web assets while providing a native user experience. The document outlines challenges in mobile development and compares different approaches. It provides a case study of how Facebook used hybrid development and discusses best practices. These include design considerations, implementation techniques, and maturity models to optimize hybrid apps.
High level overview of the Next Generation Digital Publishing Platform of Twipe. Key lessons learnt of 12 years entrepreneurship in the internet and mobile space.
The FeedHenry Platform simplifies enterprise mobility by powering mobile apps from the cloud. It provides a cross-platform solution for building, deploying, and managing mobile apps. The FeedHenry Mobile Application Platform delivers an end-to-end solution as a service and allows enterprises to build apps for all major smartphones and tablets. It includes services for development, deployment, backend integration, access control, and analytics.
Tom Deryckere shared thoughts on mobile web development and how content management systems (CMS) like Drupal, Joomla, and WordPress can be used to build mobile sites. He discussed how the mobile web is different than the desktop web and outlined techniques like device detection, template switching, and content transcoding to optimize sites for multiple devices. Examples of CMS extensions and services that facilitate mobile development were provided. Attendees were encouraged to start building mobile versions of their sites.
Presentation during http://www.cartes-asia.com/ check out www.exiconglobal.com for many more presentation and reports
I did this presentation at the pera M@D community to give a brief introduction to mobile apps development.
This document discusses using HTML5 to build mobile web applications for the iPhone. It introduces HTML5, JavaScript, and frameworks like PhoneGap that allow wrapping web apps as native apps. Key elements of HTML5 for mobile discussed include offline support, canvas, video, geolocation, and advanced forms. UI libraries like JQTouch are presented for building touch-optimized interfaces. The document also covers PhoneGap APIs for native device access from a web app.
What is the Future of Mobile Web Application ? Mobile Web could be the final winner of the Mobile App Race ?
The mobile industry is worth over $1.3 trillion annually with over 1.6 billion mobile phones sold in 2011. There is significant hardware fragmentation across the over 680,000 distinct Android devices. Developing apps across the top 4 mobile platforms (iOS, Android, Symbian, Blackberry) reaches only 20% of devices. Mobile platforms differ in their programming languages, development environments, and app stores. No single cross-platform development tool supports all mobile platforms, and mobile web apps face challenges of fragmentation, performance, and monetization.
Application Development Methodologies Application Development Approaches Application Life-Cycle Management
The document discusses challenges in mobile application development. It outlines different methodologies for developing apps including requirement analysis, mockup design, UI design, development, testing, and publishing. It also compares different approaches like native, cross-platform, hybrid, and mobile-friendly websites. Application lifecycle management tools are mentioned for testing, distribution, analytics, and push notifications.
This document discusses building rich mobile apps with web standards using Sencha Touch. It summarizes the key benefits of Sencha Touch, including being cross-platform, using existing skills and tools, and not requiring app approval. It then provides an overview of Sencha Touch's features like layouts, components, touch events, data handling, theming and more. The document concludes by encouraging building a demo app to experience Sencha Touch.
Hybrid app development allows building a single app that can run on multiple platforms using web technologies like HTML, CSS, and JavaScript. It has advantages like lower costs, faster development time, and easier maintenance compared to building native apps for each platform. Popular frameworks for hybrid apps include PhoneGap, Ionic, and React Native. While hybrid apps have performance limitations compared to native, they are suitable when targeting multiple platforms or when most device functionality can be accessed through frameworks.
Overview of the importance of open governance, open innovation, open standards and open source. Focus on how these principles relate to webinos Presented by George Vougaris of Vision Mobile
This presentation will explain, how to develop an end to end mobile application using Javascript frameworks and Other Web Technologies, from mobile to server to database and unit testing
This document discusses mobile widgets and their development. Mobile widgets are offline-capable mobile applications that appear as icons in the device's apps menu and are built using HTML, CSS, JavaScript and AJAX. They are supported on platforms like WebOS and Android. The document outlines the benefits and challenges of mobile widgets, compares different widget platforms, and discusses how to build cross-platform mobile widgets.
This document discusses mobile widgets and their development. Mobile widgets are offline-capable mobile applications that appear as icons in the device's apps menu and are built using HTML, CSS, JavaScript and AJAX. They are supported on platforms like WebOS and Android. The document outlines the benefits and challenges of mobile widgets, compares different widget platforms, and discusses how to build cross-platform mobile widgets.