Showing posts with label IBM. Show all posts
Showing posts with label IBM. Show all posts

Apple iOS and the Enterprise - Latest Developments

My friend and mobile expert Dave Akka shares his insights on the latest Apple strategies and developments to support the enterprise in this guest article.

Following the recent Apple WWDC developer conference, it’s worth looking at what they are doing to make their products more attractive to the enterprise?

iOS: The accidental leader?

As NetApp’s Mike Elgan noted recently, iOS became the leading operating system for enterprise mobility almost by accident, although it might be more accurate to say that it wasn't originally designed for the enterprise or expected to be such a hit.  The iPhone was released as a consumer device like the iPod into a world of feature phones with a small smartphone market dominated by Nokia’s Symbian, while the Blackberry was the fully-locked-down enterprise mobility device of choice.  No one expected that the consumers who bought the iPhone would consider it to be so much better than their work devices that they would break every policy imaginable to use them at work, and kickstart the BYOD or Bring Your Own Device phenomenon.

The iPhone became the dominant enterprise mobile platform for several reasons, including the ease of developing corporate apps, the iPhone’s popularity as a status symbol that made it the choice for senior managers who were able to insist on using it, and a few enterprise-friendly features that were added to iOS over time.  However the biggest reason is that it has a large, loyal customer base that love the device and feel it makes them more productive.

In the pre-BYOD world, it was assumed that consumers wanted usability, photo quality and a wide choice of applications (or the ability to do anything with the device), whereas enterprise users weren't important because it was all about management tools and easy integration into corporate systems. BYOD showed that enterprise users are also consumers, and want the same things from a work phone that they do from a personal one.

A good demonstration of this is that the first time I saw BYOD in action was at the end of a meeting when one participant took out his iPhone, took a photo of the whiteboard we had covered in notes, and sent it to everyone in the meeting.  The reaction around the table was “what a useful device; what else can we do with it?” That team had woken up to the potential of BYOD and enterprise mobility.

The iPad took off in a similar way: originally sold as a media consumption device, it has become the enterprise mobility device to take to business meetings with an array of apps that let you present, collaborate, take notes and network far more effectively than was previously possible, and you can even catch up with that latest TV series on the train on the way home.

Possibly as important as any enterprise functionality is the way that Apple sells and supports iOS devices for business in its retail stores.  I recently had a problem with my iPhone and while it was being repaired (which happened easily and seamlessly, by the way) the store staff were keen to discuss whether I used it for business, what apps and functionality I liked, what requirements it filled and so on. This showed a real commitment to making iOS devices easy for business users to get started with.  iOS devices in the enterprise also lead to Mac sales as you need to use a Mac in order to deploy enterprise apps and settings to iOS.

Apple Adding Enterprise Features

The recent preview of iOS8 shows that Apple is now very deliberately targeting the enterprise mobility market both by reinforcing the user experience that got it this far but also by providing features that make it a more attractive choice for IT.

The newly-announced Device Enrollment Program allows corporate-issued iOS devices to automatically configure and access corporate apps, reducing the time and support needed to get a new device working; and LDAP is a key component as it brings auditability to the iOS deployment with account control and authentication.

Meanwhile, the ability to passcode-protect corporate data on the device, by protecting access to the calendar, contacts, mail, third-party apps and more mean greater security for the enterprise while fingerprint unlocking means the user doesn’t have a headache accessing that data.  VIP messages allow users to keep track of important conversations more easily and even small things like automatic VPN connectivity could make a big difference to the user.

Overall, iOS8 brings advances with:

  • Simplified IT administration and security, between MDM tools; enterprise grade security including encryption, per app iCloud controls and certificate-based single sign-on; and managed book and PDFs to easily deliver content
  • Improved application development, with the TouchID API, document provider APIs, content filtering and extensibility, not to mention the new Swift language
  • Greater ease of use and productivity with improved mail, seamless working between iOS and Mac, improved calendar and peer-to-peer AirPlay

I don't want to go into too much technical detail here, but if you are interested you can find a more detailed breakdown here.

From the enterprise mobility perspective, features like Continuity, which allows users to pick up work where they left off across multiple Apple devices and the ability to create purpose-built keyboards for specific task-related apps could help increase productivity.

iOS is unlikely to completely own the enterprise mobility space in a BYOD world, but it is certainly set to continue its strong performance.

In addition, Apple and IBM announced a partnership yesterday, to aggressively go after the enterprise market.  Here is an excerpt from The New York Times, "In a deal that could deepen Apple’s sales to corporations and strengthen IBM’s position in business software, the two companies announced a wide-ranging partnership intended to spread advanced mobile and data analysis technology in the corporate world."

