Human_Centered_Mobility

Antenna Software, Inc., 111 Town Square Place, Jersey City, New Jersey 07310

phone 888.723.2832 web antennasoftware.com 1

function is the core vision that has, finally, taken us into true 21st century mobility.

The central tenet of the form and function mantra is that a) humans sit within the space defined by form and function and b) very closely and personally interact with their devices within that space. Truly hundreds of thousands of mobile apps now occupy this space – and the number is growing at an alarming rate - where device and mobile application form and function collide with user location, context, and preferences. Mobility has become pervasive, and mobile users are no longer defined purely as workers, consumers, customers or partners – they are people! People with unique likes and dislikes. Individuals with specific cultural and social backgrounds. Human beings with real wants and needs.

The goal of this paper is to dive into this exciting discipline of intelligently interacting with mobile users that has flipped our culture on its head in such a short period of time. We refer to this discipline as working within ‘the last mile of mobility’ – where it’s much less of a technology story and much more

Human Centered Mobility

SM

PreAMble

The original Apple iPod was successful on many levels. Among the more interesting of these levels - and leaving the ‘music’ end of it completely to the side - were two key factors: first, the small form factor, and the simple physical look and feel of the devices; and the user interface – which was strikingly different, and both visually and physically appealing. Form and function came together in an inspired moment that not only changed the music industry, but that also created enormous new expectations for electronic gadgets.

Then along came the iPhone – yet another revolutionary device, once again delivered complete with a strikingly different, visually and physically appealing look and feel that instantly changed the meaning of form and function for mobile devices.

Not to belabor the point, but we can also look to the iPad – certainly far less revolutionary in form and function (it wasn’t hard to guess what the iPad would end up looking and feeling like), but relative to ‘old school’ laptops, tablets and netbooks, revolutionary none the less. That Apple has managed to sell approximately 10 million of them at the time we write (early January, 2011) and with projections for sales of over 45 million in 2011, strongly suggests that the form and function mantra continues to rule the day.

That brings us to the sophisticated mobile applications that now run on the new Research in Motion (RIM) OS 6.0 devices, RIM’s new QNX-based PlayBook, Android devices, the iPhone, WebOS, and Microsoft’s new Windows Phone 7 OS and hardware. Software and hardware built around form and

We summarize our set of design ideas, and their real-world manifestations both within and outside of the enterprise, as ‘Human Centered Mobility.’

Your users Are Your Guides to buildinG trAnsforMAtive Mobile enterPrise APPliCAtions



about how and why people interact with their devices and mobile technologies (we’ll get to this in detail later on). In short, the goal becomes to deliver enterprise mobile applications that are every bit as engaging and wonderful to use as their consumer counterparts.

There are two distinct factors today that drive our ability to apply form and function to mobile application design and in turn to deliver on Human Centered Mobility (HCM). The first of these is simply today’s mobile technology. The second is role-based mobility.

todAY’s Mobile teCHnoloGY

The first critical factor in developing mobile apps is the technology itself. For example, the Antenna Mobility Platform (AMP) allows developers to get up close and very personal with any mobile device:

Special features of a given mobile device (GPS, •accelerometer, magnetometer, etc.) and the means a mobile OS provides to access these special hardware features are now simple to tap intoBackend data across multiple backend app servers and •databases is now easy to accessBusiness process modeling is a snap to capture, test, and •execute againstMobile applications that • do not compromise either role-based business process complexity or the UI capabilities one expects from applications running on laptops are fully attainableThe ability to model and build any application once, then •deploy to each specific device and mobile OS type, with each app fully optimized to take advantage of the rich and unique capabilities of every device and mobile operating system platform. This is a critical point for HCM design. ’Build once deploy to any’ does not mean creating suboptimal apps to a common denominator that

fails to take advantage of each platform’s special and unique capabilities. HCM design principles demand that the unique capabilities of every device and platform be utilized to their fullestThe capabilities of HTML5 for quickly building state of the art •Mobile Web apps are easily tappedThe ability to • extend HTML5 development to capture unique mobile device capabilities (e.g. an accelerometer)

