John M. Wargo

Twitter Feed

johnwargo: Here we go - First-time smartphone buyers favor Android over iOS: http://t.co/mQwxRHDP
johnwargo: Ummm, eating a handful of Dark Chocolate M&M's So good!
johnwargo: Working on the book's preface, hard 2 keep myself from saying 'the book you hold in your hand' since many won't ever actually hold the book
johnwargo: When sending an email to a group, why is it that Lotus Notes is smart enough to not send me a copy if I'm in the group but Outlook isn't?
johnwargo: Staying at a hotel without a gym. Ugh. I didn't even think to check to see if they had one, assumed they did.
Home
Gartner, MEAP and RIM PDF Print E-mail
Wednesday, 11 May 2011 08:01

In my role at AT&T I work with customers looking to mobilize Business to Consumer (B2C) and Business to Business (B2B) applications using Mobile Enterprise Application Platforms (MEAP). MEAP is a term I believe was coined by Gartner a few years back and since it’s their term, their publications on MEAP are the industry’s reference on the topic.

In December, 2009 Gartner published a MEAP Magic Quadrant document that talked about the different MEAP vendors, their capabilities and how they were faring in the market. It wasn’t until April, 2011 that the next edition of that publication was published and it contained some interesting information.

First of all, for those of you who understand Garter’s Magic Quadrants, any vendor wants to be in the upper right corner of the quadrant. That’s the place for the movers and shakers, the innovators and the ones to watch. For this year’s MEAP Magic Quadrant, the upper right corner is empty.  Yep, empty. None of the MEAP vendors are perceived by Gartner to be leaders in the space. I thought that was weird. How can you have 10 or so vendors and none of them being leaders?

