Reader Response on Open Source and Mobile Devices

---

Hi there, Eric.

I would just like to mention my own personal experience and view on your statement about being on my own when using Open Source GIS software.

I am using both commercial and open source in my organization, I pay quite a bit for the commercial support in the form of an annual maintenance fee. I don’t pay anything for support for the open source products I use, not because there aren’t any offerings, but it is more difficult do convince my company´s hierarchy to buy the same kind of annual support contract for open source products.

Now, even under these circumstances, I get more results from the “unofficial” open source support from mailing lists then from the commercial support contract.

Let me give you some examples on commercial support:

1. I discovered, to my surprise, the latest version of the commercial product didn’t support wms services on computers with international settings (comma instead of dot as decimal separator). I waited a year and a half for that)
2. I have found that the commercial product is 100% slower (half the speed) with a supported database product than the open source equivalent. The support told me that it was the database’s fault (which was aggravating). I had to log the sql statements and prove them wrong. I’m still waiting for a solution. There is no guarantee this will be solved. I was informed an enhancement request was filled but it is not publicly viewable.

On the other hand, I had some problems with the open source product, without any support contract. I’m seeing a quick release cycle that solves a good portion of known bugs and problems, almost always solving my problem in the process. But the best thing that happened to me is when my particular bug is fixed under 24h and I can immediately download the fixed version. I even had a situation where I needed a new feature and someone developed an initial version in a week. A day later, one of the main developers included a similar feature in the core of the program.

So, really, stating you are on your own when using open source products is really just not true and really a disservice to your audience when you state that so firmly.

From my own experience, I am convinced there is a problem with changing our usual procedures. Instead of buying a product that includes one year of some kind of support (many times ineffective), and  then paying a fee annually, we must switch to using a free product, whose cost is that when we change it for the better we contribute that back to the rest of the users. And we can and should buy commercial support when our usage pattern reaches the level when it makes sense to acquire this type of contract.

Thank you for your article. Other than this particular point, I enjoyed reading it.

Best regards,

Duarte – Portugal

Eric,

Just read your July 1 article “Expert Advice: Mobile Computing on the Rise.” Seems every time you write on mobile I feel compelled to send you an email follow up. This time’s no exception.

I too remember the Grid computer days when a tablet’s heft was in tons, handwriting recognition involved mystical templates that helped you shape your letters just so with the stylus, screen visibility outdoors was essentially non-existent and battery life diminished at the same rapid rate as water evaporating in the southwestern desert sun on a 115 degree day. I absolute agree that WinMobile’s future is questionable and even if that OS does manage to avoid emulating dinosaurs it will likely remain relegated to professional uses only with high price points both for hardware to run that OS and for the software that makes owning a device powered by it marginally worthwhile. Ruggedized hardware is the best thing going for WinMobile in my mind and I believe that’s all that can save it from becoming fossilized. But that advantage is beginning to resemble the Garmin/TomTom legacy losing traction nowadays.

Where we differ, however, is that I’m already willing to go WAY out on the limb and give the trophy for victory in the mobile war to Android devices. Here’s why.

My first smartphone was an Apple iPhone 3GS and when it came time to move up to a new phone, I wrestled quite a long time between Samsung Android-based offerings and the very new at that time Apple 4s. If you guess that I went for the Android for my second smartphone and that’s why I’m emailing you, you’d be wrong. Although I absolutely hate several limitations of iOS-based phones (no removable battery, throttling back to near non-existence of Bluetooth by Apple, and zero removable storage specifically), I went iOS yet again primarily because of Siri (which I’ve not been that thrilled with) and the fact I already had many iOS apps that I’d paid for and understood how to use.

But when it came time to buy my first non-Windows (… and I’m not talking WinMobile) tablet, I reversed course totally. I purchased a Toshiba Thrive which I really love. I don’t even bother to pack my Win7 laptop for most business trips nowadays. I have a small twelve inch laptop case with a Bluetooth mouse and keyboard and I just grab the Thrive and the case and I’m good to go. When I first got the Android OS tablet, many of the apps that were readily available in iOS were not there. By that I’m not talking about DropBox or the Weather Channel app … I’m taking specialized category level not there. I was blown away, for example, that I couldn’t find a camera app that geotagged photos taken with the Thrive. Over time, however, that gap has narrowed so it’s far less a factor and I really like the fact that I can take my 128 GB SDXC chip on which I have all my geospatial professional, university teaching and personal files and pop it out of my work Win7 laptop and into the Thrive and head out across the county. QuickOffice lets me read MS Office docs and make changes on the go. Right now, I’d not trade my year and a half old Thrive for a new retina display iPAD even if Apple paid me what the new IPAD costs if I had to give up my Thrive.