Developers gain significantly from new mobile Web technology. In particular, HTML5 opens application doors formerly limited to fully-connected desktop browsers. HTML5 delivers device-based data persistence and an on-device database, the ability to easily push data out to a device, and (because of on-device data persistence), the ability to work offline when a device is not connected to a wireless network.

When combined with AMP, enterprises become fully empowered to deliver HTML5-based mobile Web applications that are able to deliver enterprise-grade security and provide full device and application manageability.

To be sure, there are tradeoffs between HTML5-based and native-built applications, and native applications will always offer more capability. It is, though, outside the scope of this paper to elaborate on these differences. Refer to the Resources section at the end of this paper for additional information. Suffice it to say that both types of mobile applications will deliver HCM-based applications that your workforce will love to use.

role-bAsed MobilitY is tHe Golden rule of HCM

The second key factor behind HCM is what we refer to as ‘Role-based Mobility.’ At its simplest, this means that mobile applications are able to deliver on the specific needs of any given workforce segment. A more detailed view includes consideration of the following – what we refer to as the ‘4Cs’ of mobility:

Context • (location, presence, social groups, environment




and usage patterns)Content • (dashboards, documents, video, audio, spreadsheets)Collaboration• (social networking, information circulation and sharing, blogging)Commerce• (billing, banking, trading, supply chain, business partners)

Whether employee-, partner-, customer- or consumer-facing, to insure that full role-based capabilities are taken into account as part of HCM, all new enterprise and consumer-facing mobile application designs must take these ‘4Cs’ into consideration.

The 4Cs are intimately related to each other and to HCM, and it is critical to understand the relationships between them and your mobile app users. The 4Cs aid greatly in defining user roles and establish how your mobile apps will allow your users to interact with fellow employees, as well as business partners and your customers to interact with your business.

There is nothing particularly new about the 4Cs in and of themselves. Many of the capabilities listed above have evolved over time through desktop use. However, the critical difference today is our ability to tap into any – and multiple - aspects of the 4Cs anytime and anywhere through mobile technology. Understanding how different segments of your workforce – sales, field service, marketing, and so on – operate and interact in real time must be reflected in the development of any mobile application.

The last issue we’ll touch on here regarding the 4Cs is the issue of workforce generations. Baby boomers – many of whom are technology savvy (including in the use of mobile technology) – are quickly leaving the workforce. As tech savvy as they are, baby boomers are not significant users of every one of the 4Cs. 4C demand is subsequently fairly low among them.

Generation X and Generation Y, however, are not only fully versed in every aspect of the 4Cs, but in fact both anticipate and demand that the 4Cs are included as core features of the mobile applications

they intend to use. As such, every workforce segment must have, based on their roles, their appropriate 4C pieces fully implemented in their mobile apps (e.g. road warriors need their GPS and LBS services, executives need their business intelligence dashboards, marketing teams need their collaboration, and so on).

The 4Cs are also central to social/business networking. Baby boomers are not particularly interested in utilizing social networking; however they are inexorably leaving the workforce and they are not drivers of 4Cs-based social/business networking. For Gen X and Gen Y 4Cs-based social/business networking is a critical requirement.

tHe Mobile APPliCAtion PlAtforM (MAP)

Behind the scenes, all successful mobile application deployment in today’s enterprise world - whether deploying a mobile cloud model or an on-premise solution - requires a powerful mobile development platform, such as that shown in figure 1 on the following page. By deploying mobile applications through a MAP we no longer need to worry about the deep technical nuts and bolts of mobile platforms and how they operate.

Gen X and Gen Y are not onlyfully versed in every aspect ofthe 4Cs, but in fact both anticipate and demand that the 4Cs are included as core features of the mobile applications they intend to use.




Figure 1 – Antenna’s AMP Platform

‘State of the art’ in today’s mobile world literally means that all backend data source complexity, the bi-directional communications flow between the backend data and mobile devices, and the mobility platform itself all become entirely hidden from the mobile application developers, those that manage the platform, and ultimately those that actually use the apps.

