Jason.O Keefe.Genuitec.Presentation.Final

This document discusses a HTML5 framework optimized for mobile devices. It allows cross-platform development for Android, iPhone, tablets and more. Key features include stunning UI controls, hundreds of plugins, and the ability to access device hardware through PhoneGap. Developers need knowledge of HTML/HTML5, JavaScript, jQuery and CSS. The framework offers documentation, reusable code, built-in themes and an online UI builder. While it allows building one app to run on multiple platforms, HTML5 apps may be slower than native apps and unstable at times on lower-end devices. Resources mentioned for support include forums, tutorials and emulators.

Slide deck from my session at the London Customer Company Tour 2012. More details can be found in the accompanying blog post at: http://bobbuzzard.blogspot.co.uk/2013/05/mobile-web-apps-with-html5-and-jquery.html

This document discusses different mobile development platforms and their features for building native and cross-platform apps. It covers platforms that allow developing once for multiple platforms using a single codebase, like Titanium, as well as platforms for each native environment. Titanium is highlighted for its native UI, local and remote data support, social APIs, rich media APIs, and open source extensibility. The document provides an example app structure in Titanium showing common JavaScript files for the app and a window.

Presentation at the Mobile SIG for the Silicon Valley Wireless Group held in Mountain View, CA on November 17, 2009.

The world of mobile is changing fast and as technologies evolve, so do the conversations surrounding them. Let's take a look at 8 mobile terms you need to know, both in terms of their definitions and how they relate to your mobile strategy. Tune into our webinar as we delve further into the technical aspects, stats and case studies.

The document discusses the mobile landscape and debates between apps and mobile web. It notes that iOS accounts for 48% of the market, Android 32%, Blackberry 15%, and Windows Phone 2-4%. While Android may have "won" in terms of market share, debates continue around native apps versus mobile web. The document explores options like hybrid frameworks that allow developing once for multiple platforms but notes these may still be inferior to native apps. It concludes that the debate is still ongoing and developers should not limit users in how they use their devices.

An overview of difference between Hybrid Mobile Applications, Native Applications and Mobile Web Apps. List of JavaScript frameworks that we used for Hybrid Mobile Apps.

Nick Landry gave a presentation on building a Node.js mobile app backend in the cloud for Android apps. He discussed using Microsoft Azure for hosting backend services, connecting to databases in the cloud, and sending push notifications. He demonstrated creating a mobile backend using Azure Mobile Services and sending push notifications using Notification Hubs. The presentation provided an overview of cloud development options and resources for building mobile apps and backends using Microsoft technologies.

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.

Slide deck from my Dreamforce 2013 breakout session on how to turn your Visualforce application into an HTML5 mobile application using the jQuery Mobile and Knockout.js frameworks.

There's a good deal of confusion surrounding mobile terminology. What's the difference between responsive and adaptive? What makes an app hybrid? What does mobile first really mean? Here are 11 mobile terms that you need to know, and what they really mean.

This document compares native mobile apps to mobile web apps. It discusses advantages of mobile web apps like easier updates, no installation needed, better compatibility, easier to obtain and share, cannot be deleted, and lower development costs. It also discusses when a native app makes more sense, such as for speed in areas like SQL queries, methods, programming languages, and front-end performance. The document also covers responsive web design, single page applications, MVVM frameworks, and using web sockets for real-time messaging.

The slides from Kevin Farrugia's presentation for MaltaJS on Progressive Web Apps. Date: 05/03/2016

This document discusses various aspects of developing and managing mobile applications, including: - Platform notification services for different mobile operating systems like APNS, WNS, MPNS, and GCM. - Using services like Notification Hubs and Mobile Apps to send push notifications across platforms from a single back end. - Application Insights for collecting telemetry from mobile and server applications to monitor performance, usage, and crashes. - Additional Azure services that can be used to build mobile backends including Event Hubs, SQL Database, Machine Learning, and analytics tools. - Resources listed for learning more about mobile development with Microsoft Azure and tools.

This document discusses mobile mashups, which combine multiple web services or data sources into a single application on a mobile device. It describes how mashups can combine different types of data or services for consumers, businesses, or to display similar data together. Common components of mashups include APIs, data formats like XML and JSON, architectures like client-based or server-based, and interfaces like native mobile apps or web apps. Examples of mobile mashups are provided, including ones for music, maps, and social networks. The document argues that mobile mashups will become more important as mobile devices surpass PCs as the primary internet access point.