Sunday, May 11, 2014

Following the Money trail…On your Device? – Mobile Payment Landscape – Understanding of which is necessary for any Enterprise!

Topic: Following the Money trail…On your Device? – Mobile Payment Landscape – Understanding of which is necessary for any Enterprise!

Folks,

This week I want to follow the Money and explore the colorful landscape of handling Money in Digital economy. If you think all our discussion around crafting an Enterprise Mobile Strategy was complicated, wait till you see the Mobile Payment Landscape. This weeks post I wanted to focus on Mobile Payments where much works is to be done to address fragmentation and reach a critical mass. But before we jump into Mobile payments let us tie in with my previous discussion on Mobile Ecosystem and mCommerce and mBanking – as that discussion is relevant here.

In my last post (ref: Understanding Mobile Ecosystem is Vital for a MobileFirst Enterprise) I discussed the value of sound understanding of evolving Mobile Services ecosystem and inferred that the growth and expansion of business development, MobileFirst portfolio, therefore, relies on implied understanding on the co-development that provides transient energy (in the form of innovation and value), and cumulative development result will enable the beneficiary of our technology – “our clients," to derive value from our products and solutions.

Some Significant Mobile Payment Statistics:

1. $1.6 Trillion of Mobile Payment in China

2. 46% of all POS transactions b 2017

3. 100% and more year to year growth

4. 225 Mobile Money Services

5. 320 Million NFC enabled devices shipped in 2013

6. 90% growth in P2B & B2P, P2P transactions with payments/transfers worth $1.1 Billion.

And more…

Also in my earlier post (ref: mCommerce or Smarter Commerce) I discussed some of the challenges that mCommerce initiatives face. As a Merchant, the marketing, selling and servicing components involve an integrated strategy around offers and accepting payments. To this effect I discussed the following:

a. Mobile Payment – Today clients have a few choices:

i. Cloud – e.g. GDW – Google Digital Wallet/ISIS, etc. Simple and easy to Implement and integrate into business process

ii. NFC – Near Field Communications – Not all phones are enabled and this technology is still maturing in adoption, security concerns, etc.

iii. Custom processing – This is traditional credit card processing and most commerce platforms provide integration avenues including WebSphere Commerce Server. (Example Amazon.com)

iv. New emerging consortiums – MCX. –We need to understand this. Please take a moment and Google it. It is a huge consortium and gaining much momentum.

b. B2B -- Complete integration with Business partner gateway services. Mobility will need to consider this.

c. Brand management – How do we a Mobile Store front manage a cohesive brand like they do on Web? Think Multi Brand and linkages?


.. and more… These are just glimpse of issues we can encounter and by no means an exhaustive list.

Mobile Payment – A fragmented Landscape

1. Mobile Payment – an Ominichannel experience - Mobile payments, be it Mobile wallets or Digital wallet promises an Omni channel experience incorporating the coupon, loyalty programs, and integrating that with Mobile experience. Mobile payment if not integrated into a complete experience fall short of delivering the holistic digital experience.

2. Non banking players – Mobile Payments opens up new avenues to commerce and Mobile monetary exchange. Be it Bank to person (B2P), Person to Person (P2P), Person to Bank (P2B), and so on, there are many non banking players emerging in Mobile Payment space that enables a seamless transfer of funds between 2 entities either to allow commerce or transfer of funds and remittances.

3. Mobile Wallet vs. Digital Wallet: Mobile Wallet is an application on mobile device that manages access to payment credentials and value added services (e.g., bank, credit or debit accounts, prepaid accounts, transit tickets, coupons and rewards) stored in secure element in the phone to initiate mobile payment

And Digital Wallet is an application on a device that accesses payment credentials stored in cloud using phone number and PIN, or card.

4. On Device technologies – NFC, QR and HCE ( Host card emulation) – these technologies allow proximity payment solution that requires proximity to the POS – Point of Sale system. There are many security, privacy concerns in Mobile payment space and proximity payment solution needs a sound commerce and payment acceptance infrastructure.

5. Monetizing data – There are many Mobile payment players that are not directly monetizing services, but are more interested in the resulting data and analytics from mobile transactions. These services while may provide value in over all mobile payment value chain, the consumers essentially become the product, as they provide data, which is mined for insights. This requires an enterprise to consider security and privacy concerns.