this is a huge benefit! We simply do not need to worry about any of it or what goes on inside of it. What it means is that an enterprise can devote most of its IT resources to working with business stakeholders to build the right HCM models and the mobile applications themselves, rather than worrying about the otherwise highly complex tasks of building out mobile infrastructure.

So then, what do we worry about? We focus most of our energies on mobile application form, function and the mobile user – that is, everything that comprises HCM.

We estimate, based on Antenna’s extensive field experiences, that a powerful MAP will eliminate as much as 75% - 80% of a mobile application’s overall complexity. In figure 1 above this complexity includes everything in the diagram with the exception of the users on the right and the design studio capabilities of the platform.

the critical and most important result of deploying a MAP is that it frees up significant development resources (and especially the huge numbers of dollars that formerly needed to be allocated to back end development) to focus entirely on mobile user business requirements and HCM.




tHe lAst Mile of MobilitY

Telecommunications and cable companies use the term ‘the last mile’ to define completing a connection between the fiber out on the street and final connection to the home. Similarly, in today’s mobile-centric world, mobile application development concerns itself directly and primarily with its own last mile, which in our case refers specifically to the interactions that occur within the roughly 24 inches of space that exist between a mobile device screen and the mobile user, as shown in figure 2 below.

In designing today’s mobile applications, as we noted earlier, we simply don’t need to worry about what happens from the device back to the enterprise. In a nutshell, our key concern becomes instead to insure that we take full advantage of all the graphical capabilities, radios (typically, wireless, GPS, WiFi capability), on-board memory, special features (e.g. accelerometers) and computing power that now reside in our mobile devices to insure that we fully capture the 4Cs and fully deliver a user experience and user interface that is as engaging and delightful to the enterprise user as those we experience as mobile consumers.

The last mile refers to the interactions that your user will have with any mobile application. Form, function, and the space in between where the user interacts with HCM (as shown in figure 2) become the mobile app development team’s key concerns.

By direct implication, the goal becomes nothing less than one of capturing the exact same levels of success - with each of your business-focused mobile applications - that Apple, as an example, captured in form and function as it moved from iPod to iPhone to iPad, and that RIM, as another example, will likely capture through its PlayBook tablet.

Figure 2 – The Last Mile of Mobility drives Human Centered Mobile Design

Failing to take advantage of HCM-driven mobility is no longer an option and will absolutely place laggards at a distinct competitive disadvantage.




A lonG, lonG tiMe AGo in A GAlAxY fAr, fAr AwAY

Before taking a closer look at what HCM brings to the mobile application development game, let’s take a step back to what was the state of the art a mere 18 – 24 months ago. Back then mobility was still best defined as a tactical exercise, a means to deliver some level of productivity in order to shave some level of business process costs to improve the bottom line.

A state of the art mobile application circa 2007 – 2008, driven either by IT or through line of business operations, tended to look very much like what is shown below in figure 3. It is well worth noting that many enterprise mobile applications still look like this today.

Key missing elements in the design of such mobile applications included a lack of overall UI design capability (limited by the hardware and OS), the inability to capture the exact roles users play (it was always a compromise), and little if any input or feedback from the users that would eventually use the application. In all fairness, what is shown in figure 3 demonstrates what was actually possible in state of the art UI design at that time.

Not surprisingly, typical mobile application development resulted in sometimes user-unfriendly applications. Predictably these applications were sometimes followed by a reticence on the part of users to want to use the apps – at least not on any regular basis.

It is well worth noting, however, that these apps worked! They were generally accepted by users because mobility made a real difference to their work lives – job tasks became much easier to execute and productivity increased nontrivially, and led the way to today’s enhanced mobile scenarios.

In today’s world, consumers are driving the shift to mobility in the enterprise. They are adopting mobile on their own terms and want apps they love to use. Through the 4Cs mobile apps are now being used for far more unstructured work styles and behaviors, and mobile apps – through the use of HCM - need to deliver here.

One saving grace in the development process back then was the enterprise dominance of Research in Motion’s BlackBerry devices, which at least relieved developers from the need to create applications for multiple operating systems (albeit with the occasional and limited exception of Windows Mobile 4.x, 5.x and 6.x devices) and provided - and still provides - highly secure mobile communications infrastructure. The BlackBerry OS also allowed mobile app developers to maintain a standardized and consistent user interface approach, up until more recent variations of BlackBerry devices began to provide more design flexibility.