Anyway, the thing that caught my attention was how out of touch Gartner is about what RIM is doing in the market. In the 2011 MEAP Magic Quadrant document (Magic Quadrant for Mobile Enterprise Application Platforms) and another document I just read this morning called Critical Capabilities for Mobile Enterprise Application Platforms (ID #G00212257) Gartner refers to the RIM MDS Runtime client and development tools. The interesting thing about that is that RIM discontinued the MDS Runtime development tools and runtime client in December 2009. So in this case, Gartner is making statements and assessing RIM’s capabilities using products that RIM discontinued about 18 months ago.

How can Gartner be effective and accurate if they base their analysis on products that are no longer even produced or supported by the vendors? That makes no sense to me. The MDS Runtime tools were great and I am disappointed that they’re no longer available, but they’re gone now – never to return. Gartner needs to pay attention.

 
PhoneGap PDF Print E-mail
Tuesday, 10 May 2011 20:22

I started working with PhoneGap today. I've been poking around the framework for a while now and I finally got around to actually working with it. As with most Open Source projects, I find that the documentation is sorely lacking.

I'm building a PhoneGap application that uses the Domino RESTful web service I documented in a previous article on this site (Mobilizing Domino Data Using REST: Part 1). I'll be using what I'm learning now in one of my sessions at the View Domino Developer Conference. Stay tuned.

 
What Were they Thinking #8 – Part 2 PDF Print E-mail
Friday, 06 May 2011 07:30

A few hours after posting my article about the BlackBerry World conference application, RIM released an update to the program. I can’t imagine what change would be so important to release an update to the application in the middle of a four day conference, but they did. Must have been a bug.

When I opened the application the first couple of times after installing the update, instead of the default ‘please wait 2-3 minutes while the application loads’ that I complained so much about, the application showed a blank screen (with a web browser cursor for some bizarre reason) for a really long time before opening. I imagine that it was somehow updating the existing data in the application or upgrading a local database, but it took a really long time without any indication on the screen what was happening. I even pulled the battery and tried again to see if I was having a problem with my device.

That’s not good programming.

One of the things I noticed as I worked with the application was that the developer didn’t make any accommodation for changing the orientation of the device. I use a BlackBerry Torch 9800, from AT&T of course, and it has a touch screen and slide out keyboard. I can change the orientation of the device and get better screen real estate for the browser and some applications.  When you look at the application in portrait mode, you’ll see something similar to what’s shown in Figure 1.


Figure 1


When you switch the device to landscape orientation, you’ll see a screen similar to the one shown in Figure 2.


Figure 2

Notice that the screen doesn’t orient itself to make full use of the screen real estate available when the device is in landscape orientation. This makes no sense to me. BlackBerry Device Software has API’s that allow the developer to react to orientation changes since BlackBerry Device Software 4.7. These API’s allow a developer to adjust the layout of their application’s screens when the user rotates the device. The application clearly adjusts the header so it looks correct in this orientation, but why didn’t they make it so the home screen options adjust their layout as well?  What’s the sense in making me scroll down to access the third row of icons when I have the room to fit at least two of them in that blank space to the right.

It’s just sloppy programming – how could this have been missed? Did they expect that the user would never turn their BlackBerry touch-screen devices on their side?

Notice too that in Figure 2 you can see the pointer (the arrow cursor) on the screen. It’s a touch screen device, why show non-touch screen controls when running on a touch screen device? Another example of sloppy programming. When touch is not available, that’s a useful navigational element. On touch screens, in this case I’ve touched between icons to bring up the cursor, it’s not needed. There’s no need to show the cursor when I’ve touched the screen, I can’t use my finger to move the cursor (not that I’d want to), so it should be turned off when running on this device. 

It’s RIM’s app, they released it in support of their premier customer conference. They’re spending a lot of time and money promoting their concept of Super Apps http://us.blackberry.com/developers/started/super_apps.jsp but when they release an app for their conference, the hire a developer that can’t make accommodation for orientation changes or integration with the device calendar?  That’s sloppy, very sloppy.

 
Multiple-login Smartphones PDF Print E-mail
Thursday, 05 May 2011 06:58

Why can’t you login to your smartphone? You can password protect them (either set by the user or required by an enterprise administrator), but why can’t you log into them?

I got started in the mobile apps world many years ago. RIM hired me to be a mobile apps evangelist for AT&T’s customers. I worked with mobile apps at BoxTone and in my current role at AT&T I work with mobile application platforms that allow organizations to build one application that runs natively on multiple mobile device platforms. Over the years, the whole mobile apps story got easier and easier – organizations were getting over their concerns about mobile apps and actually starting to do something interesting with them.

Unfortunately now that Enterprises have to deal with the iPhone and Android platforms, many organizations have essentially put the kibosh on applications initiatives while they figure out the whole mobile device management (MDM) thing.

I’ve been in meetings and conference sessions lately that deal with device management and it’s clearly something that organizations are struggling with. BlackBerry shops have it easy since the BlackBerry Enterprise Server (BES) takes care of so many of the things IT and Security departments require, but with today’s proliferation of device types, the BES isn’t enough. With this week’s announcement of RIM’s acquisition of Ubitexx, it’s possible that RIM can solve this problem – who knows.

What’s interesting though is how the ultimate solution to most organization’s mobile device management problems is clearly known, but it’s impossible for third party software developers (such as the market’s MDM providers) to implement. The ultimate solution has to be a core part of the device operating system, not an add-on that has to work around existing API’s and device limitations. What smartphone manufacturers have to do is provide the means for the smartphone users to have the ability to define distinct logins for multiple users on the device.

For the enterprise, an enterprise aware smartphone would have the means to allow the user to have a personal login (with access to all of your personal data and accounts) and another separate corporate login with access to work-specific information (data, applications and accounts).  As the user logs into either account, he or she is exposed to only the data that’s associated with the account. This makes perfect sense – give me complete separation between my work and personal activities and most of the enterprise’s concerns go away.

The phone would have to support managing multiple phone numbers, but that technology exists already today. The user would have their personal phone number associated with one account and a work mobile number or a work mobile and office numbers associated with the enterprise login. When the phone rings, the device would have to be able to switch on the fly to the personality associated with the phone number that’s ringing or at least be able to access the caller ID information (from the address book) stored  with the account associated with the phone number so it can be displayed to the user.

Common applications (such as email, calendar, contacts and more) can be shared across multiple logins, but individual custom apps could be installed in a private memory area. There would be no common data shared between logins though except perhaps log files.

The same feature can be used to make tablets more useful as well. It makes no sense for consumers why tablet manufacturers don’t allow devices to have multiple accounts. Any family with an Android tablet should be able to define multiple accounts and easily switch between them. That way, I can setup my preferences and account information (mail, facebook, linkedin and more) and when my wife or one of my children logs into the device they see their individual settings instead of mine. Why isn’t that possible?

Clearly it’s a direct decision made by device manufacturers – these tablets are so popular and sexy, but limiting this capability forces people to buy more tablets. I have one, my wife would have one and each child would need one too. Implementing multiple logins, while completely possible, would result in reduced sales for the device manufacturers. That’s ultimately what’s keeping manufacturers from implementing this in my opinion.

What would have to change in order to support this feature I’m describing? Well, devices would need more memory; I’m guessing twice as much. There wouldn’t need to be changes in the processing power and battery for the device, it’s still doing the same amount of work. I imagine when you login to a second account, the applications being executed under the first login would need to be suspended or terminated. Everything else stays the same, right?

Carriers benefit since the device will be provisioned with multiple mobile numbers, so there’s increased revenue for the carriers.

Let’s start lobbying the device manufacturers for this capability. It makes so much more sense than what we have today. I’d love to be able to share an iPad with my wife and family.

 
<< Start < 11 13 15 16 17 18 19 20 > End >>

Page 13 of 51

InformIT (Pearson Education)