Mobile Payment - Players in the Ecosystem

1. Legal framework and Regulators. – This relates to a lack of sound and emerging legal and regulatory framework governing Mobile Payment. Today there is no one law or governing authority that oversees mobile commerce. Regulations and laws applicable to underlying payment methods (credit, debit, prepaid, ACH) govern mobile payments Mobile carriers and alternative payment providers are less familiar with banking laws for consumer protection and privacy, KYC, BSA/data security, money transmission, risk Compliance, etc. Some agencies are trying to create a consortium to better understand and regulate this area, agencies include - FRS, FDIC, OCC, NCUA, CFPB, FCC, FTC. This poses an interesting challenge to enterprise that has a liability around transacting, commerce and payment processing.

2. Industry Association – MCX as an example comes to mind. Merchant Consumer Exchange. MCX is Merchant driven mobile payment platform being developed. It is an essentially a Cloud based wallet app with QR code. Today this consortium has major 40+ retailers in the US out of overall 7 million retailers. This includes potential to incorporate merchant deals and Loyalty programs ( coupon and Loyalty). MCX recently partnered with FIS ( financial services company) to provide an EFT based payment processing and settlement system.

3. Technology and System Vendors – This includes vendors and system such as Banking and processing systems (Visa/MC/Fundamo/Temenos, etc), Wallet and App vendors (Monetize, mFoundry), NFC chip vendors (Sony, NXP, Infinion), SIM based secure elements (Gemalto, etc), MMT – Mobile Money Transfer platform – (Alcatel-Lucent, Telepin, SAP, etc.), and other providers such as an NFC Sticker, MicroSD and even HCE- Host card emulation technology that is included in Android’s kitkat Platform.

4. Payment Processors – This can include a complex set of payment processor value chain ranging from Bank – that acquires and issues Credit card, Payment Processing – Visa, MC, MMT (Mobile Money Transfer) network including service such as Mobile/Digital Wallet, Agent enabled network, Carrier (telco) enablement network. Collectively these form a rich and complex set of value chain players provide a particular value.

5. Service providers – These are a evolving set of ecosystem players that provide a specific set of services. Collectively these form a rich and complex set of value chain players provide a particular service and adding to the overall cost of transaction. Some of these services may have an interest in data and analytics, but that is again a privacy and security concern. The players include a. Card (Payment) acquirers such as - a. Traditional banks and credit card issuers (Chase/BoA, etc.) b. Card processing networks ( Visa, MasterCard, etc.) c. Payment Service Providers ( PSPs)- Another rapidly growing market include vendors such as cybersource, vesta, DataCash, etc. d. Carrier (Telco) Providers – famous concept such as M-Pesa have made this popular, and this concept is growing in Europe and other developed market, as well. e MMT- Money transfer service such as Western Union, Moneyrgam and many small and large regional vendors. f. M-Banking – traditional services providers such as Monitise, FIS, and Fiserv, etc.

6. Couponing and Loyalty services – This is an interesting segment of services that augment the various specific services discussed above. Couponing and Loyalty service integrate with payment services to not only provide a seamless experience but also assist in analytics and settlement. This eco system is growing and becoming integral part of Industry association platforms such as MCX, etc.

7. Proximity Payment Service – These include POSs, Contactless payment terminals and Mobile NFC ( Near Field communications). These provide an integration with Couponing and Loyalty programs, and have quite and emerging eco system. Some examples include – ISIS(Mobile wallet), Veriphone, Verizon, Tagpay, Intuit, etc. Many of these are technology that provides a platform to take advantage of proximity services such as NFC and iBeacon. Apple’s iBeacons and PayPal Beacons both based on Bluetooth Low Energy (BLE) may herald a significant alternative to NFC. Other technologies being deployed include QR codes, SMS and MF Tones and cloud-based services.

8. On-line (e-commerce) and M-Commerce (Omni channel) – The players here include traditional E- and M-Wallet such as Amazon, PayPal, etc. that have a stored value or payment account linked to M-Wallet to make commerce and payment easier.