Today we have an entirely different scenario.

Figure 3 – An example of a tactical, circa 2008 mobile enterprise application (and still the prevailing standard for many of today’s deployed mobile app UI designs)




let’s iMAGine wHAt we CAn do

Driven initially by Apple (now delivering iPhone 4 and iOS), and since pushed strongly forward by Google’s Android 2.x, Hewlett-Packard’s WebOS, Blackberry OS v5.x and v6.0, and Microsoft’s new Windows Phone 7, mobile enterprise application developers today have desktop-like quality UI design capabilities (such as high resolution screens and 3D rendering), as well as HTML5 at their disposal.

Further, today’s AMP platform includes the all-important design tools needed to model and build application code bases once and deploy to the entire range of mobile devices and mobile operating systems available today – and tomorrow. A mobile app design studio, such as Antenna’s AMP Studio, will also provide direct access to native smartphone APIs, allowing mobile apps to take full advantage of unique device and OS capabilities. This is far more significant than may be obvious – users look for specific and consistent features that are central to each mobile OS and device type – especially as different and multiple aspects of the 4Cs are implemented within a mobile application.

HCM-centric app design begins from the perspective of ‘let’s imagine what we can do’ and with how the ‘what we can do’ is going to interact with the users of that mobile app across the entire range of today’s graphics-rich mobile devices. Human centered mobility is primarily concerned with developing the role-specific functionality a mobile app will require plus the graphical user interface that will give the application an entirely intuitive usability that makes it both fun and a delight to use.

Many Global 2000 companies are now moving quickly to take advantage of the new opportunities afforded by a start of the art MAP and HCM design principles. As HCM-based mobile apps become prevalent, employees will become significantly more productive and effective. As businesses push out HCM-based applications to their consumers, strategic top line revenue growth will increase significantly.

What then is possible for mobile applications today?

figure 4 below shows two excellent examples of what’s not only possible, but what is in fact being deployed and used across today’s more sophisticated mobile enterprises.

Figure 4 – Examples of exciting HCM-driven mobile applications that deliver perfect integration of mobile form and function, driving strategic top line revenue growth




In addition to taking advantage of unique features of each device, they need to take the same core look, feel and functionality across each device platform. A user should easily recognize the mobile app regardless of it running on an iPhone, Android or Blackberry; each platform, however, may very well add additional functionality based on unique device capabilities.

figure 5 shows the same mobile application running across RIM, HTC and Apple smartphones – each version bears a strong (essentially exact) resemblance to the other, while taking advantage of the unique capabilities of each phone.

UI design possibilities are only limited by the imagination. Think, for example, of how some music apps show ‘flip-across’ album covers. Can business application features and choices, to use a simple example, adopt similar techniques? Of course! Think outside the box.

One last important issue that today’s mobile enterprise applications need to take into account is that companies now need to build applications both internally for employees, as well as for consumers. An earlier white paper in our series, ‘Peace. Love. Appiness. Transforming Business in a Mobile World,’ provides greater detail on

Figure 5 – The best mobile applications will run across all mobile devices and mobile operating systems, retaining the same UI look and feel while also taking advantage of the unique properties of each

the convergence of enterprise users and consumers. The key point here is that all mobile enterprise applications must deliver outstanding and delightful user applications and experiences that both employees and consumers will love to use – anytime, anywhere.

HCM And tHe sMAll sCreen

An important part of defining the role-based parameters for any mobile application is to fully understand that they will be pushed out to, and interact with ‘small screen’ mobile devices. It is critical to understand that no matter how powerful smartphones become, the small screen form factor inherent to them requires that the UI being associated with the mobile device, and the role the mobile application will enable, be specifically designed for that form factor.

Put another way, designing a mobile application with a laptop form factor mentality (i.e. adopting and trying to adapt role-based parameters that were developed for laptops) will simply not work. In fact we can categorically say such an app will be doomed to failure.