David Akka, MBA, M.Sc.
Managing Director, Magic Software Enterprises UK  Ltd.
dave_akka@magicsoftware.com

Thanks for sharing Dave!

************************************************************************
Kevin Benedict
Writer, Speaker, Editor
Senior Analyst, Digital Transformation, EBA, Center for the Future of Work Cognizant
View my profile on LinkedIn
Learn about mobile strategies at MobileEnterpriseStrategies.com
Follow me on Twitter @krbenedict
Join the Linkedin Group Strategic Enterprise Mobility
Join the Google+ Community Mobile Enterprise Strategies
Recommended Strategy Book Code Halos
Recommended iPad App Code Halos for iPads

***Full Disclosure: These are my personal opinions. No company is silly enough to claim them. I am a mobility and digital transformation analyst, consultant and writer. I work with and have worked with many of the companies mentioned in my articles.

More on IBM's Acquisition of Mobility Vendor Worklight

Last week I wrote my initial analysis of IBM's announced acquisition of mobility vendor Worklight.  Yesterday, I received a written reply from Worklight's Austin Ford that adds important information that is worth sharing.  Here is his reply in its entirety.

I'm happy to see your interests in our company! To address some questions, let's first mention that Worklight is actually predominantly used as an MCAP play (true story, most deployment usage of WL is B2C). Yes we're also a MEAP, and these distinctions in Gartner's language (they claim they coined both acronyms) are getting blended into 1 this year.


For some comparisons to the Sybase SUP, this might address the high level stuff:
 *Worklight outputs are web languages (HTML5) and usage of open or closed libraries and / or / combination using the actual SDK's from the mobile OS manufacturers. This means the outputs are actual true native code and all of it, not virtual machines and proprietary translation code like many others or limited native functionality like SUP.
*SUP = "write once, run everywhere" mentality. Proprietary outputs from a proprietary IDE experience even though it's based on Eclipse. Uh oh, you're married and already on restriction.  *Worklight = web languages (CSS, HTML, Javascript, libraries) + native SDK's together in Eclipse. Java and web developers normally ramp quickly. Also developers are motivated to learn native SDK's I've found, the skills can be leveraged anywhere the native SDK's are used again.
*SUP = extremely deep experience and hours required to get an end result that's almost as good as a true native or hybrid.
*Worklight has invested heavily in full runtime components for accessing device functionality, many we engineered in house. For example we contributed to the Phonegap project (now sponsored by Apache) and that is one of many runtime components embedded in our production environment.
*SUP doesn't have deep runtime API capability. In partial defense, for the apps they're traditionally called on to mobilize (SAP MEAP), user experience hasn't been that critical.

Of course there are other Worklight favoring differentiators like openness to support & materials, ease of use, full production environment included (no upsell to particular add on components), SLA's, flexibility in installations, and just generally good people with a great product of high value to enterprises and ISV's.

Good current write-up by Pete Lagana (Excellis Interactive) here: http://www.asugnews.com/2012/01/04/developing-sap-mobile-apps-sybase-unwired-platform-vs-native/

~Austin Ford
austinf@worklight.com

I want to thank Austin for taking the time to share with all of us!  These are definitely exciting times in the world of enterprise mobility and I look forward to watching events unfold in 2012.
*************************************************************
Kevin Benedict, Independent Mobile Industry Analyst, Consultant and SAP Mentor Volunteer
Follow me on Twitter @krbenedict
Full Disclosure: I am an independent mobility analyst, consultant and blogger. I work with and have worked with many of the companies mentioned in my articles.

IBM to Acquire Mobility Vendor Worklight - An Analysis

IBM has jumped into the MEAP (mobile enterprise application platform) competition with yesterday’s announced intent to acquire MEAP vendor Worklight.   Worklight is headquartered in New York and was founded in 2006 by CEO Shahar Kaminitz.  Worklight's software supports HTML5, hybrid and native applications for smartphones and tablets with industry-standard technologies and tools.   Their solutions include an Eclipse-based software IDE (integrated development environment), mobile middleware, mobile solution management and analytics.

Worklight Studio competes with Appcelerator, Verivo (formerly Pyxis Mobile), Sybase Unwired Platform (SAP), Antenna, Syclo, ClickSoftware, Kony Solutions, Rhomobile (Motorola), Webalo and other mobility vendors that are experiencing rapid growth.

