Skip to Content

When I got up this morning and checked Twitter the first thing I saw is that we have announced plans to acquire Syclo, a leading provider of enterprise mobile applications and technologies.This is yet another exciting step into making enterprises more agile by adding mobile solutions.

We now have an impressive inventory of mobility options that customers and developers can pick from:

Of course there’s even more out there, like upcoming RESTification of just about every ERP service, mobile applications on HANA, or DJ’s Alternative Dispatcher Layer (ADL) for ABAP. That, plus the countless mobility activities I either forgot to mention or simply don’t know about.

In the halls of Walldorf, Palo Alto and Bangalore, the buzz is mobile. If you’re a developer working on mobile Apps you need to make a choice now: is it still worth trying to build the next Angry Birds to succeed in the consumer space (or Instagram, if you like ๐Ÿ˜‰ ), or is it the time to play with the big boys and help Enterprises get a grip at mobilizing their workforce?

Of course, deciding on the right option is still not easy, and developers may find it hard to get into developing for SAP. There are a few initiatives underway to make that easier, though (apart from the overview pages I linked to above): There’s a downloadable Netweaver Gateway trial version (some SAP knowledge required ๐Ÿ˜‰ ) plus a Netweaver Gateway Demo System with a few pre-configured scenarios. Also, the SAPUI5 Trial can be downloaded for free.

That should be enough to start fooling around, don’t you think? I would also be interested to see what you can build with something like tiggzi.

So, what do you think? Is that enough to get you started? Or have you started already and are ready to show off your progress (like this great series of blogs here)? Let’s see what we can do, shall we? Show us your stuff, join the discussions on SCN!

To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Steve Rumsby

    All of these possibilities for mobile development are great news for developers. You get to use the best tool for the job at hand, plus there are lots of toys to play with. What more do you need?

    But from the customer perspective I don’t see this as quite such good news. If we want to get into mobile development, or if we want to buy in mobile apps or development skills, we could end up having to support all of these various mobile development platforms. And paying the licence fees for them. And implementing whatever server support is needed for them.

    Is it simply unrealistic to think that we could have a single mobile development platform? It seems like it can’t be done right now, but is it likely that in the future all these options will converge? If so, when? Having so much choice is going to put some customers off making the leap into mobile, for fear of choosing the wrong platform and having to switch. Having new options appearing so often – SUP was meant to be the mobile platform, right? – is going to make people wary of investing in something now that might be made obsolete by SAP’s next purchase.

  2. Christopher Solomon

    Interesting. A lot of “movement” in this area. Curious to see what comes out of it and if in the end, it’s not just a lot of aimless running around for the sake of running around. ๐Ÿ˜‰

  3. Twan van den Broek

    Thanks Frank for the ‘wake up call’. For us at SAP NetWeaver techies the world is changing fast, but changing in a very interesting direction. We’ll have to start running like never before ๐Ÿ˜‰

  4. Joao Sousa

    So many solutions also lead to client confusion. Some years ago if you wanted to implement a budget planning you couldn’t even get a straight answer from SAP about which solution was “the future” (talking about Outlooksoft vs Integrated Planning for example).

    Right now Sybase is the hot mobile SAP solution, but when you read SAP is going to buy another “ leading provider of enterprise mobile applications and technologies“, you have to wonder what exactly clients should buy.

    Product consolidation is essential and SAP is doing a very poor job managing their product offering. Putting it simply, there are just too many brands right now.

  5. Former Member


    i think the best thing will be to stick with ABAP and get the mobile apps using

    • BSP +JQuery
    • Portal on Device

    what makes me think like this? simple example of ESS/MSS, First we implemented in WD Java and also made custom apps in WDJ. now we implement WD ABAP.So SAP Starts somethings in new technologies and eventually it comes back to ABAP ๐Ÿ™‚



    1. Joao Sousa

      As someone who uses SE80 and Netweaver Developer Studio I have to say the reason is obvious. SE80 can be ugly, SE80 can lack some of the functionality of NWDS, but at least it’s stable.

      Developing in NWDS is a nightmare, with constant JavaNullExceptions, errors you have to pray have no impact, NWDI that sometimes fails to synchronize changes … my dear old SE80.

      And yes, fully updated NWDS.


Leave a Reply