Skip to content
← Back to home
ESENCambiar a español

UTEC · Mobile Applications Workshop

FarmaYopin

Mobile app for a pharmacy chain to manage its products, with a Flutter app and a Spring Boot REST API.

Role
Full-stack development (team workshop)
Year
2026
Stack
FlutterDartSpring BootMySQLSQLiteDockerJWT

The problem

Mobile Applications workshop: the brief was a custom app for FarmaYopin pharmacies to manage their products, with two roles (admin and customer) on a distributed architecture. An architecture report came first, then a complete solution connected to a real backend, with no mocked data.

What I built

  • Flutter app for Android and iOS with sign-up, login and different screens per role.
  • For the admin: create, edit and list products with price, detail, photo and stock, plus the purchase history of each product.
  • For the customer: catalog, editable cart, cart checkout and their own purchase history.
  • Spring Boot REST API with JWT authentication and MySQL started with Docker Compose.
  • Local SQLite cache to read purchase history offline, and pull-to-refresh to sync again.

Technical decisions

A real backend from the start

Instead of mocking the app with test data, we connected the catalog and purchases to the API as soon as it was available. Contract mismatches between app and backend showed up early, not on delivery day.

SQLite on the client for the history

Pharmacies don't always have good signal. Storing purchase history on the device makes it readable offline, and a manual refresh updates it when the network returns.

Roles enforced on the backend

The app hides what a role can't do, but the real rule lives in Spring Security: a customer can't call the admin endpoints even by tampering with the app.

What I took away

  • Building a mobile app end to end: state, navigation, local persistence and consuming an API.
  • Designing a REST contract that two different kinds of users share without stepping on each other.
  • That starting everything with Docker Compose speeds things up a lot when several people depend on the same backend.