How to Choose Right Technology for your Mobile Projects
•Download as PPTX, PDF•
2 likes•378 views
How to Choose Right Technology for your Mobile Projects, Mobile development strategies, Mobile development principles, choose right programming language for your mobile projects,hybrid development.
More Related Content
What's hot
What's hot (9)
Similar to How to Choose Right Technology for your Mobile Projects
Similar to How to Choose Right Technology for your Mobile Projects (20)
Recently uploaded
Recently uploaded (20)
How to Choose Right Technology for your Mobile Projects
- 1. How To Choose Right Technology For Right Project By Safil Sunny
- 2. About Me ! Lead Developer | Solutions Architect | Certified ScrumMaster® (CSM) in Mobility twitter.com/safilsunny in.linkedin.com/in/safilsunny Blog :- www.safilsunny.com
- 4. 1. Does your app requires device features ?
- 5. 1. Does your app requires device features ? 2. Your Budget ?
- 6. 1. Does your app requires device features ? 2. Your Budget ? 3. How frequent you need Connectivity ?
- 7. 1. Does your app requires device features ? 2. Your Budget ? 3. How frequent you need Connectivity ? 4. What are the devices you target ?
- 8. 1. Does your app requires device features ? 2. Your Budget ? 3. How frequent you need Connectivity ? 4. What are the devices you target ? 5. What is your development team skill set ?
- 9. 1. Does your app requires device features ? 2. Your Budget ? 3. How frequent you need Connectivity ? 4. What are the devices you target ? 5. What is your development team skill set ? 6. What performance your application expects ?
- 10. A GOOD APP STRATEGY SHOULD CONSIDER
Editor's Notes
- ----- Meeting Notes (08/10/15 10:00) ----- What are the things need to be considered when you choose a technology to develope a Mobile App?
- ----- Meeting Notes (08/10/15 10:01) ----- Acelerometer , pedometer, health kit etc
- ----- Meeting Notes (08/10/15 10:07) ----- Development Cost, maintenance Cost
- ----- Meeting Notes (08/10/15 12:22) ----- always connected, i like offline, limited
- ----- Meeting Notes (08/10/15 12:22) ----- target all the devices in the world, only apple device,only android device, only phones, only tablets.
- ----- Meeting Notes (08/10/15 12:22) ----- HTML 5, Javascript, Css, objective C, java, konny , appcelerator , ionic etc.
- ----- Meeting Notes (09/10/15 23:35) ----- HTML 5 Pros The app can be developed to work across a number of platforms and form factors from a single codebase. This can include mobile, tablet and desktop if following a responsive design approach. The app is accessed from a device’s browser, so there is no need for app store/market place certification. Updates and maintenance releases of the site can be deployed immediately as opposed to waiting for app store/market place approval before delivery to the end user. Although the base technology does not provide a mechanism for monetisation, the publisher is able to monetise the app/service through a subscription model and retains 100% of the income. The app can run offline through browser caching. The app can access a device’s local storage and local database.. Cons At this point in time, not all browsers have implemented HTML 5 features equally, so developers may need to provide workarounds. Access to device hardware is limited: at present there’s support for GPS, limited support for compass and accelerometer (depending on browser), and no support for camera and microphone. Not all browser vendors provide standardised support for accessing a device’s local database. Access to a device’s address book, email and applications is not supported. Bypassing app stores/market places reduces the visibility of an app (though considering the vast number of applications published application developers/publishers need to market their applications beyond simply publishing them to an app store/market place). Gestures and touch input will need to be implemented by the developer (third party frameworks such as Sencha Touch do exist – though not every framework works across all platforms). Hybrid Pros These hybrid applications are published through app stores/market places so benefit from increased visibility and can also be monetised. The code base works across platforms, however in some circumstances the presentation layer may need to be adapted for each platform. This approach reduces the cost of delivering an application across a number of mobile platforms. Hybrid apps can access device APIs and sensors – though not all third party frameworks provide equal access. Once installed locally on a device the application behaves the same as a native application. Cons In some circumstances hybrid applications may appear to run slower than native applications due to the implementation of the JavaScript runtime hosted in an embedded web browser. Gestures and touch input will need to be implemented by the developer, although third party frameworks like Sencha Touch do exist (though not all frameworks work across all platforms). Native Pros Native app are optimised for device hardware CPU/GPU. Gestures and touch input are provided through a device’s SDK and controls. Simple and easy display of data in a variety of user controls, out of the box. These apps have access to device APIs and sensors. Native apps are published through app stores – this increases the visibility of an app, and means that the app can be monetized. The apps is installed locally and has no external dependencies. Cons Native apps are built for a single platform only.For multi-platform support the developer/publisher will need to port the application across to other desired platforms, which requires more development time and impacts the cost of production.