Learnings from Early Native Apps Improve HTML5 and Hybrid Apps

January 28th, 2014 |
Image for FaceBook
Download PDFRead/Download White Paper (PDF)
Share this post:
Facebook | Twitter | Google+ | LinkedIn | Pinterest | Reddit | Email
This post can be linked to directly with the following short URL:

This pdf file can be linked to by copying the following URL:

Right/Ctrl-click to download the pdf file.
Connected Social Media - iTunes | Spotify | Google | Stitcher | TuneIn | Twitter | RSS Feed | Email
Intel - iTunes | Spotify | RSS Feed | Email
Intel IT - iTunes | Spotify | RSS Feed | Email

IT Best Practices: Over the past two years, Intel IT has validated and improved its mobile application development framework, Focusing first on native development, we identified best-known methods (BKMs) that we used to refine our framework and applied these methods to emerging development technologies.

We then conducted a pilot project to deliver increased productivity. In the process, we successfully overcame the technical challenges we had encountered during earlier mobile application development efforts. We also identified several BKMs for native development, which we are now applying as we shift our focus to newer emerging and maturing technologies. These methods include the following:

  • Componentization. Our practice is to componentize mobile applications and connect features to back-end services for all delivery mechanisms.
  • Reusable libraries. We developed reusable native libraries and ported them to the Web/HTML5 and hybrid delivery mechanisms.
  • Creative solutions. Shifting our thinking from desktop and notebook applications, we explore creative ways to meet mobile development needs.
  • Best delivery mechanism. We consider the business needs of the mobile application, weighing the advantages and disadvantages that each delivery mechanism provides.
  • Third-party integration. Taking our lessons learned in connectivity and security, we educate our third-party suppliers on how to integrate with our back-end services while traversing our firewall.
  • Collaboration. Working together to streamline mobile application development, we collaborate and benefit from each other’s work.
  • By having one strategic direction and common resources, we are able to eliminate duplicate efforts and improve the process overall.

    For more information on Intel IT Best Practices, please visit intel.com/IT

    Tags: , , , , , , , , , , , ,
    Posted in: Corporate, Intel, Intel IT, IT White Papers, IT@Intel