9. Mobile Money Transfer (MMT) – This includes domestic and international remittance; sole trader, merchant, bill & salary payments. This is fairly crowded space that includes large and small companies trying to grab a slice of Mobile Payment business. Some popular companies include Visa, M-Pesa, Moneygram, Western Union, etc. The service provider in this space include internal remittance of money transfer to person to person, money transfer/based on agent network and enabling mobile money transfer for the ‘Unbanked’ – a population that does not have a valid bank account or affiliation with a financial institution.

10. M-banking –These are traditional banks with a Mobile interaction, account management, bill pay and all related services to the ‘Banked’ customers. In many ways, m-Banking does compete with various payment providers and service providers discussed above. From Bill pay to fund transfers and small trader remittances, they play an important part in Mobile Payment economy due to the fund sourcing and familiarity with global financial systems.

11. Mobile Wallet – As discussed earlier - Mobile Wallet is an application on a mobile device that manages access to payment credentials and value added services (e.g., bank, credit or debit accounts, prepaid accounts, transit tickets, coupons and rewards. This can be any manifestation from a secure SMS (USSD) to a fancy app that links multiple accounts. As a generic concept it is utilized by many players in following ways:

a. Telecommunication sector – These are carriers and many in telecommunications sectors are forming tie up with banks and payment processors to facilitate fund transfers.

b. Payment Processors – These are central to traditional credit card and e-commerce payment processing systems. The implied business understanding provides these with a competitive advantage with mobile payment space. But this space is increasingly evolving and concepts around facebook's social payment and P2P, P2B payment landscape can be disruptive to their domain.

c. Mobile OS and Hardware owners – All Mobile handset and Mobile OS vendor that seek a very high degree to client/user engagement are continually innovating and including the enabling technology such as NFC, iBeacon, HCE – Host card emulation, etc., all with the intention to enable mobile payment capabilities and increase their adoption and dominance in huge global marketplace.

d. Remittance agencies - Money transfer agencies are embracing mobile as a remittance and bill payment channel and partnering aggressively with carriers to deliver international services.

e. Retail banks - These are traditional banks with a Mobile interaction, account management, bill pay and all related services to the ‘Banked’ customers. In many ways m-Banking does compete with various payment providers and service providers

f. ‘Other Agent’ Network – These are ‘agents’ that form the network that is alternative to traditional banking or money transfer network. These are especially dominant in ‘unbanked’ markets and critical to the eco system of the Mobile payments, remittances, P2P money transfer, etc.

While this discussion may present a long list of considerations around the complexity around Mobile payment, Let us try to simply this. Fundamentally, we need to understand how the players and Landscape align, and this will enable us to not only understand the challenges but also formulate a thoughtful strategy around adoption of Mobile Payments as an integral part of Enterprise Mobile Strategy. So basically any Enterprise Mobile strategy that includes Mobile payments, below are 4 sets of considerations where some or any of the Mobile payment players may fit in:

1. On device components – This includes things like, Mobile and/or Digital wallets, Trusted service manager – which includes Mobile wallets and associated secure elements, Cloud management – for use profile, QR code, and Digital Wallet management. The Challenge here to choose from a plethora of choices as an accepted form of payment.

2. Mobile Payment services – This part includes integration with Mobile Money transfer, Mobile payment services, agent network – all aspects of the value chain that are involved in acquiring, accepting and processing payments.

3. Financial Intermediaries –These are financial intermediaries that deal with the merchant regarding rebates, coupons, issuers of gift cards, etc. Essentially any intermediary that ranges from providing consultative selling to fund sourcing.

4. Clearing and settlement - These are financial powerhouses, which are at the terminal end of the Mobile payment value chain and include clearing houses, financial settlement and card processing units ( Digital Wallets, etc.).

Mobile Payment Industry Challenges:

1. Technology Adoption – Technology adoption ( NFC, Mobile and Digital wallets, QR code, HCE, etc.) that handles Money requires trust and ability to track, dispute and manage a transaction. The adoption of these technologies both from a consumer or end user perspective or an enterprise – which may be a part of Mobile Payment value chain is a challenge. While industry standards are still emerging, but lack of current standards and scattered governance and legal framework makes mobile payment an interesting landscape, given the statistics that surround it and adoption in some geographies. Technology companies that play in this space should focus and present a framework that can not only be easily consumed, but provides an enterprise integration that can secured, monitored and audited.

2. Security and Privacy concerns -- Given the diversity and fragmentation in Mobile market place,as we discussed here, there are many touch point along the payment processing value chain, any enterprise that is either a part of value chain or initiates or invokes any part of the value chain, is and should be responsible in ensuring security of the transaction and privacy of their users. This is a challenge due to lack of transparency between these interactions of the transaction as it progresses through these touch points.

3. Data Ownership - As discussed earlier, there are many Mobile payment players that are not directly monetizing services, but are more interested in the resulting data and analytics from mobile transactions. These services while may provide value in over all mobile payment value chain, the consumers essentially become the product, as they provide data, which is mined for insights. This requires an enterprise to consider security and privacy concerns.

4. Emerging regulatory and legal framework - Today there is no one law or governing authority oversees mobile commerce. Regulations and laws applicable to underlying payment methods (credit, debit, prepaid, ACH) govern mobile payments Mobile carriers and alternative payment providers are less familiar with banking laws for consumer protection and privacy, KYC ( Know your Customer), BSA/data protection, money transmission, risk Compliance, etc. This poses a challenge in not only governance but also settlement processes. This is largely an enterprise policy decision on the level of risk an enterprise is willing to assume with mobile payment transactions.

5. Highly fragmented market – These are a lot of Mobile Payment players in this diverse and largely unregulated market, this makes adoption of these technologies complex and challenging. For instance, how does an enterprise chose between supporting Mobile wallet or Digital Wallet, NFC vs. iBeacon, Mobile Money Transfer (MMT) vs. M-Banking, etc. Lack of standards, single governing authority, many touch points due to many service providers while fostering innovation makes the choices difficult due to accountability and lack of transparency in event of a dispute.

Conclusion:

Mobile Payment landscape is complex, fragmented and diverse. Today there is no one law or governing authority oversees mobile commerce. However, this is an emerging space that no enterprise engaging in any Mobile commerce, ranging from retailers to governments can ignore. Mobile payments promise an Omni channel experience incorporating the coupon, loyalty programs, and integrating that with Mobile experience. Mobile payment if not integrated into a complete experience fall short of delivering the holistic digital experience. While the promises of Mobile payments are immense there are many considerations, challenges and possibilities that an enterprise should consider. What makes Mobile Payments an interesting space is the emergence of new players on a daily basis. For instance, facebook announced it Social Payment ( P2P and MMT patterns) ambitions – if facebook succeeds it will not only lower the cost of transaction of payments and transfers, but will disrupt yet again a landscape that is in constant state of flux. The true challenge is to pick a sustainable platform or a mobile payment strategy that is cost effective, and yet addresses the diversity in this evolving landscape.

Interesting Readings:

1. http://www.ncsl.org/documents/standcomm/sccomfc/MarianneCrowe_PowerPoint.pdf

2. Mobile Payment Industry Analysis - http://www.firstpartner.net/downloads?op=add&id=214

3. http://en.wikipedia.org/wiki/Host_card_emulation

4. http://www.fdic.gov/regulations/examinations/supervisory/insights/siwin12/mobile.html



References:

Ref: Mobile Banking or mBanking

Technical Imperatives :

a. Understanding the security Implications – this includes data on device, data in transit, data in enterprise, but also includes considerations around malware, malicious application ( on same device), wireless carrier infrastructure, availability to tools and fraud control policies. Etc.

b. Payment technology Landscape - Banks do have to consider the payment technology landscape. Today, primary elements of mobile payment technology include (but not limited to) NFC (Near field communication), SE (secure element – cryptographic module), TSM (trusted service manager – handles transactions – sort of like a transacting clearing house) and Cloud based payment services ( Google digital wallets and Passbook based)

c. Risk Mitigation – Measures that can be taken to address security challenges of Mobile Banking and payments. These include Fraud detection and alert, secure notification system, Mobile application design and policy that govern end user action. Understanding, access and fraud detection and alert system in the application design process.

d. Omni Channel Service integration - Enable bi-directional access, and communication across all channels of communication including request for contact center callbacks from all channels.

e. Secure notification Landscape - email/SMS/online msg/app alerts generate automatic fraud alert, offers, promotions, etc. that is sent to customers in real-time. The alert use deep linking to enable things like, direct dial to fraud agent, schedule a callback or even click through to disable the block from the mobile app. Application Design considerations.

f. Mobile Device and Application Landscape – This deals with the policies and technology to provide malware and jail break detection, Spyware and SMS Trojans, Mobile OS and Application runtime vulnerabilities and so on. All this is geared towards preventing privileged access to application and user data that can compromise the integrity of a transaction.

And more…


Monday, May 5, 2014

Agile Application Infrastructure: A New Paradigm for New Workloads

I recorded this event hosted by IDG on role of Agile Infrastructure on new Mobile Workloads.
These are fundamentals, we need to be aware of for MobileFirst and Application Infrastructure

http://www.idgconnect.com/download/18812/agile-application-infrastructure-new-paradigm-new-workloads?source=IBM

:)
Nitin

