Mappt v2.1 Now Available

Version 2.1 has finally found it’s way to the Google Play store!  This version contains range of improvements and bug fixes.

As always, you can download the latest version of Mappt from the Google Play store:



We’ve been busy!  Read on to find out what we done did.

Marker Icons Can Now Be Customised

You can now customise the icon used to display markers, just in case the standard map pin wasn’t doing it for you.  This offers an extremely helpful at-a-glance aspect to markers, as demonstrated in this image below.

Screenshot showing customisable marker icons in Mappt

New Line Styles for Lines and Polygons

Lines and polygons can now be drawn using a set of predefined line styles, such as dotted, dashed, and even dotted and dashed!  At the same time!  Welcome to 2014.

We also support several other line styles, as seen in the screenshot, below.

Screenshot showing line and polygon styles in Mappt

Line styles are an early access preview, so you may find some quirks here and there.  As always, we are welcome to suggestions, so be sure to let us know your feedback!

Feature Labels

You can now specify a label to display for features!  This is specified in the properties of the containing layer, allowing you to choose the value of an attribute, or even the name of the feature itself.

Here’s our previous Mines example, this time with labels turned on.

Screenshot showing feature labels in Mappt

Bug Fixes, Other Improvements and a Goat

As always, we’ve eliminated bugs and made small tweaks here and there to improve the user experience.

We’re now hard at work on the next version of Mappt, much like this goat is hard at work on goating like a goat.

Goat standing on a tree stump.

We’re running out of simian pics, so we’re breaking tradition and going with a goat instead!

Mappt v2.0.0.9 Now Available

Version has been released!  This version contains a few bug fixes and improvements and brings with a it new licensing model.

You can download the latest version of Mappt from the Google Play store:


Read on to find out more about this version!

Features Now Display Their Styling

The layer list now shows the styling applied to a particular item, making it easier to pair the listed features with their visual representations on the map.

This works well when combined with our Thematic Mapping tool (previously known as Classifications), as can be seen in the following image, which shows geographical areas styled by their area.

Screenshot showing feature style indicators.

The colouring used in the icons on the left matches the styling used in the rendered features on the right.

The New Tier-Based Licensing Model

Given the volume of functionality that we have added over the past year-and-a-bit, as well as the exciting upcoming features on our roadmap, we have decided to split the Mappt licensing model into a tier-based model.

A tiered model allows you to choose the level of functionality in Mappt that you need.  The tiers, and their features, are listed below.

Mappt Features by Licence Tiers

Bug Fixes

As always, we tweaked a few things here and there and fixed more bugs than we introduced: net result positive.

Our unrelated simian picture for this post is whatever this thing is:

Lar Gibbon

It’s an unhappy gibbon, apparently.

Mappt v1.5 Now Available

The Mappt simians, having toiled in their underground banana caves, have produced version 1.5 of Mappt for Android!

You can download the latest version of Mappt from the Google Play store:



This version bring performance improvements in the handling of large datasets, as well as a few features:

Tap to Select Features in the Map

Finally, you can tap features in the map to select them!  No more hunting through the layer list, peering, squinting, trying to find the marker that tells you where you left your car last night.

You can also long-press on features to open their properties!

Reordering Layers and Drawing Order

Mappt now respects the order of layers and features in the layer list, drawing them in a bottom-up fashion.  This means that layers “on top” in the layer list will be on top in the map view.

Along with this, we’ve added buttons to allow you to reorder your layers and features, and even shift features between layers!

Drawing Enhancements

We’ve added a few new tools to make drawing features a bit easier.

Firstly, you can now abort changes made when editing a polygon or line!  This means you can edit a feature, and if you mess it up, simply press the Abort button to revert the feature back to it’s original, pre-edit, shape.

We’ve also added a button that will, when in edit mode, allow you to append a point to the current polygon or line at the current crosshair position.  When combined with the GPS follow tool, this is handy for “walking out” the boundaries of a polygon, or the path of a line, dropping points at your current location as you go.

Bug Fixes

We fixed some bugs, too, but that’s pretty boring – so here’s a snapshot of the team at work, “fixing” bugs:

Look at us, hard at work, fixing bugs. Delicious, delicious, bugs.

Look at us, hard at work, fixing bugs. Delicious, delicious, bugs.

The Mappt Development Cycle

Software development is easy, but managing software development is hard.  When asked for timelines on feature requests, software developers will offer vague answers such as “soon”, “next release” or the ever-helpful “it’s on the roadmap,” expertly avoiding a definitive answer as well as the best politician.

As Mappt is a new product, feature requests come in thick and fast, much faster than our team of handsome developers can implement.  Because of this, prioritisation becomes key.

All feature requests (and bug requests) made to the Mappt team, be they verbal, written or mimed, are catalogued into our internal “backlog,” to be reviewed, estimated, prioritised and scheduled for implementation at a later date.

When work on the current set of features and bug fixes is complete, the Mappt team sits down at the Table of Meeting and looks through each item in the backlog, fleshing out the details and putting an estimate against each one.


The Mappt team meets.

Each item is then prioritised against the others, giving us a rough “order of implementation.”  We then calculate how much developer time we have to address these items, based on developer availability, as well as set a target date for implementation.  From these figures, we can confidently determine exactly which items will be implemented (and bugs fixed) by the target date.  The team as a whole agrees to the defined set of work, making a promise to deliver on-time, and pets are given up as collateral.

This is all roughly based on the principles of the Agile method of software development.

The whole process usually takes anywhere from 2 to 6 weeks, depending on the urgency of publishing a new version to the Google Play store.  This means that at the time a feature request comes in, even in ideal circumstances, it may be a few months before it finds its way into a public Mappt build.

Of course, there are always exceptions.  In cases where items are critical to client needs, we can accelerate development or offer custom builds.  We consider these types of situation on a needs basis, so feel free to contact any of the team if you need some special love.