A very interesting notion emerges from this: All new enterprise applications should be designed and built first and foremost, from the ground up, through HCM for a smartphone form factor. It is far easier to grow an application to larger form factors than it will ever be to shrink it down to a mobile form factor.

Following this mobile application build, the next step becomes one of expanding the application to take advantage of expanded tablet capabilities (e.g. iPad’s larger screen form factor and its multi panel capability).

Last, the ultimate iteration of the original mobile app then becomes, if required, a ‘supersized’ laptop application – but it nevertheless remains a laptop application with full mobile DNA and full mobile credentials at its core. Refer to figure 5 on the next page for a summary view of the process.




Figure 5 – Develop for the smartphone first. Expand functionality as needed for the tablet. Utilize the Web and HTML5 for additional laptop and desktop development

It is far easier to build the mobile application first and to then progressively expand its capabilities to larger scale devices - smartphone to tablet to laptop - than it is to build the larger device application first and then try to shoehorn that application progressively down to smaller devices. In fact, it becomes entirely possible for desktops and laptops to access ‘larger scale mobile apps’ – especially those written in HTML5 – directly through a browser front end, potentially eliminating the need for significant additional development in many if not most cases.

HCM therefore becomes not only the mantra behind mobile application development, but also takes on the critical central role for all new strategic enterprise application development!

A very interesting notion emerges here: All new enterprise applications should now be designed and built first and foremost, from the ground up, through HCM for a smartphone form factor. It is far easier to grow an application to larger form factors than it will ever be to shrink it down to a mobile form factor.




HCM in ACtion

Let’s next consider HCM in action in the real world.

First, let’s recall what we said in our preamble:

Mobility has become pervasive, and mobile users are no longer defined purely as workers, consumers, customers or partners – they are people! People with unique likes and dislikes. Individuals with specific cultural and social backgrounds. Human beings with real wants and needs.

Enterprise mobility is driven by the jazzy soul of people out to have a delightful and great time both personally and professionally through their having embraced mobility and their mobile devices. Enterprises both large and small must figure out how to tap into that jazzy soul of mobile users in order to create strategic benefits across an entire company – whether the goal is to develop superior workforce business execution over competitors, or to build major new streams of revenue by tapping into an organization’s consumer-facing user bases.

Or, as is quickly becoming the case, both.

The mobile market is primarily defined by hot, exciting, primarily youth-oriented, and very touchy-feely technology. Touchy-feely? Well, yes, it’s a key business technology term in the mobile world, and a corollary to jazzy mobile souls. Think of it as meaning that people REALLY love their mobile devices in a very tactile and a very personal sort of way.

In most, if not all cases, the device itself is much more important to the user than the stuff that runs on it. But the truth of the matter is that what runs on the device is what ultimately drives the mobile touchy-feely love that mobile consumers have discovered for their devices.

Consumers don’t care about this, and they do not acknowledge it – the one thing they know is that they love their devices. Mobile app

developers, on the other hand, need to understand intimately that applications and the mobile platform that drives those applications are the keys to successfully deploying mobility at the business level and to insuring that the apps don’t get in the way of users continuing to love their devices.

What HCM dictates is that what is unique about mobile technology in business is that for the global workforce it’s a consumer play, meaning that device choice and the overall fun and ease of use that mobile devices now deliver on the personal side (the touchy-feely jazzy soul stuff) now become the central driving forces for ensuring that enterprise mobility is successfully deployed and successfully utilized.

But it’s not just about the mobile app.

Keeping the 4Cs in mind (context, content, collaboration, commerce), it’s about how users interact with and perceive the app. Does it deliver a valuable personal or business service that is both intuitive and fun to use? Does it embrace the user’s choice of device? Touchy-feely is about the device-app-jazzy user soul relationships, where the mobile app (more accurately a user’s collection of mobile apps) absolutely insures that the device itself is ultimately the thing that gets the love.

users won’t stop using their devices of choice – they will, however, immediately resist, drop and steer clear of any mobile apps that make it seem like their devices of choice are not delivering a fun and delightful experience or, even worse, have become hard to use. Let’s take a look at a mobile application that takes all of the above into full consideration – and delivers on the resulting benefits we’ve discussed. The app, shown in figure 6 on the next page, was developed by ING Direct USA and built on Antenna’s AMP.




