Chapter 14

Sharing Business Logic between Applications

What's in this Chapter?

  • Establishing an enterprise library of reusable components
  • Sharing business logic code across architectures
  • Planning for portability of app code to other platforms
  • Standardizing on JavaScript interfaces for hybrid apps
  • Taking advantage of custom URI schemes
  • Creating a suite of interconnected iPad applications

The last chapter examined the various languages, development environments, and technology stacks that can be used to create iPad applications.

In this chapter, you're going to examine some of the enterprise iPad app development best practices.

First, you'll cover the design and use of reusable enterprise software libraries and components, to simplify development and to standardize on things like authentication or encryption for security or utilities like logging or analytics.

Then, you'll outline how applications can be designed to allow for flexibility across architectures, as well as future portability to other platforms if that were to become necessary. Establishing standards for hybrid application development will also be covered.

Finally, you'll look at custom URI schemes, and how that can be used to not only provide deep-linking into your iPad applications, but also facilitate the creation of a robust suite of apps.

Using Reusable Components

Independent of the architecture and technology stack that you choose to develop your enterprise iPad apps, it is a good idea to logically design and ...

Get iPad® in the Enterprise: Developing and Deploying Business Applications now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.