Knowing that just my enthusiasm about someday being able to take a terabyte of geospatial data on an Android tablet with me to the field will probably not convince you to join my declaration of victory, I’ll finally get to the point of this email.

The fact is that MANY vendors are introducing this summer ruggedized Google-based tablets. Contrast that to the fact that iPADs will always have to be encased in some kind of protective shell. That’s the piece of the story that I think you missed. To me this is a very big deal. A Panasonic Toughbook Android offering compared to the delicate iPAD for use in my geography is a no brainer. I also don’t expect to see too many daylight optimized iPAD screens coming out anytime soon from Apple.  Also MIA in your piece was easy of development.  Friends and I are building a new geospatial apps company and so we’ve been done a bit of development on both Android and iOS. So far we’ve used Flash Builder and created FLEX-based apps just by checking the two appropriate boxes for iOS and Android Mobile. Then it came time to test the apps. I can tell you that the venture capital sized fee required, the CDC DNA sample, TSA full body scan and NSA screening one must endure plus the length of Apple’s approval process to be able to just push a simple test app out to a few devices from iTunes compared to the far more pleasurable experience fielding a test Google app leave me never wanting to write again for iOS. And then there are the UDIDs for every darn iOS device you plan on testing your code on. Developing on iOS is a royal pain compared to Android. Pain of development is the second thing not in your write up.

Yes I find the lack of being able to create a folder unifying programs of a general type (telecom apps, office apps, etc.) on one of the Thrive’s home screens to be a bit of a pain but I really like being able to switch out my Thrive’s battery when I need a new one or I need one that’s freshly charged to head out into the field.

So … I predict loudly (because unlike you I have nothing to lose in doing so), Google will win the field mobile race beating Apple as you said but I’m thinking more like three years and I believe ruggedized hardware designed specifically for field use that cost more than a Thrive but far less than a Getac Win7 convertible or a Trimble GeoXT will be a key factor in that victory.  And if ArcPAD for Android or a Trimble GeoXT with Android comes out…best get out of the way ‘cause a Tsunami’s coming.

Keep up the great articles and I hope you find my thinking interesting,

Larry – West Virginia USA

---

 

I largely agree with Larry. I think the mobile operating system war will likely be won by Android (market research predictions support this), and Windows Embedded Handheld might end up being the choice for “professional” users. Why? It’s all about the apps. Of course, there are tons of professional apps written for Windows Mobile (Windows Embedded Handheld will run them) and we’re starting to see geospatial apps being written for Android. Yes, there are geospatial apps written for iOS too, but if you look at the potential upside, I keep hearing that Apple just isn’t a developer-friendly environment, and as Larry mentions, Apple will always be focused on the consumer market, so don’t expect a ruggedized version of the iPad anytime soon. However, on the flip side, one Apple developer relayed to me that it’s very helpful that Apple retains strict control over app development for iOS devices:

“When Apple upgrades IOS, it is pushed out to all devices (pad/pod/phone) and the updates are very well documented in terms of what changed. He said users just agree and they all get it, very rarely does someone say no to the upgrade. So, you have basically one version to program for/test at a time. Long story short, you only have to program the different screens and the rest is standardized. The info is there to tell you what the device is, so it is easy to have one app look diff or add something for a pad w/larger screen than on the phone.

For android, the OS is open, so every manufacturer and/or provider and every different phone from them can have a different/unique OS. It starts out the same but some add features others don’t and most modify the code to suit their needs. Then, upgrades only happen if the manufacturer and/or provider decide they want to upgrade them and which ones (old phones might not get upgraded for example).  So, lots of Androids out there are not on the same/most current OS. Users can’t just do upgrade themselves, a generic version might not work right on their phone and most people don’t look for upgrades anyway.”

Over the next six months, it’s going to be really interesting to watch what kid of geospatial apps are introduced for iOS and Android. That will be the main driver behind the adoption of mobile devices based on iOS and Android. It will also be interesting to watch how many new devices are introduced that are running Windows Embedded Handheld/Windows Mobile.