Projects 07 / 11
Ateri
Offline-first management of rural technical visits
A platform for field technicians who support family agro-industries. Producer records, visits with a traceable history, photos and documents. Works with no signal and syncs later, resolving conflicts field by field.
Overview
Ateri organizes the work of rural extension technicians who support family agro-industries in western Paraná. Every producer has a record, every visit has a traceable history, and the dashboard shows the monthly quota — one visit per producer —, what is overdue and what is coming up next.
The field app is offline-first: it stores everything on the device, works with no signal on the farm and syncs when the connection returns, resolving conflicts field by field. The C# and .NET 10 API is the shared contract for the React Native app and the React web panel, and the project was also a way to study the stack the market asks for.
Features
What the system does
-
Monthly quota dashboard
How many producers have been served, completed, overdue and next-week visits, who still needs a visit and progress per route block.
-
Visit schedule
Visits by day with pending, completed, rescheduled, canceled or overdue status, and filters by block, city and "only mine".
-
Producer record
Details, coordinates, CAF with expiry warning, responsible team, pinned notes and the full visit history.
-
Route blocks
Cities grouped into blocks to plan field trips and track coverage of each region.
-
Files and expense entries
Photos, documents and audio per producer, uploaded only on Wi-Fi, plus mileage and visit expenses.
-
Works without a server
A local mode lets the app be used in the field before a server exists, keeping the operation queue to take everything to the API later, without losing anything.
Screens
Inside the system
Screens show fictional data generated for demonstration.
Stack
How it was built
- Frontend
- ReactTypeScriptTanStack QueryTanStack TableZustandTailwind 4shadcn/ui
- Mobile
- React NativeExpoExpo RouterSQLiteNativeWind
- Backend
- C#.NET 10ASP.NET Core Minimal APIsEF Core 10DapperIdentity + JWTOpenAPI
- Data
- PostgreSQL
- Infra & DevOps
- DockerxUnitTestcontainersVitestPlaywright
Behind the scenes
Technical challenges
-
One sync route
The device sends its operation queue and receives, in the same response, what changed on the server since the last cursor. With weak signal every round trip saved counts, and the app already gets the merged state of what it just sent.
-
Idempotent operations with device ids
Every operation has a GUID v7 generated on the phone and the time it happened. Resending the same queue duplicates nothing, and entities created offline are born with their final id.
-
Never losing work in a conflict
Last write wins field by field, with a history per record. If an operation is rejected (a duplicate tax ID, for example), the following ones for the same producer are deferred instead of discarded, waiting for the fix.
-
One contract for two clients
The OpenAPI document generated by the API is the source of types for web and app. Web and mobile have their own interfaces, but speak exactly the same language with the server.
Need something
like this?
Tell me the idea or the problem. I help shape the solution and build it from the API to the app.
Let's talk