Tuesday, April 22, 2014

Understanding Mobile Ecosystem is Vital for a MobileFirst Enterprise


Folks,

          This week I would like to focus on Mobile Ecosystem.  In ever changing mobile world the realm of possibility around technology and business models are on a continual shift. With increase in sophistication of technology  on devices, wearable and the ability to connect more devices, to more endpoints than ever before, has not only enabled innovation marketplace and business models, but also added complexity traditional business model and enterprise application landscape. It is my view that it is vital for any business and technology vendors to understand the ecosystem, to not only effectively compete but also thrive in the new economic age. In other words EVERY business, which has anything to do with Mobility, needs to adapt. Much like all living organisms adapt in an ecosystem to survive and thrive.  I would like to build upon a fundamental principle that development depends on co-development. This principle implies that the co-developed, which is part of the ecosystem, collectively defines the progression or development in technology and an ability of a business to adapt to survive or thrive. The business can be a widget vendor or a technology vendor – the rules of engagement (i.e. Innovation and implied understanding) are the same. In this post, it is my attempt to discuss and (hopefully) explain the enterprise mobility ecosystem map that will not only enable us to compete better, but exploit the co-developments and thrive in the marketplace.    

         So let me start with defining a Mobile Ecosystem. I think of a Mobile Ecosystem as a collection of diverse interaction model (Devices, wearable, convergence, etc.), connected to various ‘services’ by a granular, yet diverse fabric of networks that can work seamlessly and share data (location, state, information etc.). I realize that this simple definition may not include things like security, analytics, cloud, etc. But I am including ‘services’ as a definition to cover the broad range of eco-system players.