The deal size was not disclosed by IBM or Worklight, but the Israeli website Globes (www.globes.co.il) reported the acquisition to be $50-60 million.  Worklight raised $21 million in investment capital, from investors Genesis Partners, Pitango Venture Capital, Index Ventures, and Shlomo Kramer.  Globe also estimated 2011 revenues for Worklight at between $5-10 million (http://www.globes.co.il/serveen/globes/docview.asp?did=1000720723).


My analysis is that all ERP vendors need a standardized approach for supporting mobility.  Mobility, and MEAPs in particular, are far too strategic to leave up to partner ecosystems to deliver.  SAP acquired Sybase, IBM will acquire Worklight, and we are all awaiting Oracle’s expected 2012 move to acquire a MEAP vendor.

Interesting note, I cannot think of many situations where an ERP vendor bought a mobile apps company.  I am told that SAP's proposed acquisition of SuccessFactor will involve some mobile apps, but have yet to see them.  ERP vendors seem to want to buy the middleware, so they can standardize integration, syncing, security and management, and leave most apps to their partner ecosystem.

In a recent IBM study of more than 3,000 global CIOs, 75 percent of respondents identified mobility solutions as one of their top spending priorities.  Nearly all of the global analyst and research firms are also reporting enterprise mobility to be a top three priority.  In the Enterprise Mobility Survey 2011 that I conducted in September of 2011, 80% of survey respondents said enterprise mobility was "very important" to "critical" to their company's future success.

IBM officials said with this acquisition, IBM's mobile offerings will span mobile application development, integration, security and management.  Dow Jones Newswire reported on an internal memo from IBM’s senior vice president in charge of middleware software, Robert LeBlanc that highlighted their ambitions, “"Now is the time to make IBM essential in the era of mobile computing."

I had the privilege of interviewing Worklight’s COO Kurt Daniel about 15 months ago and published the interview on this site.  Here are some excerpts that you may find interesting given this week's news.


Worklight has developed a MEAP (mobile enterprise application platform) and a mobile SDK (software development kit), not for their own use, but rather for systems integrators and end customers to use to develop their own enterprise mobility solutions.  They want to be a technology company, not a mobile application company.

Kevin: What are your areas of responsibilities at WorkLight?
Kurt:  I look after our worldwide business channels, partnerships, sales and marketing.
Kevin:  Tell me about your solutions.
Kurt:  We have the WorkLight Studio, WorkLight Server and WorkLight console.  ISVs and OEM partners use these solutions to build their own packaged mobility applications.
Kevin:  How do you avoid competing with your partners in the mobility market?
Kurt:  We don't sell applications.  We are not experts on ERPS or other backend systems.  We focus on developing the best mobile technology possible, not services or mobile applications.
Kevin:  How do you fund your start-up business in the early years without generating revenue from services and mobile applications?
Kurt: We raised over $17 million.  That affords us the opportunity to invest in the technology without losing focus by delivering services and enduser solutions.
Kevin:  How do you keep your users loyal to your technology?
Kurt:  We provide them with a platform and SDK that supports the latest modern devices.  We provide them with great productivity tools that enable the same code base to be used across multiple devices and mobile operating systems.  We offer trial versions for 60 days.
Kevin:  Where do you see mobility going in the next 18-24 months?
Kurt: Enterprises are going to need to support a larger number of mobile devices and mobile operating systems.  They will need to support iPads, tablets of all kinds, Android and many more mobile apps.  Internally, companies will be launching large numbers of their own mobile applications that were developed in-house.
Kevin: Who do you compete with?
Kurt:  In-house development teams, Sybase and Antenna.
Kevin:  In conclusion, where does your company fit in the enterprise mobility ecosystem?
Kurt:  WorkLight is a 100 percent technology focused company.  We develop a horizontal MEAP.


It is fascinating to ponder Worklight's strategy.  They decided to build a new and powerful MEAP, but not to provide services or sell mobile apps to end users.  They chose to use their investment capital to focus exclusively on developing technology and developer support.   That is a rare strategy.  Sybase mostly followed that strategy with their embedded mobile database and synchronization business (iAnywhere and former Extended Systems) and was purchased by SAP, and now Worklight who followed a similar strategy will be acquired by IBM.  What does this tell us?  Perhaps ERP vendors don't want the burden of supporting a large MEAP or mobile app enduser base that does not fit their traditional customer profile.  They would rather just acquire the technology stack?  What do you think?

Most MEAP vendors depend on services and end user app sales to help cover expenses as they develop and mature their solutions and channels.  Worklight refused to follow that path.   It doesn't appear they had yet reached profitability, since it seems they took in another $4 million in investor funding in the past year, but they did accept IBM's offer as their exit strategy.  They committed to focus on the technology, rather than indulge the temptation (and distraction) to grab short term end user sales.

End user mobile app sales are sexy.  They get the press and show well, but ultimately I think the MEAPs themselves are the mobile market consolidation points.  Not just the mobile middleware, but the IDEs.  The integrated development environments that are used to design and develop the apps.  Some mobility vendors like ClickSoftware and Syclo actually support several choices of mobile middleware under their IDEs.  The customers often only see the IDE, but underneath the covers are middleware options.  SAP and the Sybase Unwired Platform also offer numerous choices (SUP, NetWeaver Gateway, Sybase 365, etc.) for middleware in their architecture.

If all the large ERP companies are going to ultimately acquire their own MEAP solution, that means MEAP market fragmentation will be hardened along ERP lines.  If that is the case, would mobility vendors that focus on mobile end user applications find it necessary to support all the major MEAPs if they want to sell into those markets?  That would be expensive!!!  If that is how the market evolves, then it seems cloud based ERP-to-mobile app integration hubs would be worth a consideration.  Mobile app developers would simply connect to one cloud based integration hub that integrates with all the ERPs.  Wow, this line of thinking reminds me of my early days working with EDI/B2B translators and EDI hubs.

It will be interesting to watch the choices companies will make that have a mix of different business solutions and ERPs across their IT landscape.

If I have any bad data or information in this article please correct me!

Please share your thoughts and ideas with us!!!


*************************************************************
Kevin Benedict, Independent Mobile Industry Analyst, Consultant and SAP Mentor Volunteer
Follow me on Twitter @krbenedict
Full Disclosure: I am an independent mobility analyst, consultant and blogger. I work with and have worked with many of the companies mentioned in my articles.

Reporting on Enterprise Mobility from Singapore

Singapore's Skyline
Early this morning (2 AM) I landed in Singapore, took a taxi to my hotel and slept for a few hours.  I got out of bed at 6 AM and walked around the city as the sun rose.  Later in the day, I had the pleasure of conducting a workshop on enterprise mobility to a full house in the Screening Room which is not far from Singapore's China Town.

The weather was hot and humid today, but there was no rain until late in the afternoon.  My traveling companions said we could walk to the workshop venue, but a mile walk in this humidity would have left us dripping in sweat so we opted for a taxi ride.

It was great to be guided by Patrick Carroll on this trip as he grew up in Singapore and attended school here.

The event was organized and sponsored by the good folks at K2 Partnering and it was well attended with folks from SAP, IBM, British Telecom, Johnson Controls, Cognizant, Spansion, Kulicke and Soffa and many others attending.  We had a lively crowd that was willing to ask questions and share experiences over lunch and during the workshop.

Jeff Wallace with Cognizant
(right) and Patrick Carroll (left)
with K2 Partnering

One of our workshop participants shared a story about how 5,000 rugged devices were purchased and deployed to their field services teams, but that the field services teams had refused to use them.  The project ended up failing partly because the users did not want to carry the heavy and ugly ruggedized "bricks."

Another attendee confirmed my observations that most companies avoid using the IT department for mobile B2C (business to consumer) app development and implementations.  It seems most B2C projects are outsourced by the marketing departments.

IBM, SAP and Cognizant all shared that they were expanding their efforts around enterprise mobility in Asia and that there is a great deal of interest among their customer bases.

Singapore is a very interesting mix of cultures and a hub for global commerce.  You can't walk a block without passing dozens of delicious looking restaurants with exotic foods from all over the globe.

Many western companies have their Asian headquarters in Singapore as English is the official language and it is a business friendly central location.

These enterprise mobility workshops that I have been conducting seem to be both useful and popular as many of the attendees were asking for the dates of future workshops that their colleagues could attend.  I cover mobility platforms and frameworks, mobile security, mobile SDKs, mobile strategies and supporting a real-time enterprise.

Side note #1:  The K2 Partnering team in Singapore also voted Korean food as their favorite.  What is up with that?

Side note #2:  My Singapore hotel shower head is directly over the toilet.  How very efficient.

Side note #3: Foot massages hurt.

Side note #4:  My spicy chicken dinner included about 50% chicken bones.

Side note #5: If you hang up your dress shirts overnight they are wrinkle free in the morning due to the humidity.

Side note #6:  A one way street means you must drive in reverse to go against the traffic.




*************************************************************
Kevin Benedict, Independent Mobile Industry Analyst, Consultant and SAP Mentor Volunteer
Follow me on Twitter @krbenedict
Full Disclosure: I am an independent mobility analyst, consultant and blogger. I work with and have worked with many of the companies mentioned in my articles.

Interviews with Kevin Benedict