We have spoken many times on this blog about our release of GeoMobile for ArcGIS. The link below will take you to a more detailed discussion:
Our logic for the release was:
- To demonstrate a custom ArcGIS mobile application
- Build a cross platform mobile GIS app or one code base which runs on multiple platforms; iOS, Android, Blackberry
- Model the app on the ESRI ArGIS Flex viewer; a flexible framework allows widgets to be easily dropped into the mobile app to extend functionality
So an extensible mobile ArcGIS framework for data visualization, search, query, update/editing, data collection etc. We never imagined it to be an out of the box mobile app; a generic $4.99 mobile app. It was a first step into the mobile GIS world for a number of our engineers. And ultimately resulted in us moving from a PC Web focused application development company to fully mobile developers. So we’ve put all our eggs in one basket; mobile. Taking a risk? We don’t think so. Our focus is location data, mobile enhances what we can now provide clients. One day, not far off, we think the location and GIS community will wonder how they ever got their jobs done stuck in an office. There is another side to this, and that is the potential location and mobile presents for all apps. As Ryan Kim at GigaOM.com said in early 2011:
“We’re still a ways off from our prediction that every mobile app will have location integration. But we’re seeing that potential reality take shape more and more”
The GIS tag may be less used with time. GIS Developer may simply be replaced by Location Focused Developer.
We have digressed from the thrust of this post. In a recent article entitled ‘Hot Topics in Mobile GIS’ we reprinted some of the conversations we had with clients in 2011:
Maybe the ‘hottest item’ at the minute is online/offline mobile data collection and editing. There are an increasing number of apps now available which offer the ability to load and edit shapefiles. Many have a GIS tag; Wolf GIS, GIS Pro, GISRoam. We wrote a review of some at the link below:
and compared them in action in this video:
Our main finding was that most are built for iOS only. And all used the Google maps API. Google maps for GIS I hear you cry. Indeed. Google maps was never designed for GIS. The issues we highlight in the comparison video above are a result of the use of the Google maps API. So cool mobile apps built using the wrong API.
Flexible Framework using a Mobile GIS API
To build a mobile GIS application you need to use a GIS API. Extending the functionality of this mobile GIS application you need a flexible framework. To cut costs as users broaden the mobile devices and platforms they use; you need a cross platform solution.
This has become our company mantra!
Nah, but it makes much sense.
GeoMobile for ArcGIS taught us much about the future of mobile GIS. The feedback we are getting from users has guided our thinking as we move forward. Having a flexible cross platform mobile ArcGIS framework has allowed us to extend this work to fit client needs. As already said, we don’t imagine releasing an off the shelf mobile GIS app for $4.99. We build custom mobile GIS solutions to fit client needs. We work closely with ESRI, and have a good feel for what is coming in the next 12 months. This helps us gear our solutions to where they are moving.
Our next big release will be GeoMobile for GeoServer; an open source version of GeoMobile for ArcGIS. We are looking at both OpenLayers and OpenScales as potential client (software) API’s. A flexible cross platform mobile open source GIS framework.
We live in exciting (flexible) times.
Let us know your thoughts on mobile GIS. Maybe you are developing cool mobile GIS apps. Or looking for a mobile GIS solution. Contact us