A simple ‘day in the life of a Mobile user’ can  very easily adapt to our broad definition. A user has a device  manufactured by a vendor, which included Mobile OS with customizations and custom services provided by the network service provider. The same user is able to cross authenticate between apps, share data, location use Dropbox like service to store files, invoke API to make payment, inquiries and is possibly monitored for any security vulnerabilities by an enterprise agent. So the notion of ecosystem services embedded into applications is not only seamless but also ubiquitous. 

Let me try to define the players in the rich and evolving Mobile ecosystem:

1.    Application SDKs :
Application SDK vendors provide platform and SDKs for mobile application development.

Players: Android, Apple, Windows, PhoneGap, BlackBerry, Appcelerator etc.

2.    Mobile OS/Handset OEM :
Handset vendors that subscribe to one or more SDK vendors , and OEM SDK as a  part of handset/device software stack. Essentially a Mobile OS.

Players: Nokia, Samsung, LG, Microsoft, Apple, etc.


3.    MDM/MAM :
Mobile Device Management/ Mobile Application Management. Interesting space that not only needs to keep up with the  Application SDK, but security threats and new emerging IDaaS models to ensure meaningful usage which is secure and adopted by the end user.

Players: Mobile iron, Fiberlink, Airwatch, good, XenMobile, Apperian, Knox, Afaria, etc.


4.    Mobile Services :
Broad range of services  that either provide a point solution to address a specific problem or provide a ancillary service such as  Paypal which may interface with a retail app, and only provide payment service, and another app may provide location based marketing, with contextually relevant couponing system.