Figure 6 - ING Direct USA’s Flip for Fun Banking App

It is a mobile banking app that ING Direct USA considers a ‘branch in your pocket.’ It delivers a visually appealing UI that nicely anticipates the user’s needs during a mobile banking session. The app intelligently delivers on function, while fully utilizing the form inherent in the iPhone – the app takes great effort to stay within the bounds of the user’s expectations for both the iPhone itself and for conducting a fast and efficient mobile banking session. But…there’s more!

Figure 7 - The ING app screen shot in horizontal flip for fun mode

As figure 7 demonstrates, when the user ‘flips’ the phone from the app’s vertical orientation to a horizontal orientation, the app provides an entirely new layer of functionality directly suited to a horizontal perspective – the user quickly goes from the banking app to preconfigured social networking settings.




Perhaps the user has just purchased something cool and exciting, and after checking the bank account, wants to tell one or more persons within the user’s social network about a great sale. Done in an instant, with the app anticipating and delivering on the user’s desires. The possibilities are endless.

A firsthand look of this mobile app is possible - the iPhone/iPad version of the application, which will soon launch on Android and BlackBerry as well, is available for download and study through Apple’s AppStore.

figure 8 shows the newest consumer-facing mobile application from Hallmark, which was officially released for Thanksgiving 2010 to drive Black Friday in-store customer traffic. This HCM-loaded app was built, tested and deployed within 4 weeks of its initial concept. As with the ING Direct USA app, the Hallmark app is available to download and study from the AppStore (and will soon be released for Android and BlackBerry).

Note the rich and intuitive UI on each of the pages shown in figure 8, as well as the examples of services provided by the app that greatly aid the user, whether in the store or out in, say, a mall. The ‘My Hallmark’ page demonstrates the use of personalization in real time. of equal importance (this is true of the inG app as well) the application maintains Hallmark’s key brand persona, significantly enhancing the company’s ability to drive brand loyalty and recognition.

There are three things of great importance in dealing with all of your mobile users: what they do, how they do it and why. In the case of consumer facing users such as those utilizing ING Direct USA’s Flip for Fun and the Hallmark app, it’s all about capturing the what, how and why of their personal desires and needs, anywhere, in real time.

In the case of business facing users (employees, partners, business customers, etc.) it is all about capturing the what, how and why of role-based business processes as they happen in real time. A merely clever business app UI will engage the user with ‘what.’ A great mobile business app UI will also anticipate the ‘how and

Figure 8 - Hallmark app screen shots

why’ a user consumes services (e.g. a set of business processes).

As an example of a mobile business app, let’s next take a very quick look at what a well-designed and well-executed mobile sales application will look like following our HCM design principles. In this case we’ve moved from an original smartphone sales app, to one that has been ‘upscaled’ to a tablet format. The app is shown in figure 9 on the following page.




Figure 9 - AMP Pharma App on iPad

Utilizing our HCM principle of starting with the smallest form factor possible - the smartphone, the sales app (again built on Antenna AMP) is fully backwards compatible with the smartphone app, but now has new additional features that take full advantage of, in this case, the iPad’s much larger screen and multi-pane capabilities.

A detailed deep dive into the iPad sales app is beyond the scope of this paper, however a deep dive is available through the following video: Mobile sales on iPad – doing it right. The link is available under Resources.

There are several key things to note and consider while watching the video. Aside from the beautiful multi-pane UI of the app, there is a less visual though profoundly significant feature: the app anticipates every need of the user. In our example here, the app has been further refined for use in the heavily regulated pharmaceutical industry, placing additional substantial burdens on what the mobile app needs to anticipate and trigger in terms of the user’s real world pharma sales needs, in order to deliver the

requisite delightful and engaging user experience.

HTML5, combined with MAP capabilities – which we refer to as hybrid mobile apps - will provide similar levels of functionality, manageability and security as native mobile apps, as well as a similar level of HCM design possibilities. For an example of hybrid apps that utilize both HTML5 and the MAP, refer to the following video: Antenna AMP Approvals suite: next Generation Mobile Applications. The link is available under Resources.

