Mobile Apps Development Articles


Several open source frameworks have come and gone over the past few years. Now that the dust has settled a bit, there are four top choices: Ionic, React Native, NativeScript, and Xamarin. The Ionic framework provides the ability to cover the most amount of platforms with a single codebase: web apps, mobile apps, progressive web apps (PWAs), and desktop apps (via Electron.js). Ionic apps are built on top of Angular, which means you’ll need to learn it first along with Typescript. Facebook’s React Native is another option. Apps are written in JavaScript, but instead of using web components like “div” or “span”, native components like “View” and “Text” are used, producing a real native mobile app. This approach provides great performance but means that the code can only be used for mobile apps. Telerik’s NativeScript is another neat option. Apps are written in Angular, TypeScript, or plain JavaScript, then compiled into native code. You’ll need to learn their custom UI layout mechanism (tags such as “<Page>”, “<Image>”, etc. get converted into a specific native representation), but otherwise will reuse your existing JavaScript skills. Microsoft’s Xamarin framework is a bit different than the others — apps are written in C#. This is great for .NET developers looking to try their hand at mobile development. As with React Native and NativeScript, the C# code gets transformed into a native representation. - done reading - done reading - Compare Adobe PhoneGap, AppGyver Steroids, and Telerik Icenium - done reading - done reading - done reading - done reading - Web Development For The iPhone And iPad: Getting Started - done reading - done reading - done reading

App Generator
App Maker



Firefox OS:

Email Design:

Intel Edison:


Backend As A Service:


Amazon: - done reading

LinkedIn: - done reading - Mobile Web Apps: Loading Pages - Why and How to Make Your Website Mobile Phone Compatible - 9 Mobile Framework to Kick Start Your Mobile Development Career - Mobile Sites vs. Media Queries - Making It a Mobile Web App - Avoiding Web Habits in Your iPhone Apps - Mobile First: One Year Later - 10 great mobile web site builders - Mobile Web Design: Tips and Best Practices - A Quick Look at Mobile Web Designs - The touch action (from quirksmode) - Persistent touch event objects - PINT CEO Talks Mobile Web Development - Best practices for mobile Web application development - Building Mobile Web Applications: A Tutorial - Mobilize Websites & Applications Gears on Mobile Devices - Designing and Developing for the Rich Mobile Web - Video: Rich & Mobile Form Design - Mobile browsers list and test advice - Prevent Page Zooming in Mobile Browsers - The Tangible Web: Thoughts on Designing Websites for Touchscreens - A tale of two viewports — part two - Flexible, Mobile-First Layouts with CSS3 - Designing For The Modern Day Mobile Market - Audio: Mobile First! - Video: Mobile First! - Data Monday: Location Based Services - Mobile Device Capabilities: Updated - Designing for the Retina Display (326ppi) - Mobile web conferences: Mobilism and Breaking Development - Mobile Application vs. Mobile web and Where Mobile is Headed - Choosing an Approach to Mobile Development - Data Monday: Mobile Apps vs. Mobile Web


IBM Worklight:


Apache Cordova / PhoneGap:


Intel XDK:

Codename One:





iPhone: - Optimizing Web Content



Ruby Motion

Sencha Touch:

jQuery Mobile:

MoFuse: How to Create a Mobile Site with MoFuse - MoFuse – Create a Mobile-Friendly Version of Your Website

Making your web site mobile friendly: - Make your Site Mobile Friendly - Make Your Site Mobile-Friendly in Two Minutes - How to Create a Mobile Version of Your Website - How to Create a Mobile Version of your Website - Create a Mobile Site Designing for the Mobile Web - Convert your site to a friendly mobile viewer - Coding for the mobile web - Mobile Web Design





Offline first:









Testing: - How to make a mobile app in 25 min - For FREE! - InfiniteMonkey - done reading - done reading

Marketing and Monetizing:

What are the steps involved in making an app?

  1. Define Your Goal - define the purpose and mission of your mobile app. What is it going to do? What is its core appeal? What concrete problem is it going to solve, or what part of life is it going to make better?
  2. Start Sketching - By developing sketches you are laying the foundation for your future interface. In this step you visually conceptualize the main features and the approximate layout and structure of your application. Having a first rough sketch of your app helps everyone on your team understand the mission. These sketches should be used as reference for the next phase of the project.
  3. Research - This research has four main purposes:
    1. Find out whether there are other apps doing the same thing
    2. Find design inspiration for your app
    3. Find information on the technical requirements for your app
    4. Find out how you can market and monetize your app
  4. Create a Wireframe and Storyboard. In this phase your ideas and features fuse into a clearer picture. Wireframing is the process of creating a mockup or prototype of your app. You can find a number of prototyping tools online. The most popular ones are Balsamiq, Moqups, and HotGloo, which allows you to not only drag and drop all your placeholders and representative graphics into place, but also add button functionality so that you can click through your app in review mode. While you are working on your wireframes you should also create a storyboard for your app. The idea is to build a roadmap that will help you understand the connection between each screen and how the user can navigate through your app.
  5. Define the Back End of Your Mobile App. Your wireframes and storyboard now become the foundation of your back-end structure. Draw a sketch of your servers, APIs, and data diagrams. This will be a helpful reference for the developer, and as more people join the project you will have a (mostly) self-explanatory diagram for them to study. Modify your wireframes and storyboard according to technical limitations, if there are any.
  6. Test Your Prototype. Revert to your wireframes and ask friends, family, colleagues, and experts to help you review your prototype. Grant them access to the wireframe and have them give your app a test run. Ask them for their honest feedback and to identify flaws and dead-end links. If possible, invite them to your studio and have them try out the prototype in front of you. Monitor how they use the app, taking note of their actions and adapting your UI/UX to them. The goal is to concretize your app concept before it goes into the design process! Once you start designing it is much harder to change things around, so the clearer the prototype from the start, the better.
  7. Build the Back End of Your App. Now that your app has been defined pretty clearly, it is time to get started on the back end of your system. Your developer will have to set up servers, databases, APIs, and storage solutions. Another important thing on your to-do list at this stage is signing up for developer accounts at the app marketplaces you are developing for. Getting your account approved may take several days (depending on the platform) and shouldn’t be left to the last minute.
  8. Design the App “Skins”. “Skins” are what designers/developers call the individual screens needed for the app. Your designer’s job is now to come up with high-resolution versions of what were previously your wireframes. In this step it is crucial to include all comments from your prototype testers (see Step 6). After all, you are trying to build an app your target audience is actually going to use, therefore their feedback should guide you toward to the perfect UI-User Interface.
  9. Test Again (Yes, Again). Once your designer has completed the design skins, you’re up for another round of testing. Don’t think that you are all set with what you’ve done so far. For the first time you have your actual app concept completely in place, all the graphics inserted, and all text as it should be. Which means you can finally test your app in the way it will really look and feel. To test your app, two great testing apps come to mind: Solidify and Framer. These apps allow you to import your app designs and add links where needed to test the flow from screen to screen. Don’t confuse this stage with Step 6 (wireframing). At first it was about creating the basic look and feel of the app. Here you’ve implemented the actual design and made it clickable.
  10. Revise and Continue to Build. Once you’ve given your design a test drive and collected more feedback from future users, you should use these new ideas to polish your app idea. You can still ask your designer to change the layout, and you can still tell your developer to change something on the back end.
  11. Refine Each Detail. As you continue to build you will want to have a constant look at your new app. On Android, for example, it is easy to install your app file on a device to test its functionality in a live environment. iOS is different. There you will require a platform like TestFlight to download and test your app as it proceeds. This step is the last step in the app development process. You can monitor your app all the way until your product is complete.
  12. Release Time! App marketplaces have very different policies when it comes to publishing a new app. Android, for example, does not review newly submitted apps right away. They’ll pass by at some point and check it out but you are able to instantly add your app to Google Play.

While you may think that you have a revolutionary idea, you may get your hopes crushed very quickly. There are more than 1 million apps for Android and iOS, so building something that hasn’t been done before is nearly impossible. Nonetheless you must not get discouraged by those who may playing in the same arena. It is imperative that you focus on your own project and your user acquisition. Learn from the key features and mistakes of your competitors, and drop all other thoughts about them.

This is also the right time to look into the technical aspects of your mobile app. Find out what your requirements are and get a clear picture of whether your idea is truly feasible or not from a technical standpoint. In most cases there will be an alternative solution to proceed on a slightly different route. This research extends into legal restrictions like copyright and privacy questions, giving you a complete understanding of your situation.

If you have connections in the industry, get an expert opinion on your idea right from the start.

Two other important points are marketing and monetization. Now that you have confirmed the feasibility of your app, you should think about your strategy of getting it out onto the market. Determine your niche — know exactly how you can reach your target user and how you need to approach him to make him see the value and use the app.

Another important consideration is figuring out how your app is going to generate money. Will you charge your user to download it? Or will you offer the app for free but run ads on it? This model would require a large user base, so think about that as well. There are various ways to monetize an app and it is up to you to decide on the channel you want to use.

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License