Commentary

Alexander Wolfe
 

Podcast: Sybase, SAP Talk Smartphone Apps

I've been tardy in posting this five-minute podcast, where Sybase chief marketing officer Raj Nathan and SAP vice president Vinay Iyer delve into their joint deal to improve access to SAP's smartphone apps. (Sybase is providing the middleware.) But you should listen, because the "smartphone is the computer" is a meme that's rapidly gaining traction from deals like this.

I've been tardy in posting this five-minute podcast, where Sybase chief marketing officer Raj Nathan and SAP vice president Vinay Iyer delve into their joint deal to improve access to SAP's smartphone apps. (Sybase is providing the middleware.) But you should listen, because the "smartphone is the computer" is a meme that's rapidly gaining traction from deals like this.By pressing the tiny play button here you can listen to my chat with Raj and Vinay.

You can go here, to Mary Hayes Weier's March 11 news story, where she outlines this specifics of the spot news. Basically, it's like I said above. SAP apps, which are already mobilized (is that a word?) to some extent are going to go more native -- i.e., they'll have more functionality and work better -- thanks to middleware from Sybase. The latter will do the grunt work of managing integration between the SAP apps and the multiple mobile device (iPhone, Blackberry, Windows Mobile) on which they'll run.


More Global CIO Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Users won't see fruits of this deal until late this year or early next year. That kind of time lag is pretty consistent with what I discovered when I reported the InformationWeek cover story last fall, Is The Smartphone Your Next Computer?. Namely, there's such intense interest in moving forward on smartphone apps, that user desires, technical discussions, and vendor deal-making are somewhat ahead of the actual end-user applications.

I don't expect this state to obtain for long, though. There are two trends that are driving the imminent acceleration of mobile apps. One is technical, the other economic.

Let's take the second one first. The economic accelerator here is that the current recession is not only flattening workforces, but causing the idea of "empowered workforce" to become a real business imperative. People simply don't have the time to operate as if the old top-down model was still in play. Plus, they can't travel to meetings as much as they used to. Everyone's under the gun, so everyone's empowered and we're tilting towards an "all mobility, all the time" mode of operation.

For that to run successfully, though, the mobile apps have to be there. As Raj Nathan points out in the podcast, to date this has been doable for big companies, with bucks and resources to roll their own custom smartphone apps. The significance of deals like SAP/Sybase, as well as other relationships like Oracle partnership with Antenna Software, and Apple's opening up of its iPhone developer's program, is that the playing field is widening so that many more businesses can get started on getting the mobile apps they need.

Anyway, so in closing I don't want to go overboard and give the impression that we're there yet. (Although most enterprise software vendors would be quick to argue this point, and note they that do indeed have mobile apps now.) What I really mean is that we're still in an early, but very fast moving, stage of this brave new mobile world where we all will be doing a lot more than email on our smartphones, and very soon.

As SAP's Vinay Iyer sums it up in the podcast: "I think we are on the cusp of major innovation, of bringing business process information to workers globally on any device, anywhere, anytime."

What's your take? Let me know, by leaving a comment below or e-mailing me directly at alex@alexwolfe.net.

Like this blog? Subscribe to its RSS feed: (here)

For a microblogging experience, follow my daily observations on Twitter: (@awolfe58)

 My videos on ( YouTube)

 Facebook 

  LinkedIn

Alex Wolfe is editor-in-chief of InformationWeek.com.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links