All successful HCM deployments fully depend on the power of the underlying Mobile Application Platform.




Whether an application should be built as a hybrid or native app is a discussion outside the scope of this paper; generally speaking, however, hybrid apps will always be easier and faster to build, but will ultimately lack the entire range of capabilities a native mobile app will deliver.

In many cases the hybrid mobile app can serve as an almost fully functional prototype for a native app – making field testing of the user interface and key features easy and quick to do. It is also likely that a hybrid app will, after field testing, prove to be the perfect application even in cases where a native app was originally scoped out.

Finally, it is critical to note that all successful HCM deployments fully depend on the power of the underlying MAP. In the case of all the apps we’ve shown here – all of them were built on Antenna’s AMP – there is a great deal of sophisticated and complex technology operating behind the scenes to insure that the apps are operating in well connected, highly secure and well managed environments.

Both users and enterprises must have FULL trust in the applications from this perspective. The complexity – it bears repeating - is handled directly through the MAP, allowing essentially all IT development resources to be allocated to delivering the mobile apps themselves through the HCM principles we’ve highlighted in this paper.

Through the power of Human Centered Mobility and our ‘let’s imagine what we can do’ mobile app philosophy comes the freedom – and the necessity - to innovate. Innovation in turn becomes the key cornerstone of all mobile enterprise application development.

Through innovation, driven by the ideas of HCM and within the ‘last mile of mobility,’ companies gain the power of discovering new ways to conduct business much more efficiently and effectively, new ways to capture and handle business and customer work flows and information (a.k.a., business intelligence) in real time, and creative and engaging ways to connect with and motivate partners, customers and consumers.

Simply put, all of the ideas noted in this whitepaper will deliver new strategic enterprise application methodologies, strategic advantages and new top line revenue growth opportunities for the enterprises that choose to deploy full HCM-driven mobile strategies.




uPCoMinG PAPersEnterprise App Stores – Your Mobile Apps Discovered & Used (AMP MarketPlace)•

Appiness Scores - Are Your Enterprise Mobile Apps Delightful and Effective? •

Native or HTML5 Applications – Which, Why, When, Where & How•

The Imaginative Pragmatist – Who Are the Enterprise Mobile Masters?•

Buy Now, Build Later – Why Building In-House is NEVER the Way to Begin Strategic •

Mobile Applications Projects

The Antenna Technical ‘How To’ Guide to Mobile App UI Development•

resourCeswhitepapers in this series:

Peace. Love. Appiness. Transforming Business in a Mobile Worl• d

Mobile Consumer Application Platforms – The Five Key MAP Requirements•

Mobile Cloud Computing•

Additional resources:What Makes a Great Mobile Ap• p – Watch the Video

Mobile Sales on iPad: Doing it Right – Watch the Video •

HTML5: Changing the Web Apps Development Gam• e – Watch the Video

Antenna AMP Studi• o – Watch the Video

Antenna AMP Approvals Suite: Next Generation Mobile Application• s –

Watch the Video

Antenna AMP MA• P – Detailed White Paper

web sites & social networking:www.antennasoftware.com

www.mobilemasterscommunity.com

www.facebook.com/antennainc

www.twitter.com/AntennaSoftware

www.twitter.com/MobileMasters

For any feedback or comments, please send us a message at [email protected]

Visit the Mobile Masters Community at www.mobilemasterscommunity.com for knowledgeable blogs, forum discussions, additional videos and other valuable resources.


http://www.antennasoftware.com/pdf/whitepaper_PLA.pdf

http://www.youtube.com/watch?v=Pnc-qfpP1gk&feature=player_embedded

http://www.youtube.com/watch?v=BBE7sjmC2w8&feature=player_embedded

http://www.youtube.com/watch_popup?v=0NRGhgdpze0&vq=medium

http://www.youtube.com/watch?v=BBE7sjmC2w8&feature=player_embedded

http://www.antennasoftware.com/amp3.aspx

Human_Centered_Mobility

Documents

Transcript of Human_Centered_Mobility