Aotomatic
A shrimp farm diary where one day's entry went from 24 screens to 7.
Aotomatic is Forte Biotech's app for shrimp farmers to log each pond, every day. The first version, built by another team, asked one question per screen. The client hired ARIS, the agency I work at, to redo it. As the only UX/UI designer, I grouped the questions into five forms, then designed the add-ons that followed in 2024 and 2026, including an AI chat.
Live on the App Store and Google PlayThe screens are the real designs. The first version was built by another team, and its screens are labelled that way. Screens tagged Rebuilt are chat states put together for this case from parts of the real design. Place names, the address and personal details are removed or blurred, and two typos in the web admin are fixed. The demo readings were adjusted to realistic values, and antibiotics in the demo data were replaced with Vitamin C and a probiotic.
- How did I help
- Design & system work
- AgriTech · Aquaculture
- Role
- Sole UX/UI designer
- Team
- 2023: 2 mobile, 2 web, 2 QC
- Timeline
- 2023, ~3 months · add-ons in 2024 and 2026
- Platform
- Mobile app + web admin
- Forte Biotech's app for shrimp farmers to log each pond, every day.
- As the only UX/UI designer on the agency side, I grouped one-question screens into five forms: one day's entry went from 24 screens to 7.
- I also designed the 2024 and 2026 add-ons, including an AI chat. Live on the App Store and Google Play.
The tour: Group the questions by the job → An AI chat → Put the five forms in front of farmers earlier

One question per screen.
The app was already in production when ARIS took it over. Logging one pond for one day took 24 screens: the pond page, a menu, four section title screens, 17 questions and a closing screen.

Where a day's entry lost time.
- 01One reading per screenWater quality alone asked 13 readings on 13 screens, plus a title screen.
- 02A calendar, not the dayThe pond page opened on a calendar. What had been logged that day wasn't on it.
- 03Tests kept apartTest results sat in a separate Testing area on the farm page, outside the daily entry.
Group the questions by the job.
I was the only UX/UI designer on the ARIS side, working with 2 mobile devs, 2 web devs and 2 QC.
- 01Audit the first versionWent through every screen of the live app and listed each question it asked and where it led.
- 02Group them into formsPut the questions into the five forms a farmer fills in at the pond: nutrition, water quality, feeding tray (vó), medicine and RAPID test results.
- 03Check with engineeringChecked low-fidelity flows with the mobile and web devs for feasibility before handoff.
Before and after.

Water quality in one form
One water quality form with every reading in one scroll, and Next pinned at the bottom.
Inside the 2023 app.

Log one pond for one day
From the pond page: Add an entry, five forms in a row, then a confirm screen. Seven screens in all, against 24 in the first version.
The client's teal and font.
The system around them is mine.
Forte Biotech brought the colour tone and the SFU Futura typeface. I built the colour and text styles, the type scale, the shadows and the components on top. For this case they are recreated in Figma as variables.

Revenue and profit.
Entries you can edit.
A short add-on: the pond page shows each entry time as a column you can edit, and revenue and profit each got a form.

An AI chat.
Photos and RAPID PLUS too.
Add-ons the client asked for, shipped in 2026, inside the same design system.

A tab for the AI chat
An AI tab between Statistics and Profile.
The store pictures.
Mine too.
I designed the App Store preview images.

When something goes wrong.

When the connection drops
If the connection drops, the chat says so where the answer would appear, with a Retry button under the message.
Put the five forms in front of farmers earlier.
The forms held up in walkthroughs with QC and engineering. Next time I would test them with farmers at the pond before handoff.
- Count the screensCounting the screens for one real day's entry showed where the time went, before any visual change.
- Add-ons on the same systemThe 2024 and 2026 add-ons used the 2023 tokens and components, so the app still looks like one product.
- Check the brand colour earlyWhite text on the brand teal is about 3:1, under the 4.5:1 that small text needs. Next time I'd add a darker teal for buttons and text.
Regroup the flow around the real task.
For products where people push through too many steps. I audit the flow and regroup it around the job they came to do.
Similar work: UX audit, quoted after a short call