Players: Urban Airship, Twitter, Facebook, Paypal, Google Places, Localytics, foursqure, Linkedin,WhatsApp,Flurry, etc.

5.    Databases/data Services:
Important data service that needs to not only consume traditional enterprise data models , which embedded in legacy enterprise systems ( RDBMS?ODBMS) but also bring the new data models (No SQL , unstructured data) to relevancy. There is an assumption that some ephemeral unstructured data is needed  for analytics, inference and action but necessarily for enterprise business systems.

Players:  IBM DB2, Mongo, Couch, Cloudant,SAP HANA, Oracle, MySQL, etc

6.    Identity Service
Identity service provide a mechanism to assure identity of the device owner, while a device may have multiple persona the assurance of application , data and identity security is of paramount focus.

Players: LDAP, IDaaS, Access management, Identity interceptors, CloudEntr, etc.

7.    API Management
The ability for an enterprise to expose an enterprise persona either by offering services to enhance developer productivity, enable new application design models such as composable services or to monetize the services - API management provides the glue to bridge the gap between traditional  and new services.

Players: Apigee, Layer 7, IBM API Management, Mashery, etc.

8.    Enterprise BaaS
Enterprise back-end as a service which encompass any back end service and can employ API management to expose these services to be metered and utilized. This mechanism gives a sense of decoupled model for service consumption  and composition.

Players: IBM Bluemix, Kinvey, Feedhenry, parse, stackmob, etc.

9.    Middleware
Traditional middleware services that house the enterprise business logic, rules and processes, usually connect to a back end database or EIS systems. I choose to include this as a ecosystem component as most services today are not created in a vacuum and many reside in Middleware systems.

Players: WebSphere, Tomcat, Weblogic, Jboss etc.

10.Mobile Middleware:
MEAP – Mobile enterprise Application platform can be classified as a Mobile middleware service which provide flexibility, control, and enterprise awareness to Mobile applications and Mobile specific services to legacy enterprise applications

Players: Worklight, Antenna (Pega), Kony, Verivo, engine yard, SUP-Syclo (SAP), etc.

11. Enterprise Stuff: CRM/EMP/ERP /BPM/ECM
These are the services that enterprise have been building over decade to manage enterprise resources, human resources, customer relationships, business process etc.  I am including this also in the ecosystem for the same reasons I included middleware services.

Players: IBM BPM, SAP ERP, Peoplesoft, Siebel, Salesforce, Dropbox, Box, sharepoint, Pegasystems, etc.

12. Cloud Services
This broad category probably represent a lot of  services available today – includes both public and private. While this is evolving and widely accepted,  it is to be noted that cloud service spans a broad range of services

Players: IBM Bluemix, SalesForce, Facebook, Ebay, Dropbox, CloudEntr, LinkedIn, Google+, APNS, GCM, AppStore etc.

13. Connectivity Service Providers
The telecommunication providers, which are the carriers of our voice and data packets, are an important part of  Mobile ecosystem, and they continue to play a broader and important role, ranging from network provisioning to application services provisioning.

Players: Verizon, ATT, Sprint, T-Mobile, NTT, Vodaphone, CenturityLink, Comcast, TWC, regional telecom provider

         As you all can see that there are a number of key building blocks necessary for enabling  a robust mobile application ecosystem. While, like any other ecosystem, even Mobile ecosystem  will evolve and change the operating landscape, interoperability with the ecosystem should be an embedded thought in the design process. Be it designing an Enterprise Mobile Strategy, Mobile platform, MEAP or a cloud service, the true value  to an enterprise and client is the ability to adapt to the ecosystem and exploit the choices in a diverse set of available services.

Ideally  a design of  an enterprise Mobile Platform should be open, and have the ability to absorb and adapt to changing ecosystem, at the same time provide integration to not so dynamic enterprise application systems. Such a design imperative would be a strategic extension to an enterprise mobility strategy. In addition, any Mobile Platform should provide the following characteristic to be widely accepted ( besides being open or build on open standards)


1. Integration - We want a completely agnostic message to our clients that you can do "native" , hybrid, or mobile web because the real value is in the platform, administration, up-keep, security, and integration layer we provide better than anyone else.

