Showing posts with label mobile micro-apps. Show all posts
Showing posts with label mobile micro-apps. Show all posts

Mobile Middleware for Instant Value or Mobile Micro-Apps

Mobile middleware is more than synchronizing databases and providing basic application integration. It needs to include support for business process extensions, and it must provide a set of features and functions that support lightweight, "Instant Value" or "Mobile Micro-Apps" smartphone applications.

 
There are many features and functions that are needed by mobile workers that are not easily supported by smartphone operating systems like iPhone or BlackBerry. Often the data set is large and the software application is an ERP.  The mobile user does not need access to the full ERP or the full data set, just a subset.  In these cases it would be useful to have a mobile middleware layer that recognizes the needs of the mobile user and provides an optimized mobile application with functionality that supports either browser based or mobile micro-apps.

It seems there is a need for a new middleware layer that is designed to support a wide range of requirements to address the limitations of lightweight and browser based smartphone apps.

Within the SAP ecosystem I am hearing a lot about this concept from the likes of  Vivido Labs  and Leapfactor.

Leapfactor says their mobile middleware layer forwards and broadcasts staged digital content collected at a location and delivers it to any designated consignees, on any smartphone, and always with high availability based on a secure and scalable platform.  They state that their solution relies on four fundamental technologies: 
  1. LeapApps -  mobile micro apps for smartphones
  2. LeapShell - an SDK that accelerates development and portability to any mobile OS
  3. Leap Central - a secure cloud-based service-processing component
  4. LeapAgent - securely connects and authenticates LeapCentral with an enterprise
I spent a lot of time working on mobility projects that utilized Sybases' SUP (mobile middleware).  The mobile applications were "thick" clients with mobile databases on smartphones to hold data and synchronize data with the back office database application.  Our mobile applications often had complex business processes and business rules built into the mobile applications to ensure field work was done correctly.  These rules were stored in the mobile database in the thick client.
 
Where are all of these business rules and business processes stored for "Instant Value" and "mobile micro-apps" for smartphones?  Do these lightweight mobile applications simply ignore business rules and business processes, or is this functionality provided in a smartphone middleware layer in the cloud?  These are the things I ponder on a Wednesday morning.
 
Do you see a need for a mobile middleware layer that is specifically designed to support business rules and business processes for mobile micro-apps?
 
*************************************************
Kevin Benedict, CEO Netcentric Strategies LLC
SAP Mentor, SAP Top Contributor, Mobile Industry Analyst
http://www.netcentric-strategies.com/
www.linkedin.com/in/kevinbenedict
http://twitter.com/krbenedict
***Full Disclosure: I am an independent mobility consultant and Web 2.0 marketing expert. I work with and have worked with many of the companies mentioned in my articles. ***************************************************

Mobile Expert Interview Series: Leapfactor's Lionel Carrasco

I was in Miami, Florida a few weeks ago and was able to meet up with Lionel Carrasco and do some sailing. Lionel Carrasco is the CEO and founder of Leapfactor, an Enterprise mobility player and partner of SAP. Lionel shared his thoughts and insights while the sun was setting over Miami.

I asked Lionel how he originally got into the mobility industry. He explained that he managed the development, as an SAP systems integrator CTO, of a number of large enterprise mobility projects in the Direct Store Delivery, Logistics Execution, and Sales Force Automation space. These projects were in the USA, Latin America, and Europe. In the course of designing, developing, deploying and supporting these applications, he learned much. He believes this experience will be invaluable to SAP and Leapfactor customers.

I asked Lionel how he would describe Leapfactor. He answered that Leapfactor understands that cloud computing and mobility should come together. This joining together will enable large enterprises to take advantage of mobility in ways similar to consumers. He believes enterprises should mobilize employees, partners, and consumers. He believes enterprises should consider mobilizing their entire ecosystem as there is value to be recognized in all areas of it.

