The document discusses considerations for choosing between native and HTML5 approaches for mobile app development. Key factors include app complexity, target platform, audience, development team strengths, and future plans. It also covers technology choices like using native device functions, offline storage, and development speed. Hybrid, mobile application development platforms, and cost considerations are also discussed.
The document summarizes the development of Scripted, a lightweight browser-based code editor. It discusses observations that heavy IDEs are not ideal for JavaScript development and speed is essential. Two prototypes were created - Orion and Scripted. Scripted focused on speed, code awareness through static analysis, and module system comprehension. Near term goals include improved content assistance and a plugin model. Long term goals include debugging integration and support for additional languages.
This is the slide deck of the Zend webinar "A tale of two toolkits".
Have you heard of the exciting new open source XML Toolkit currently being developed in collaboration between IBM and Zend? Are you curious about how it works and what you need to get started? Are you aware that it is available in Zend Server 5.1 as a beta and soon to be released as GA? Well rest assured, Mike Pavlak will fill you in on the details and a little bit more.
You can watch the webinar at http://bit.ly/q9byHS, after a short registration.
Slides for my talk at OpenSlava conference 2013-10-11.
Abstract: Integrated Development Environments are at the neuralgic centre of developer activities. For many of us it’s unconceivable to work in complex developments leveraging multiple heterogeneous tools for design, build and test activities without the IDE connecting them all.
IDEs are powerful tools, capable of handling many types of tasks. In many cases, IDEs are perceived as a commodity but this is a naïve approach that ignores the many brilliant features that IDEs can be used for: debugging, code generation, test automation, version control, quality assurance, task & issue management, etc.
During this talk, participants will get an overview of what IDEs mean today, for the newbie, the enterprise and the hard-core developer, will get introduced to key IDE features that every one of us should be using, and will participate on an open discussion about what next-generation IDEs should look like.
The document discusses the future of mobile applications and frameworks. It covers HTML5 and cross-platform mobile development using PhoneGap. PhoneGap allows developing mobile apps using web technologies like HTML, CSS, and JavaScript that can access native device capabilities and be deployed to various mobile platforms. The document provides an overview of PhoneGap, mobile design considerations, and an example of building a photo sharing application using PhoneGap.
Everyone, everywhere, at any time: adopting a multi-device learning strategyEpic
Kath Fleet & Raoul Dewhurst's seminar at Learning Technologies 2013 in which they explore responsive design for e-learning and share Epic's case studies of sucessful multi-device learning projects.
New voice, new tone, new IA: Writing for the modern developerKeith Boyd
Keith Boyd presented on changes to Microsoft's developer documentation strategy. The developer landscape has shifted to a post-PC world with multiple platforms. Microsoft faced challenges with outdated content and siloed information. For Windows 8, Microsoft adopted a developer content 3.0 approach with a targeted, integrated experience on Dev.Windows.com. This includes easy to find content organized by a software development lifecycle. Samples are prioritized to inspire developers and support scenarios from planning to selling apps. The voice and tone of content shifted to a more approachable style while maintaining authority. Metrics like Windows Store app growth will track the strategy's success.
This document discusses code generation in .NET. It begins by outlining some common problems developers face when dealing with large amounts of repetitive code. It then discusses various approaches to solving this problem, including hand coding everything, fully generic design, and using a combination of tools including code generation. The rest of the document discusses specific code generation tools for .NET like StringBuilder, CodeSnippets, XSLT, Reflection.Emit, EnvDTE, CodeDom, and T4. It also discusses pros and cons of each approach and provides examples of using code generation in different real world scenarios.
The document summarizes the development of Scripted, a lightweight browser-based code editor. It discusses observations that heavy IDEs are not ideal for JavaScript development and speed is essential. Two prototypes were created - Orion and Scripted. Scripted focused on speed, code awareness through static analysis, and module system comprehension. Near term goals include improved content assistance and a plugin model. Long term goals include debugging integration and support for additional languages.
This is the slide deck of the Zend webinar "A tale of two toolkits".
Have you heard of the exciting new open source XML Toolkit currently being developed in collaboration between IBM and Zend? Are you curious about how it works and what you need to get started? Are you aware that it is available in Zend Server 5.1 as a beta and soon to be released as GA? Well rest assured, Mike Pavlak will fill you in on the details and a little bit more.
You can watch the webinar at http://bit.ly/q9byHS, after a short registration.
Slides for my talk at OpenSlava conference 2013-10-11.
Abstract: Integrated Development Environments are at the neuralgic centre of developer activities. For many of us it’s unconceivable to work in complex developments leveraging multiple heterogeneous tools for design, build and test activities without the IDE connecting them all.
IDEs are powerful tools, capable of handling many types of tasks. In many cases, IDEs are perceived as a commodity but this is a naïve approach that ignores the many brilliant features that IDEs can be used for: debugging, code generation, test automation, version control, quality assurance, task & issue management, etc.
During this talk, participants will get an overview of what IDEs mean today, for the newbie, the enterprise and the hard-core developer, will get introduced to key IDE features that every one of us should be using, and will participate on an open discussion about what next-generation IDEs should look like.
The document discusses the future of mobile applications and frameworks. It covers HTML5 and cross-platform mobile development using PhoneGap. PhoneGap allows developing mobile apps using web technologies like HTML, CSS, and JavaScript that can access native device capabilities and be deployed to various mobile platforms. The document provides an overview of PhoneGap, mobile design considerations, and an example of building a photo sharing application using PhoneGap.
Everyone, everywhere, at any time: adopting a multi-device learning strategyEpic
Kath Fleet & Raoul Dewhurst's seminar at Learning Technologies 2013 in which they explore responsive design for e-learning and share Epic's case studies of sucessful multi-device learning projects.
New voice, new tone, new IA: Writing for the modern developerKeith Boyd
Keith Boyd presented on changes to Microsoft's developer documentation strategy. The developer landscape has shifted to a post-PC world with multiple platforms. Microsoft faced challenges with outdated content and siloed information. For Windows 8, Microsoft adopted a developer content 3.0 approach with a targeted, integrated experience on Dev.Windows.com. This includes easy to find content organized by a software development lifecycle. Samples are prioritized to inspire developers and support scenarios from planning to selling apps. The voice and tone of content shifted to a more approachable style while maintaining authority. Metrics like Windows Store app growth will track the strategy's success.
This document discusses code generation in .NET. It begins by outlining some common problems developers face when dealing with large amounts of repetitive code. It then discusses various approaches to solving this problem, including hand coding everything, fully generic design, and using a combination of tools including code generation. The rest of the document discusses specific code generation tools for .NET like StringBuilder, CodeSnippets, XSLT, Reflection.Emit, EnvDTE, CodeDom, and T4. It also discusses pros and cons of each approach and provides examples of using code generation in different real world scenarios.
How engaged are your customers, how do you know and why should you care? - To...Internet World
Digital Marketing Theatre - 17th June, 10:30-11:00
Personalised email content based on individual subscriber preferences is already widely used, but a quantified understanding of subscriber engagement is now emerging as a valuable new insight into past, current and most importantly future customer behaviour. This presentation explores some of the latest developments, applications and benefits of 'engagement' profiling.
The Council on Environmental Quality (CEQ) has taken several steps to increase transparency and comply with new FOIA guidelines from the President and Attorney General. These steps include revising FOIA regulations, implementing new procedures for processing requests, providing staff training, and increasing proactive disclosures by improving its online reading room. However, CEQ still faces some impediments to fully utilizing technology due to lacking internal IT support.
Creating an online community is important for the Howard League to connect with supporters and raise awareness of issues. They are reorganizing their website, developing blogs, and building online campaigns. Supporters can get involved by revealing themselves on the site, joining discussions, and spreading the Howard League's message that custodial sentences often fail to rehabilitate people and reduce reoffending.
This webinar provides an overview of what to expect at diabetes camp, including a typical daily schedule, registration procedures, homesickness prevention and treatment, diabetes management, and outstanding forms. It outlines a sample camp day consisting of wake up, activities, meals, testing blood sugar levels, and bedtime. The registration process uses stations to meet staff and get important information. Homesickness is addressed by keeping campers busy and reminding them of all the fun activities.
Viscous Open Data: The flow of data in a public university governance ecosystemFrancois van Schalkwyk
This document summarizes research into the open data ecosystem surrounding public university governance in South Africa. The ecosystem involves data suppliers like the government department DHET and intermediaries like CHET. While DHET supplies some open data, it is not well integrated and lacks context, so uptake is limited. However, intermediaries provide open datasets with richer information that are used more widely. For the ecosystem to evolve further, the research argues the government needs to improve how it supplies open data to make it more interoperable and provide better documentation and tools to support use.
This document discusses careers in communication and public relations. It outlines typical career paths at public relations agencies and in corporate communication departments. For agency careers, it describes increasing levels of responsibility and compensation over time from assistant account executive up to CEO or president. For corporate careers, it outlines progressing from entry-level communication specialist to senior vice president of communication. The document also examines important skills for employers such as writing ability, strategy, leadership, and relationship building. It provides advice on gaining experience and developing skills through networking and mentorship.
Food & Faith: A Values-Based Approach for Community Food Security
Angela Smith, Baltimore Food & Faith Project
Pastor Heber Brown III, Pleasant Hope Baptist Church
Jenny Holmes, Ecumenical Ministries of Oregon
Cassi Johnson, Community Food Advocates
Five faith-based organizations and faith communities representing different traditions will share their work to support local farmers, develop community gardens, and increase healthy food accessibility. Attendees will be asked to share best practices from their own faith-based efforts and participate in structured small group discussions, each led by a panelist.
Developers should invest in 10 key skills in 2014:
1. Know a native mobile platform like iOS, Android or Windows Phone.
2. Know an agile development process and tools like Scrum, Kanban, or Extreme Programming using tools like JIRA, PivotalTracker or Trello.
3. Know how to effectively estimate tasks and leverage team techniques like story point estimation and velocity.
HTML5 is the latest version of HTML that provides native support for multimedia and graphics. It enhances HTML with new elements and APIs to build more robust web applications. While HTML5 offers advantages like cross-platform support and lower development costs, it also faces challenges from browser fragmentation and lack of access to device capabilities. Kony's platform aims to address these challenges by allowing developers to build HTML5 applications that can be optimized for all browsers and integrated with native device features.
Top 4 Cross Platform tools for Mobile App Developmenttechugo
Scope of Cross Platform App Development is bright as developers and engineers find it easy and interesting to use a single code base to compile and deploy their app on all major mobile platforms. Top 4 Cross Platform Development tools are discussed here in the presentation, with few of their major pros and cons:
Mobile Blast - Mobile strategy for developersJohn Jardin
John Jardin is a CTO who will discuss mobile development strategies. He will cover HTML5 vs native development, mobile web vs hybrid apps, and preferred tools like IBM Worklight, PhoneGap and Appcelerator. Key factors for choosing a development approach are the platforms targeted, offline needs, and hardware integration required. Best practices include using JSON, securing HTTP requests, local encryption, and applying an MVC strategy.
Deal with the dilemma of hybrid and nativeswamileo1
There are two kinds of platforms that can be used to build an app, Hybrid or Cross platforms and Native platforms. Hybrid and Native technologies have their own pros and cons although it is still debatable which framework is better.
The document discusses HTML5 and its potential for mobile application development. It provides an overview of HTML5, describing it as a standard based on open web technologies that allows developing applications once that can run on multiple devices. It outlines some of HTML5's key capabilities and components. It also discusses challenges with HTML5, such as browser fragmentation, as well as advantages like being cross-platform and lower maintenance costs compared to native applications. Finally, it presents options for HTML5 and native application development and argues that Kony's platform can help eliminate challenges with HTML5 like browser fragmentation and uneven performance across devices.
Facebook said no to HTML5 - but should you? This presentations cover the pros and cons of choosing to develop with HTML5. Find out if it is the right solutions for you.
The document discusses native mobile apps versus hybrid mobile apps. It provides an overview of advantages and disadvantages of each approach. Native apps provide better user experience but require separate development for each platform. Hybrid apps allow cross-platform development but can have performance issues. It also examines case studies of how LinkedIn, Facebook, and Dropbox developed their mobile strategies using both native and hybrid approaches.
This document discusses building native mobile apps using HTML5. It explains that HTML5 apps can be wrapped as native apps to access device functionality like the camera and run offline. The architecture involves PhoneGap wrapping HTML/JS code so it can run as a native app within a browser runtime. jQuery Mobile and Knockout.js are recommended for client-side code, while PhoneGap Build and services like TestFlight can help deploy and test apps. Debugging can be done using desktop browsers, simulators, and tools like Firebug Lite.
Enroll for Android Certification in Mumbai at Asterix Solution to develop your career in Android. Make your own android app after android development training in mumbai provides under guidance of expert Trainers. For more details, visit : http://www.asterixsolution.com/android-development-training.html
Post Windows Mobile: New Application Development PlatformsBarcoding, Inc.
Jack Nosek, Barcoding’s lead software engineer, reveals what application tools and platforms companies will employ with the next generation of mobile devices. During this session, Nosek compares HTML5, Xamarin, and Native development for iOS, Android, and Windows Phone/Embedded 8.1.
The document provides advice for new developers on how to get started building mobile apps. It recommends starting small by building a mobile web app prototype instead of a fully native app, as mobile web apps are easier to develop, can access many native features, and allow developers to test ideas and tweak the app more easily. Once the prototype is complete, it can be expanded into a larger project, turned into a full native or hybrid mobile app, or used as a sample for testing. The document stresses answering questions about the app's purpose and users before designing, and offers tips for user interface and experience design.
When Thinking about Developing Mobile Applications, business owners have one primary question in mind, what to choose between native vs. cross-platform. This is one of the most fundamental decision that has to be made, and is not easy. Check it out
How engaged are your customers, how do you know and why should you care? - To...Internet World
Digital Marketing Theatre - 17th June, 10:30-11:00
Personalised email content based on individual subscriber preferences is already widely used, but a quantified understanding of subscriber engagement is now emerging as a valuable new insight into past, current and most importantly future customer behaviour. This presentation explores some of the latest developments, applications and benefits of 'engagement' profiling.
The Council on Environmental Quality (CEQ) has taken several steps to increase transparency and comply with new FOIA guidelines from the President and Attorney General. These steps include revising FOIA regulations, implementing new procedures for processing requests, providing staff training, and increasing proactive disclosures by improving its online reading room. However, CEQ still faces some impediments to fully utilizing technology due to lacking internal IT support.
Creating an online community is important for the Howard League to connect with supporters and raise awareness of issues. They are reorganizing their website, developing blogs, and building online campaigns. Supporters can get involved by revealing themselves on the site, joining discussions, and spreading the Howard League's message that custodial sentences often fail to rehabilitate people and reduce reoffending.
This webinar provides an overview of what to expect at diabetes camp, including a typical daily schedule, registration procedures, homesickness prevention and treatment, diabetes management, and outstanding forms. It outlines a sample camp day consisting of wake up, activities, meals, testing blood sugar levels, and bedtime. The registration process uses stations to meet staff and get important information. Homesickness is addressed by keeping campers busy and reminding them of all the fun activities.
Viscous Open Data: The flow of data in a public university governance ecosystemFrancois van Schalkwyk
This document summarizes research into the open data ecosystem surrounding public university governance in South Africa. The ecosystem involves data suppliers like the government department DHET and intermediaries like CHET. While DHET supplies some open data, it is not well integrated and lacks context, so uptake is limited. However, intermediaries provide open datasets with richer information that are used more widely. For the ecosystem to evolve further, the research argues the government needs to improve how it supplies open data to make it more interoperable and provide better documentation and tools to support use.
This document discusses careers in communication and public relations. It outlines typical career paths at public relations agencies and in corporate communication departments. For agency careers, it describes increasing levels of responsibility and compensation over time from assistant account executive up to CEO or president. For corporate careers, it outlines progressing from entry-level communication specialist to senior vice president of communication. The document also examines important skills for employers such as writing ability, strategy, leadership, and relationship building. It provides advice on gaining experience and developing skills through networking and mentorship.
Food & Faith: A Values-Based Approach for Community Food Security
Angela Smith, Baltimore Food & Faith Project
Pastor Heber Brown III, Pleasant Hope Baptist Church
Jenny Holmes, Ecumenical Ministries of Oregon
Cassi Johnson, Community Food Advocates
Five faith-based organizations and faith communities representing different traditions will share their work to support local farmers, develop community gardens, and increase healthy food accessibility. Attendees will be asked to share best practices from their own faith-based efforts and participate in structured small group discussions, each led by a panelist.
Developers should invest in 10 key skills in 2014:
1. Know a native mobile platform like iOS, Android or Windows Phone.
2. Know an agile development process and tools like Scrum, Kanban, or Extreme Programming using tools like JIRA, PivotalTracker or Trello.
3. Know how to effectively estimate tasks and leverage team techniques like story point estimation and velocity.
HTML5 is the latest version of HTML that provides native support for multimedia and graphics. It enhances HTML with new elements and APIs to build more robust web applications. While HTML5 offers advantages like cross-platform support and lower development costs, it also faces challenges from browser fragmentation and lack of access to device capabilities. Kony's platform aims to address these challenges by allowing developers to build HTML5 applications that can be optimized for all browsers and integrated with native device features.
Top 4 Cross Platform tools for Mobile App Developmenttechugo
Scope of Cross Platform App Development is bright as developers and engineers find it easy and interesting to use a single code base to compile and deploy their app on all major mobile platforms. Top 4 Cross Platform Development tools are discussed here in the presentation, with few of their major pros and cons:
Mobile Blast - Mobile strategy for developersJohn Jardin
John Jardin is a CTO who will discuss mobile development strategies. He will cover HTML5 vs native development, mobile web vs hybrid apps, and preferred tools like IBM Worklight, PhoneGap and Appcelerator. Key factors for choosing a development approach are the platforms targeted, offline needs, and hardware integration required. Best practices include using JSON, securing HTTP requests, local encryption, and applying an MVC strategy.
Deal with the dilemma of hybrid and nativeswamileo1
There are two kinds of platforms that can be used to build an app, Hybrid or Cross platforms and Native platforms. Hybrid and Native technologies have their own pros and cons although it is still debatable which framework is better.
The document discusses HTML5 and its potential for mobile application development. It provides an overview of HTML5, describing it as a standard based on open web technologies that allows developing applications once that can run on multiple devices. It outlines some of HTML5's key capabilities and components. It also discusses challenges with HTML5, such as browser fragmentation, as well as advantages like being cross-platform and lower maintenance costs compared to native applications. Finally, it presents options for HTML5 and native application development and argues that Kony's platform can help eliminate challenges with HTML5 like browser fragmentation and uneven performance across devices.
Facebook said no to HTML5 - but should you? This presentations cover the pros and cons of choosing to develop with HTML5. Find out if it is the right solutions for you.
The document discusses native mobile apps versus hybrid mobile apps. It provides an overview of advantages and disadvantages of each approach. Native apps provide better user experience but require separate development for each platform. Hybrid apps allow cross-platform development but can have performance issues. It also examines case studies of how LinkedIn, Facebook, and Dropbox developed their mobile strategies using both native and hybrid approaches.
This document discusses building native mobile apps using HTML5. It explains that HTML5 apps can be wrapped as native apps to access device functionality like the camera and run offline. The architecture involves PhoneGap wrapping HTML/JS code so it can run as a native app within a browser runtime. jQuery Mobile and Knockout.js are recommended for client-side code, while PhoneGap Build and services like TestFlight can help deploy and test apps. Debugging can be done using desktop browsers, simulators, and tools like Firebug Lite.
Enroll for Android Certification in Mumbai at Asterix Solution to develop your career in Android. Make your own android app after android development training in mumbai provides under guidance of expert Trainers. For more details, visit : http://www.asterixsolution.com/android-development-training.html
Post Windows Mobile: New Application Development PlatformsBarcoding, Inc.
Jack Nosek, Barcoding’s lead software engineer, reveals what application tools and platforms companies will employ with the next generation of mobile devices. During this session, Nosek compares HTML5, Xamarin, and Native development for iOS, Android, and Windows Phone/Embedded 8.1.
The document provides advice for new developers on how to get started building mobile apps. It recommends starting small by building a mobile web app prototype instead of a fully native app, as mobile web apps are easier to develop, can access many native features, and allow developers to test ideas and tweak the app more easily. Once the prototype is complete, it can be expanded into a larger project, turned into a full native or hybrid mobile app, or used as a sample for testing. The document stresses answering questions about the app's purpose and users before designing, and offers tips for user interface and experience design.
When Thinking about Developing Mobile Applications, business owners have one primary question in mind, what to choose between native vs. cross-platform. This is one of the most fundamental decision that has to be made, and is not easy. Check it out
HTML5 or Android for Mobile Development?Reto Meier
Android apps or the mobile web? It's often a hard choice when deciding where to invest your mobile development resources. While the mobile web continues to grow, apps and app stores are incredibly popular. We will present both perspectives and offer some suggestions for making the most of each platform.
What Mobile Development Approach Makes SenseDipesh Mukerji
This document discusses different approaches to developing mobile apps: native, mobile web, and platform. Native apps are coded for specific platforms using languages like Objective-C or Java and have best performance but are not cross-platform. Mobile web apps live in the mobile browser and support multiple platforms but have slower speeds and less capabilities. Platform approaches use cross-platform frameworks like JavaScript to write once and deploy anywhere, offering performance and cross-platform support. The document analyzes the challenges and advantages of each approach and provides guidance on which to use based on factors like devices, budgets, and requirements. It promotes platform development using Kony for its tools and ability to build native, mobile web, and hybrid apps from a single codebase.
This document summarizes an experience report on developing mobile apps to access content from an Enterprise Content Management system using different technologies. It discusses using native iOS development with Objective-C, mobile web apps with jQuery Mobile, hybrid apps with PhoneGap, and cross-platform apps with Appcelerator Titanium. It finds that Titanium provides the best balance of native look and feel with multi-platform support and productivity. Future work includes generic browsing apps and business-specific mobile apps.
4. Answer
That depends…
• App complexity • Maintenance plans
• Target platform • Future scope and overall mobile
strategy
• Target audience
• Connectivity, storage,
• Development team strengths and synchronization, security…
experience
www.intelliware.com 4
5. Know you’re purpose
If you’re not ready to answer questions about why you’re
building
b ildi a particular mobile app you’re not ready t
ti l bil ’ t d to
answer the questions of Native vs HTML 5.
www.intelliware.com 5
6. Know you’re purpose
• Who is the app for? • Who will develop the app?
• Internal audience? • Internal or outsourced team?
• C t
Customers? ? • T
Team language/platform experience?
l / l tf i ?
• Both?
• Who will maintain the app?
• What is the value proposition? • Same as development team?
• What problem does the app solve?
p pp • Hours available for maintenance per
p
• Why do users open it? week?
• What are it’s essential functions? • How are support issues handled and
funnelled?
• How will the app be used?
• O li / ffli ?
Online/offline?
• How will t e app e o e
o the evolve?
• In the field, office, home, on the road? • Is app one-off or part of larger mobile
strategy?
• Local vs cloud data? • Will future versions be released?
• Are new features already in the pipe?
www.intelliware.com 6
7. Managing Different Forces
• Prioritize Your Questions in Context
• Is the UI/UX plan flexible or set in stone?
• Does your development platform support all planned app features?
• Is your development team comfortable with the development platform/environment?
• Do your current software development lifecycle practices fit with your development
platform choices?
www.intelliware.com 7
8. Technology Considerations
• Using native functions of the device. (GPS, Camera, Accelerometer)
• More native functions, like GPS are being exposed through HTML/Javascript bridge – stay up-to-date on what can
and cannot be done when you choose native vs HTML vs some MADP platform.
y
• Open GL and other low-level UI control
• Game developers typically choose native development and will look to get a value of code re-use by using C++
libraries that can be compiled for the different mobile platforms such as Cocos 2d.
• Offline reliable and secure local storage
Offline,
• HTML 5 does provide local storage but you need to be aware of how this compares to other local storage options in
terms of meeting the project requirements, especially around security and reliability
• Actual speed of development to achieve desired UI
• If the UI relies heavily on native widgets looking like native widgets, this can require a lot of fussing to achieve in
y g g g , q g
JQueryMobile or Sencha Touch versus the seconds it takes to create the same look using the native IDE UI tools.
• If the UI relies heavily on a custom look that bares little resemblance to any native UI widgets it could be easier to
achieve in HTML 5 than it is to customize native widgets. (Of course that will depend on the different native platforms
and the widgets involved.)
www.intelliware.com 8
9. Technology Choices
HTML 5
Strictly speaking you can choose to HTML 5 for your mobile applications
and not use any 3rd party libraries. You can write y
y p y your javascript, css, and
j p, ,
HTML to produce your mobile application and you will likely end up with
something that is exactly what you want with an architecture that suits your
needs. However you will not have saved much time or money. When we say
HTML 5 we really mean choosing an HTML library to jumpstart our
development effort:
• Common Libraries
• JQuery Mobile
• Sencha Touch
• Dojo Mobile
• Meteor
www.intelliware.com 9
10. Technology Choices
Native
Native apps typically refer to apps written using the native SDKs of the OS
providers. In some cases the OS provider has provided multiple SDKs, in which
case native refers to the SDK that compiles directly to the device chip
architecture:
• Common Native Languages
• iOS – Objective C and C and C++
• Android – Java, C and C++
• Windows Phone 8 – .Net, C and C++
• Blackberry 10 – C and C++
y
Native app development can also be accelerated using 3rd party libraries, such
as the Cocos 2d library for game development, which can used cross-platform.
www.intelliware.com 10
11. Technology Choices
Hybrid
Hybrid typically refers to an app that uses a mix of Native code and HTML 5
in order to deliver features There are different approaches to hybrid:
features.
• Hybrid approaches
• Native app wrapper where all the real development work is in HTML 5 which is served up
by a nested native Web View widget Wrapping the native app allows the app to be
widget.
distributed through the App Store and it allows the app to communicate with native API’s
through a Javascript bridge.
• Native app with embedded HTML used for less interactive content to get some reuse of
code across platforms while still d li i a primarily native f li app.
d l tf hil till delivering i il ti feeling
• Native with HTML content pushed to app allowing app content, functionality and look and
feel to all be updated without putting the app through a store review. (Depending on the
type caching involved this will require extra connectivity logic.)
www.intelliware.com 11
12. Technology Choices
MADP (Mobile Application Development Platform)
People always ask Native vs HTML 5 but the real question behind that question is usually “What’s
the quickest, cheapest, fastest, best way to deliver a mobile app across ALL my channels and
make ALL my customers/employees/users happy?”
Other’s in the mobile space have built products that attempt to be the solution to this question:
• Worklight
• Brings together other tools like Sencha Touch and Cordova and automates how they all stitch together. Includes
server to facilitate building backend connectors for enterprise integration.
• Kony
• Proprietory tool built in India that uses Javascript or Lua as the primary development language and produces native
or HTML 5 output. All Kony apps require a Kony server (like Worklight) and a key area of focus (like Worklight) is
enterprise services integration.
• Cordova (formerly Phone Gap)
• Opensource Apache project. Early Phone Gap projects were criticized by users for failing to provide a decent UI
experience. (Original O’Reilly iOS app built by the Phone Gap team is an example of one such failure.)
• Appcelerator
• You write in Javascript and it generates native apps.
www.intelliware.com 12
13. Costing Your Solution
Many people assume 3 platforms means taking the estimate for 1 platform
and multiplying it by 3. This doesn’t hold.
py g y
• Team experience
• Do you have developers experienced at your native platforms?
• Do you have developers experienced in y
y p p your MADP or in HTML 5 and all the technologies
g
those will entail. (Javascript, CSS, HTML, etc.)
• Porting or rewriting apps is faster
• Experience shows us that once a p j
p project is complete it is often faster to rewrite
p
• Do App features match well with Development Platform
• Make sure you and your team have an idea of how you will build each feature, some
features will be quick to develop using one platform while slow to develop using another
www.intelliware.com 13
14. Other Factors
• Testing
• Unit testing and Integration testing are both areas that complicate the technology choices faced
when choosing between HTML 5, Native, Hybrid and a MADP for mobile development.
• Home-grown testing solutions can become brittle and break as Apple, Google, Blackberry and
Microsoft evolve their toolsets and SDKs.
• Server
• W kli ht and K
Worklight d Kony b th provide a server piece f all apps. Th f
both id i for ll The focus i on enabling enterprises t
is bli t i to
expose complicated and heavy backend services through mobile APIs, so for apps that require this
type of backend integration the question becomes less about Native vs HTML 5 and more about
how easy it will be to provide that backend integration.
• O
Other Requirements
• Requirements outside the scope of specific app features may also influence choices. Today, choices
need to be made in the context of the entire Mobile Strategy for an enterprise, not isolated to
considerations about a specific app.
www.intelliware.com 14
15. Bake-Offs
One way to assess your technology choices is a bake-off. Create a small
POC (proof of concept) p j
(p p ) project and split y
p your dev team into 2 or more
smaller teams and have them build the POC using your different platforms.
• Pros
• Prove out whether platform will support desired features
• Assess actual speed of development
• Cons
• Adds to costs because now you need time in your project to do the bake-off and assess the
bake off
results
• A bake-off may not be long enough or complicated enough to truly evaluate platform and
may provided a skewed view of the world
www.intelliware.com 15