2. Flexibility - Mobile Middleware should provides a layer of indirection, which allows for the back end services to be shifted without affecting the end point

3. Control - Ability to surgically enable and disable Application specific to a platform, administratively provide platform specific messages.

4. Security - Mobile Middleware also arms the enterprise to adapt and fit into to current Enterprise Security platform ( authentication, authorization and security policy enforcement etc).

5. Reuse and Optimization of existing enterprise services - also provides an avenue to exploit existing services ( SOA Model) and since these services were design for Web Application, Mobile middleware allows for filtering and altering the content, prior to sending the response back to end use.  

6.Mobile Specific Services and Eco system consumption - Unified push notification, SMS, cloud services and devices specific notifications etc, provide an avenue to address these via platform. and more…. 


Conclusion:
When we talk about self-sustaining growth, we ought to realize that self-sustaining growth is not really self-sustaining  (in Mobile world), and it needs infusion of energy from outside – the ecosystem. This principle is true for any ecosystem, including our own planet. The growth and expansion of business development, MobileFirst portfolio therefore relies on implied understanding on the co-development that provides transient energy ( in the form of innovation and value), and cumulative development effect will enable the beneficiary of our technology – “our clients”, to derive value from our products and solutions.


Good Read and References:




Saturday, March 29, 2014

Wearable Technology – The Next frontier – My initial experience with Google Glass


Wearable Technology – The Next frontier – My initial experience with Google Glass

Folks,

 It has been interesting few weeks – I have been engaged with some really interesting projects, travels and I think have embarked on a new journey to a new frontier – Wearable technology. I would like to share some of my experiences and excitement with Google Glass. In this post I’d like to spend some time discussing enterprise imperatives with Wearable technologies. I find this space fascinating and intriguing at the same time. While the adoption of Wearable technology is still in its infancy the promise it holds is immense.  

Let me start with  some of my experiences:
My journey with this titanium-framed Wearable device has been more of an experiment with technology, our attitudes and simple joy of exploring. I also realized that I am one amongst ten thousand folks who have subscribed to this controlled experiment, with a steep price tag that compares itself to a home computer. So here are my initial thoughts:

Technical Spec include:
1.    5-megapixel camera, videos shot in 720p,  - Think image quality
2.    Wi-Fi,  - Think connectivity
3.    Bluetooth,  -- Think Battery life of the paired devices
4.    12GB of usable memory synced with Google cloud storage (16GB Flash memory total) – Storage capability

Support for (Limited) Devices –
a.  MyGlass for Android requires Android 4.0.3 (Ice Cream Sandwich) or higher.
b.  MyGlass for iOS requires iOS 7 or later (iPhone 4 and above, iPad 2 and above with cellular connection)

SO here are a  few quick observations:

1.    It is lightweight and less intrusive, probably because I do not wear glasses.
2.    The battery life is OK, for me with active usage it last for 3-4 hours.
3.    The battery drain is two fold – as you pair the device with your smart phone and now you have to really be aware of battery usage.
4.    The Glass itself run’s on Google own Android Mobile OS – but cannot ONLY connect from Android and iOS devices.
5.    The titanium frame is malleable, nose bridge can be adjusted, and back part  houses switch, USB charger and battery and amazingly lightweight.
6.    Security – this is tied to your device. All the social media posts, e-mails relies on the application on your device and there is a “trust’ between your glass and paired device.
7.    The quality if image, video and feeds from CNN is crisp and commendable, with option to read the news feed or have glass read it on your behalf.
8.    Active Glassware – App function of the Google glass which allows for “Glass ready” apps in market place to  be ‘Installed on glass’ – which  is an interesting concept ( more on this later)
9.    The Screencast feature is a nice feature to “mirror” what is seen on glass. – this is good for demo’s
10.Glass requires separate contact list to be able to call and it does a good job with speech recognition.
11.Primary way to interact with glass with via speech and swipe on the frame, thought I did fund an app that allows you to open URLs and ‘Push’ them to glass, which allows for “speech-less” interaction.
and  more…

