Ardian SinuratCivil Engineer & Automation Developer
CV
Case study 08 / 10ProductPrototype

Geous

Offline field map for Android. Survey, plantation and supervision crews work where there is no signal, and still need to see where they are on the project map, drop points and record tracks.

At a glance

3stages working on device
~2,500lines of Dart
0static analysis issues
Period
May – June 2026
Role
Product owner; learning Flutter; tests every stage on a real phone
Status
Prototype
Links
Not public
Geous offline map layersMap layers drawn on the phone without signal: CARTO basemap tiles, a georeferenced geo-PDF map, live GPS position, and waypoints and tracks stored in SQLite.Waypoints and tracksstored in SQLite (sqflite)Live GPS positiongeolocatorGeo-PDF project mapgeoreferenced, works offlineBasemap tilesCARTO via flutter_mapNo signal neededfor position, mapor recordingIn the field
Swipe sideways to see the whole diagram. Layers drawn on the phone without signal: basemap, geo-PDF project map, live position, waypoints and tracks.

01Problem

Survey, plantation and supervision crews work where there is no signal, and still need to see where they are on the project map, drop points and record tracks.

02What I built

An offline-first field map in the spirit of Avenza Maps: basemap, live GPS position, waypoints stored in SQLite, georeferenced geo-PDF maps that work offline, and track recording.

03How it works

  1. Map stack. Flutter with flutter_map; CARTO basemap tiles (OpenStreetMap's own tile servers block app use).
  2. Small, confirmed stages. Sync, accounts and a backend are deliberately gated until prospective users have been interviewed.

04Results and scale

  • Stages 1–3 work on device; about 2,500 lines of Dart; static analysis clean.
  • Next: distance and area measurement, GPX/KML export, and 5–10 user interviews.

05Stack

  • Flutter
  • Dart
  • flutter_map
  • geolocator
  • SQLite (sqflite)
  • Android
Next case studyATLASRunning many AI coding sessions without collisions