Annex

March 22, 2018

iOS App

Enterprise level development often produces applications with overlapping features as different business groups fund different projects, but share common "big picture" objectives. Annex attempts to merge 4 native iOS applications into one cohesive experience for capturing data in the field.

screens1

screens2

branding

The difference between a robust app and a bloated one is always the experience. While no new functionality was introduced, the application feels powerful, yet simple to use. It's also a more modular structure, so expanding and adding features won't break the experience. The branding and fresh coat of paint also help the app feel modern and fun, taking a human-centered approach to data capture.

architecture

Annex uses a flat architecture based on abstract concepts of viewing, adding, or manipulating data and isn't bogged down by how current systems function. These 3 states are on equal footing at the app root, and launch experiences that are laser-focused on the task at hand.

I mapped the features to flows stemming from the flat root states: view the map, capture some data, or do a task. The map is just that, and you can manipulate it to see as much or little data as you'd like. It's essentially a "read-only" state. The capture state gives a menu of types of data that can be captured. I grouped observation types based on physical attributes (rather than data attributes as was currently in use).

wireframes

After an exhaustive inventory of the current apps, I built a matrix of features and personas who use them and put them in buckets based on the above concepts. I found that some users only want to view information on a map and filter data layers based on a task done outside the app. Other users have a to-do list and only care about crossing items off (and adding data to a database).