So essentially Glass takes photos, videos, navigation assistance, Google searches reads and sends text messages, engage in social media interaction  and location based contextual engagement model – very much in the “Now” mode. But a lot of these features are heavily dependent on connectivity – when offline Glass can ONLY take photos and Videos. So this tell me one of limitation, which is by design, I think. So it is evident that in any enterprise context, this is a not only a design imperative but a fundamental shift in Mobile application design paradigm. Something, which I intend to research and explore with a  point of view. But Google has a few guidelines (discussed below) for developing application (or I would say interaction themes) for Glass, which IMHO are reasonable and can be applied and extended to a next generation of Wearables.

Note : Google Glass – announced alliance with Ray-ban maker Luxottica, aiming to move glass from “explorer edition’ to mainstream ‘consumer edition’. This move will greatly move wider adoption of internet-connected Glass spectacles into a widely available, stylish consumer product. So we can expect a evolution is more seamless integrated design with lifestyle.

Less is more: Glass Application Guidelines:

Google has four primary guidelines for developing for Glass4:

1. Design for Glass: Do not design for another device, like a Smartphone, and import to Glass. Because Glass is unique in how users interact with it, Google suggests that you developer directly for it.

2. Don’t get in the way: Apps should be for users, not for developers. Don’t be pushy with notifications and other information.

3. Timely: The goal is to provide users with up-to-date information with Glass. Make sure your app responds with correct information in a timely manner.

4. Avoid the unexpected: Imagine walking down the street and Glass send you an unexpected notification. This can be annoying or even dangerous. Make sure the user has given explicit permission to be notified in Glass.

 So as I ponder upon application of Wearable technology like Glass in an enterprise with a use case and a define business model, I am also focusing how adaptability of these wearables. So below are some use cases  - some of these I have read in my research, some of these are discussed in my conversation with clients and some I am envisioning as we design Mobile solutions.

Retail:
Use cases like inventory management, competitive ‘in-store’ comparison, and areas such as apparel procurement etc, can utilize Glass technology to not only enhance productivity of the employees but streamline business processes and aim towards a real time reaction system – this can be priceless in a price sensitive industry with low margins.

Healthcare:
 I find use of Glass like technology (yes with more maturity) to find its use in Health care. I can only imagine achievement of a Watson as a Cognitive-computing platform, which enabled not only information but also inference at ‘our fingertips’, and Wearable technology enable the notion of “Inference in a blink”.

Cognitive Computing Platform + Agile, elastic and Robust Middleware and data platform + Wearable Mobile technology = Robust healthcare Access Platform

Manufacturing:
Use cases like inventory management, access to MSDS(Material Safety Data Sheets), Access to repair manuals, ability to report malfunctioning machines with remote diagnostic and repairs by an off site SME, all leading to a efficiently run, on–demand access to critical information that impact the health and well being of the workers on the shop floor.

Energy (Oil and Natural Gas):
Industry with heavy reliance on scientific and geological data with equal emphasis like that of a manufacturing base with real production targets – Energy industry, which can also greatly benefit from on–demand access geological, scientific and empirical data during exploration – to make better decisions and all the use case of manufacturing post exploration and during production – can greatly benefit from Wearable ruggedized technology.
And More…

 As  I explore and use Google Glass, I think of enterprise design imperatives as these Wearable technology goes mainstream, below is my initial attempt to list some design imperatives for the next frontier of Mobile technology:


As we design platform and solutions for Wearable technology:

1.    Design --- not just of the app but end-to-end becomes of paramount focus.
2.    It is more about Data ( Structured and Unstructured) and Network ( Connectivity)  as much  as it is about the interface.
3.    Interaction  and NOT interface is on the forefront
4.    “The NOW” factor – truly integrating with systems of engagement – that are Just “Aware”
5.    True Digital persona – fitting into a enterprise digital strategy. Which aims to seek pervasive digital connections in which the individual technologies (cloud, near field communications, mobile, big data, etc.)
6.    Aim to deliver an experience that looks and feels an awful lot like our natural behavior
7.    Rich Digital Density - more connections between people, places, information, and things (aka digital density).
And this is just the beginning…

As always, I look forward to your comments, likes and critique.

Have  a great week ahead!
:)

Nitin

References and Interesting read: