msc mobile blog - Responses

Re: Keep it native!

Luis Cabrera — Sat, 02 Oct 2010 00:45:56 GMT

Hello Alexander,

I Completely agree with you. I would summarize it as "Don't be lazy, go native". Four months later (and, apparently, for many more months to come), people are still figuring out ways of NOT building native apps. Even more now that HTML5 is in the spotlight. We've also written some other arguments in favor of Native apps here: http://bit.ly/bUlaIV

Perhaps what most don't realize is that building a native app doesn't necessarily mean to wire everything "natively" from the backend all the way down to the device. That's what platforms are there for.

Keep writing!

Sybase or Syclo Two MEAP Provider?

Anonymous — Tue, 18 May 2010 18:37:42 GMT

Good buy Sybase. Goodbye Syclo?

It’s the question at the top of many people’s mind - SAP customers, partners, prospects, employees and the analyst community. Now that SAP has shown their hand and made a clear decision to acquire market leading MEAP provider Sybase for 6 big ones, and yes $6 billion, what will happen to the future of the Syclo MEAP Agentry platform? Is there any reason to have two MEAP providers? Two technology platforms, two market messages, two support organizations, two road maps? If I were SAP what would I intend to do? Promote a third party solution MEAP (Syclo) or their own MEAP application? I wonder!

An SAP spokesman said today: "We remain committed to our open ecosystem strategy and enabling customer choice by working with a range of partners that drive customer value.’’ We all know that when an organization pays billions of dollars to acquire another company their shareholders are going to look for fast return on investment. Do customers really have a choice on mobile?

I spent time today with Sybase and the SAP community at SAPPHIRE and there was a common perception that in the long term (meaning as soon as the acquisition is completed) the de-facto standard for mobilisation of SAP back end systems is going to be Sybase, whether it’s for SAP CRM, SAP Enterprise Asset Management or field service..

It is also expected that in the long term SAP will jointly develop the field services and mobile asset management capabilities that up to now Syclo has specialized in. It is also expected that SAP will eventually push customers toward an SAP-Sybase platform. SAP has the knowledge, technology and people to develop the Syclo EAM template functionality without much trouble.

RIM have the customer base to ensure its continued growth irrespective of SAP and Syclo.

Two questions which are still unclear are what will happen to RIM and SAP Mobil Asset Management? Will SAP build on the SAP NetWeaver platform using Sybase? Whatever the answer, one thing is clear, SAP finally has a company wide mobile strategy. Unlike the short-lived co-innovation partnership, this one is here to say, like it or hate it. Well done SAP, customers can really benefit from this acquisition.

Re: Hoa: Offline applications with HTML 5

Paddy2k — Wed, 24 Mar 2010 09:41:24 GMT

I had done a similar exercise for Google Gears and will port that code over to HTML5 with the aid of your tutorial. Android 2.0 and above now support HTML5 so this demo works perfectly. Now all the major smartfone operating systems have a common platform on which to build.

Re: Integrate 3rd Party Mobile Development Tools with SAP

Paul Horan — Fri, 18 Sep 2009 11:37:45 GMT

Sybase has SUP - Sybase Unwired Platform, that makes mobilization of SAP via BAPI calls a snap. SUP also handles device management, provisioning, security, etc.

Re: iPhone OS 3.0 - still not Enterprise ready

Ratna Chengappa — Sun, 21 Jun 2009 07:54:53 GMT

In my experience, most enterprise IT managers opt for cheaper and easily replaceable devices. The iPhone does not fall into either of these categories (as I write I find it is currently out of stock at the UK's largest supplier due to unprecedented demand).

Hence cost & supply might be the deciding factors in most organisations

Ratna