You are here

Every product decision has a route

Geonavix Consultation helps organisations work out where they are, where they could go and which way is safest, before money goes into code. Then we help build and publish the mobile apps, web products and interfaces that the chosen route calls for.

Grid A1 · Legend

The map legend: what we do

Six symbols, six kinds of help. Most projects use three or four of them, in an order that depends on where you are starting from.

Route consultation

Structured exploration of options: build, buy, adapt or wait. We map the terrain, name the risks and recommend a route with reasons you can check.

Mobile apps

iOS and Android apps, cross-platform or native depending on what the route demands, built in short legs with a working build at each stop.

Web products

Web applications, portals and internal tools that run in any browser and load quickly on ordinary connections.

Wayfinding UX

Interface and experience design treated as signage: people should always know where they are, where they can go and how to get back.

Publishing support

App store releases, listing preparation, privacy declarations and the documentation that gets a product across the border.

Support after arrival

Maintenance, fixes and adjustments under agreed terms, handled during working hours from base camp.

Compass 01 · Decision route finder

Which route fits your idea?

Five questions, one suggested route with its first four waypoints. Change any answer to see how the route shifts.

Who will use it most?
How often will they use it?
Must it work without signal?
Is there already a system doing part of this?
How sure are you about what users need?

Grid A2 · Why routes

Most expensive mistakes are wrong turns, not bad code

Organisations rarely fail at software because developers cannot type. They fail because they built the wrong thing, or the right thing in the wrong order, or something that already existed off the shelf. Each of those is a navigation error made early, when it would have been cheap to check the map.

Our consulting work makes those early choices visible. We put the options side by side, show what each costs in time, money and risk, and recommend one, with the reasoning written down so you can disagree with it specifically.

A paper map of fenland with a brass compass and orange string between waypoints
Illustrative generated image, not our office or client material.

Grid B1 · The survey

We start with a survey, not a sales pitch

A first conversation focuses on where you are now: who your users are, what they do today, which systems are already in place and which decisions are still open. We then propose a discovery phase sized to the uncertainty, sometimes a few days, sometimes a few weeks.

Discovery produces a short report, a journey map and usually a clickable prototype, so the decision about what to build rests on something people have actually tried. You can stop there and take the findings anywhere. How an expedition runs.

Grid B2 · Mobile & web

Three paths through mobile and web

The choice of platform is a route decision with lasting consequences. These are the three paths we most often recommend, and when.

Path N

Native app

For products that live on the device: heavy camera use, sensors, background location, demanding performance. Highest reach into each platform, highest cost to maintain two codebases.

Path X

Cross-platform app

One shared codebase for iOS and Android. Sensible for most products built on lists, forms, accounts and content, with native modules where needed.

Path W

Web first

A responsive web product reaching every device without stores. Ideal for occasional use, internal tools and testing demand before an app.

Mobile and web routes in detail

Grid C1 · Wayfinding

Interfaces designed like good signage

The best path signs answer three questions at a glance. So should every screen. We design interfaces using the same principles that guide walkers across open country.

You are here

Clear titles, current location in navigation, progress in multi-step tasks.

Where next

One obvious next action per screen; alternatives visible but quieter.

Way back

Undo, back and cancel that never lose what someone typed.

Hazards

Warnings before destructive actions, written in plain English.

Our wayfinding UX approach

Compass 02 · Build, buy or adapt

Weigh the three roads

Give each criterion a weight (0–5) and score each option (0–5). The totals are weight times score. Rename criteria by editing your own copy offline; the defaults are typical starting points.

CriterionWeightBuildBuyAdapt
Fits our process exactly
Cost in year one
Speed to first use
Control over the future
Maintenance burden

Grid C2 · Publishing

Crossing the border to the stores

Publishing an app is a checkpoint process: accounts, listings, privacy declarations, review, release. We prepare every document the reviewers will ask for and walk you through the identity checks for your own developer accounts.

Publishing support in detail

  1. PapersDeveloper accounts in your organisation's name.
  2. ManifestListing text, screenshots and privacy forms matched to the real app.
  3. InspectionReviewer notes and a working demo account.
  4. CrossingStaged release where available, watched closely.

Grid D1 · Standards

Rules of the road

The commitments that hold on every route we travel with a client.

01Show the mapWritten options and reasoning before any significant commitment, with the trade-offs stated.
02Short legsWork in increments of one to two weeks, each ending in something you can open and try.
03Your vehicleCode, accounts and documentation belong to you from the first day.
04Everyone can travelDesign and testing towards WCAG 2.2 AA, with any gaps reported openly.
05Light luggageCollect only the data a product needs; describe it honestly.

All standards

Compass 03 · Discovery planner

How long should the survey take?

Estimate the size of a discovery phase before any build begins. Each square is one working day: orange for research, aqua for prototyping and testing.

Grid D2 · Field guides

Field guides for the undecided

Guide 1

Build, buy or adapt?

A plain method for comparing the three roads, with the questions that usually decide it.

Read the guide

Guide 2

Reading a discovery report

What a good one contains and the warning signs of a weak one.

Read the guide

Guide 3

Signs of a lost project

Seven symptoms that a software project has drifted off its route, and how to reorient.

Read the guide

Grid E1 · Base camp

Support from base camp

Clients with a support agreement log issues through the support page, which gives each request a reference. We respond during working hours, Monday to Friday, 09:00 to 18:00 UK time, according to the priorities agreed in writing.

Open a support request

Grid E2 · Set out

Tell us where you are

You do not need a specification. A paragraph about the decision in front of you is enough to start. We reply by email with questions or a suggested first conversation.