What differentiates Leapfactor from other SAP mobility partners? Lionel answered that Leapfactor is a native cloud based mobile offering that can handle a large scale volume of users, even in on premises implementation models. They do their best to remove the complexity from a mobile enterprise, yet they offer the required enterprise class security and compliance capabilities. He added that Leapfactor does not think from the "inside out." “Looking from the inside out,” according to Lionel, “Makes you think like an ERP running on a desktop computer and simply extending features outside the four walls which limits you.”

"We are thinking of not just one mobile application but hundreds!" Lionel emphasized. "Developers can build them, customers can build them, our partners can build them, and we can build them on behalf of our customers as well."

Lionel emphasized again and again that the economics of mobile applications, the way they are developed, deployed and supported is completely different now than they were even a few months back. I interpreted that to mean not many mobility vendors have recognized or accepted the new paradigms and realities yet. He believes the new business models that Leapfactor is bringing to the SAP marketplace are significant, not only for customers but SAP and the partners ecosystem.

I asked Lionel about his target audiences. His answer was end users, end users, and end users. He believes that end users need to realize value with the very first click of a mobile application, and the enterprise should receive their value second. It is a view that suggests the end users are the secret to an enterprise's success. If the end user likes the mobile application, then the enterprise will realize the value.

Lionel said that Leapfactor is here to create value for the business. The winners will be those enterprises that create apps for the edges of the processes because the core is already taken care of and automated by ERPs. The edges are where the enterprise relates to customers and partners and where the opportunities for mobility lie. He then added that it is also very important to make the IT department the heroes, because they will be able to respond to business demands faster instead of managing the complexity and maintenance budgets.

I asked about Leapfactor's mobile applications. He listed them as follows: 
  • Business Indicators - Mobilized business intelligence for all types of users from the executives down to blue collar workers.
  • Mobile Alerts - When action and acknowledge is required and email is not enough.
  • Mobile Approvals - For any system and process that requires an approval. 
He then shared that one of the most interesting new mobile applications would be released in time for Sapphire. It is a mobile social intelligence application for large enterprises.

I asked Lionel if he viewed Leapfactor as a development platform. He answered that it is a mobile deployment platform that can rapidly scale up and scale down depending on the customer's and software developer's needs. “We added some development accelerators and user interface libraries to increase productivity and reduce complexity for developers, but that does not make us a development platform. We rely on the native development tools of each mobile OS,” he said.

It is a deployment platform that mobile application developers can use to deploy the applications they have developed without the need to build a complete and expensive SaaS infrastructure themselves.

One of the most interesting thoughts that Lionel shared was this, "Applications and lines of code are increasingly disposable. The code is less and less important since mobile applications can be developed quickly and with relatively little investment." Hmmm . . . where is the value then? Lionel believes the value will be in the ability to economically and quickly deploy and support mobile applications – applications that offer immediate value to the end users and that are easily distributed. I think he was only half joking but he said, "Mobile applications can be easily thrown away as newer and better mobile applications are developed." It seems to be the personification of agile.

Lionel sees one of the key roles of Leapfactor is to help other mobile software developers manage deployments, compliance issues, and testing and then supporting their operational environments through the Leapfactor platform.

One of the key values in the Leapfactor platform is its ability to meter and measure the use of mobile applications. This information can be used for any number of emerging business models that may include charging the user based on transaction numbers, volume of data used, etc.

I asked Lionel for his opinion on the role of mobile micro-apps. He said mobile micro-apps are easy to maintain, easy to deploy, and easy to develop. This means developers can rapidly bring value and incremental improvements to users. He added that sharing the consumer approach to mobile applications with large enterprises also offers a lot of value.

Lionel refers to "thick client" mobile applications as "obese" mobile applications. He said it is wrong to include too many features in one code base for mobile devices. Obese applications are nightmares to maintain and take far too long to develop, test and deliver. He added, "Developers need to stop thinking like Windows Desktop application developers and change their paradigms to think like a mobile user."

In my past I have been involved in many "obese" mobile application development projects. I can share that the customer requirements always seemed to change faster than you could design, develop, test, and deploy them.

I asked Lionel for his opinions on MEAPs (mobile enterprise application platforms). He said there is still a need for MEAPs on some projects, but the development is very expensive. He believes MEAPs were mostly designed for older development paradigms, and they need to change to support a more consumer-oriented approach for enterprises of today.

I asked Lionel to look into the future and tell me what he sees. He offered that mobility is already pervasive. He said most less-developed nations have more mobile phones than landlines. He believes that soon all mobile phones will be smartphones.

He also believes that enterprises will begin building management functionality that enables a separation between work and play on the same mobile phone. Perhaps it is a work phone until 5:00 p.m. and then switches to personal settings with personal applications. I find this whole area of thinking very interesting.

What is SAP doing right? Lionel said SAP is focused on mobility in 2010, which is a very good thing. They are demonstrating that they believe it is important, and although they have been slow to embrace mobility and cloud computing, they seem to be picking up speed. They are rallying the SAP troops and the customer base which is all good. Lionel added, “I have had the chance to meet Kevin Nix, who now leads the SAP mobile strategy, and it was refreshing to hear his fresh ideas and real world experiences.”

Lionel believes that SAP's partner strategy for mobile applications is the right strategy. "They realize they cannot do it all and have invited partners to fill the gaps" he added. "Past failures that SAP experienced in mobility were due to SAP following old paradigms."

What can we expect from Leapfactor in 2010? Lionel provided the following list:
  • Leapfactor will show the industry and customers more proof points that Leapfactor's model and technology is the right approach. It will be disruptive to current thinking, but it is the right approach.
  • Leapfactor will deliver more killer apps, but more importantly, customers and partners will do the same.
  • Leapfactor will be adding many customers, small and extra large ones.
  • Leapfactor will publicly release a Developer Kit that has been limited to date to only a few partners.
  • Additional RIM and Android apps will be released this year.
If there is a mobile expert that you think I should interview please contact me!

Read more interviews with mobile experts:
***************************************************
Kevin Benedict
Author of the report Enterprise Mobile Data Solutions, 2009
Mobile Strategy Consultant, Mobile Industry Analyst and Web 2.0 Marketing Expert
http://www.netcentric-strategies.com/
www.linkedin.com/in/kevinbenedict
twitter: http://twitter.com/krbenedict
http://kevinbenedict.ulitzer.com/
http://mobileenterprisestrategies.blogspot.com/
***Full Disclosure: I am an independent mobility consultant and Web 2.0 marketing expert. I work with and have worked with many of the companies mentioned in my articles. ***************************************************

Mobile Micro-Applications vs Thick Mobile Clients

As I have shared before, my background was in the MEAP (mobile enterprise application platform) world.  We used different acronyms, some not repeatable in this family friendly blog, but it was the same thing as today's MEAPs.  I have managed development projects where the mobile applications we delivered could be considered a full ERP in many places.  It was painful and expensive, but it worked.  Our customers had hundreds of route sales, service technicians, and delivery folks walking around carrying full functional ERPs on their ruggedized mobile handheld computers.

The application I am referring to above consisted of the following:
  • Mobile sales force automation application
  • Mobile order entry application
  • Mobile invoicing
  • Mobile proof-of-delivery application
  • Mobile work order management application
  • Mobile inventory management system
  • Mobile price and promotion management application
  • Mobile enterprise asset management application
  • Mobile CRM to access customer service and support issues
MEAPs and thick client mobile applications certainly have their place, but there was so much customization that this finished mobile application was probably out-dated by the time we delivered it.  If any part of our mobile application needed changed, the entire mobile application had to be updated and re-tested.  With a mobile application that big and complex, the opportunities for bugs were endless.  We had to charge a fortune to deliver it.

Our customer wanted a thick mobile client application that could work in a connected and disconnected mode so that their employees could work whether there was connectivity with the internet or not.  Three years ago there were not a lot of options.  As a result there were a lot of thick mobile clients delivered.

With this particulary mobile application, the training requirements were huge.  The mobile workforce needed to understand every aspect of their mobile ERP before it could be effectively used.  You can image the level of IT support for the first six months.

It will be interesting to see how thick clients and MEAPs evolve.  There are some very active debates on the SAP Enterprise Mobility group on LinkedIn on this subject.

Where do MEAPs stop and mobile micro-applications start?  If I were to develop that same mobile application today, would I use nine mobile micro-applications rather than try to build all of the features and functionality into one giant mobile application?  Good question! 

SAP's partners are on both sides of this question. SAP partners like Vivido Labs and Leapfactor focus mostly on mobile micro-applications.  Sybase and Syclo focus mostly on thick mobile clients, while Sky Technologies seems to be hedging their bets with both thick mobile clients and mobile micro-apps.

It will be an interesting evolution to watch!

***************************************************
Kevin Benedict
Author of the report Enterprise Mobile Data Solutions, 2009
Mobile Strategy Consultant, Mobile Industry Analyst and Web 2.0 Marketing Expert
http://www.netcentric-strategies.com/
www.linkedin.com/in/kevinbenedict
twitter: http://twitter.com/krbenedict  
http://kevinbenedict.ulitzer.com/
http://mobileenterprisestrategies.blogspot.com/

***Full Disclosure: I am an independent mobility consultant and Web 2.0 marketing expert. I work with and have worked with many of the companies mentioned in my articles.
**************************************************

Redbox, M2M and Mobile SAP Micro-Apps

M2M is not only a cool acronym, kind of James Bond like, but a very interesting category in the wireless industry.  M2M in this context means machine-to-machine wireless connectivity.  A few other terms that describe this category are "the Internet of Objects" or the "Internet of Things."  All of these terms relate to machines that can talk or exchange data with other machines via wireless connectivity.

One strange example that I wrote about a few months ago was a bathroom scale that would wirelessly tweet your body weight to your Twitter list every time you weighed yourself.  The scale, a machine, was collecting data and sending it automatically via a wireless connection to another machine (server).

A recent example that I found particularly interesting was Redbox.  These are the DVD rental kiosks that we see everywhere now days. Did you know that Redbox machines are M2M enabled?  You can go to the Redbox website, find a kiosk near you that has a movie you want and reserve it online.  You can also use their micro-app for iPhones to find a movie in a kiosk near you and rent it.

A quick digression - look for a large number of new mobile micro-apps to be announced at SAP's Sapphire event in May.  Companies like Vivido Labs and Sky Technologies, and many others, will be releasing many new mobile micro-apps for iPhones, BlackBerrys, Android and other OSs.  These are typically small, one purpose or business process, mobile apps that are integrated with SAP.

Here in Boise, Idaho there is a local success story involving M2M with a company called Telemetric.  Here is their description:  Telemetric provides wireless remote monitoring and control of equipment and machinery using cellular networks.  We provide solutions that enable electric, water and gas utilities and their customers to measure, monitor and control usage of valuable resources.  Our solutions improve system efficiency, asset management, speed up responses to service interruptions and equipment problems, and automate reporting functions resulting in lower operating costs and more reliable service.

Telemetric develops monitoring equipment that measures and reports wirelessly to other machines.  Managers can watch dashboards and see the measurements from remote equipment.

The bottom line is that field data collection does not always require a person with a ruggedized handheld computer to be traveling around collecting data. High value assets and equipment can be set-up with monitoring devices that report their status to other machines and servers that can be programmed to do certain things based upon the data coming in.  I am now writing a new analyst report on M2M to be released in June 2010.

Related articles:
***************************************************
Kevin Benedict
Author of the report Enterprise Mobile Data Solutions, 2009
Mobile Strategy Consultant, Mobile Industry Analyst and Web 2.0 Marketing Expert
http://www.netcentric-strategies.com/
www.linkedin.com/in/kevinbenedict
twitter: http://twitter.com/krbenedict
http://kevinbenedict.ulitzer.com/
http://mobileenterprisestrategies.blogspot.com/

***Full Disclosure: I am an independent mobility consultant and Web 2.0 marketing expert. I work with and have worked with many of the companies mentioned in my articles.
**************************************************

Interviews with Kevin Benedict