Skip to main content

Picking A Mobile Technology Stack




  • There are many ways to create an app but we want to examining the importance and adoption level of different tools and tool-stacks to create a mobile application.
  • The new mobile technology stack includes everything from traditional technologies such as backup and data loss prevention to emerging application development platforms and management suites.
  • Typically, every mobile app project requires consideration based on its own merits.
  • If the apps are specialized enough to require Native iOS and Android/Java development skills, some portion of these can be made in-browser web apps optimized for mobile.
  • Some of the following consideration get matters to design mobile application stack

  1. Front end and Services support
    1. Pick a technology solution that supports your front end (UI) and middleware needs.
    2. Most all mobile apps have a UI component and a services tier. Based on their origins, certain software tools tend to have strengths in one area vs another.
  2. Deployment Flexibility
    1. Give yourself the flexibility of deployment - on-premise, private cloud, hybrid and public cloud.
    2. From an application suitability standpoint, some applications are better suited as behind-the-firewall apps while others are good for cloud usage.
    3. Cloud suited applications include those that have data that may not be as sensitive, or have traffic patterns that are hugely variable.
    4. Apps with relatively constant workloads that need to be maintained over longer periods of time tend to be better suited for on-premise deployments.  
    5. Also, applications may start their life cycle deployed on a public cloud, and as it matures, the business may decide to bring it in-house and host it in an internal datacenter.
    6. Applications may also need to support a hybrid deployment model that allows cloud capacity to augment dedicated capacity during peak workloads.
    7. While applications transition through these states often, most application development platform alternatives provide solutions that are either cloud offered (SaaS), or usable on-premise, but are seldom optimized for both.
    8. While on-premise runtimes can be deployed in a VM on cloud, true built-for-cloud offerings support cloud optimized scalability by adding VMs. They typically use stateless architectures to support this kind of scalability.
  3. Native App vs Hybrid App vs Web App
    1. There’s More Than One Way to Build Mobile Apps
    2. There are three major ways to build your mobile app: Native, Web and “Hybrid.”
    3. This factor depends on business strategies and your target audience.(For more details go to here.)
                            

  1. Scalability
    1. In the world of application development, speed to delivery is often inversely proportional to the suitability of the solution for enterprise scalability.
    2. While developer productivity tooling that is used for speedy delivery drives out time to go-live, it often does so making general purpose assumptions about service and schema architecture that falls short when it comes time for scale out.
    3. While making a technology choice, decision makers need to evaluate their solution to ensure that it allows customization of the right application tiers to meet specific needs of the solution.
  2. Skills
    1. Native iOS and Android development skills tend to be expensive and hard to come by, while developers with Javascript/HTML5 skills are relatively inexpensive.
    2. Your choice of application development technology should be driven by your cost of development.

  • A tech stack is a combination of software products and programming languages used to create a web or mobile application which is based on above consideration.(For more details go to here).

Comments

Post a Comment

Popular posts from this blog

What exactly means MVW design pattern ?

What is a MVW framework? The abbreviation stands for 'Model - View - Whatever'.  Well there are many different JavaScript frameworks available , all invented for the same purpose. They all try to separate the presentation logic from the business logic where JavaScript holds the model and logic, and html the presentation layer. Quick overview : You can change the model without changing the view and vice-versa Unit testing is easy These are the core benefits of using such a framework. By separating presentation and business logic changes to the code are easier to implement and take less time. Another benefit is that code can be reused from a controller thus saving more time. Angularjs makes the code also shorter in comparison to other frameworks, which improves code stability. Less code means minor potential for bugs. For several years +AngularJS was closer to MVC (or rather one of its client-side variants), but over time and thanks to many refactorings

File Upload & Download With ng-cordova File Transfer Plugin In Ionic Framework

Using the AngularJS extension set , ngCordova , with Ionic Framework and the Apache Cordova File Transfer plugin, you can easily upload files to a remote server and download files from a remote server. 1.Create the project ionic start Test blank cd Test ionic platform add android 2.Add Plugin org.apache.cordova.file-transfer https://github.com/apache/cordova-plugin-file-transfer This plugin allows you to upload and download files. This plugin defines global FileTransfer, FileUploadOptions Constructors. Although in the global scope, they are not available until after the deviceready event . Installation cordova plugin add cordova plugin add cordova-plugin-file-transfer     2.    org.apache.cordova.file             https://github.com/apache/cordova-plugin-file             This plugin implements a File API allowing read/write access to files residing on the    device.             Installation cordova plugin add cordova-pl

Steps To Create Cordova Plugin

Introduction A plugin is a package of injected code that allows the Cordova webview within which the app renders to communicate with the native platform on which it runs. Plugins comprise a single JavaScript interface along with corresponding native code libraries for each supported platform. Due to following reason, we will go for plugin development To get the native capabilities of the device in the cordova based app Build the common functionality across the number of Cordova application(Reusability) Prerequisites For the creation of plugin you need to install plugman . npm install -g plugman Plugin Structure Decide Plugin ID & Name The plugin ID should be unique Plugin name should follow the convention “cordova.plugin.[your.plugin.name]” Create the structure Use the following command to create the plugin with plugin ID “cordova.plugin.test” and name “Test”. plugman create --name Test --