← Selected projects

Commerce & Services

Grobax.

Commerce & supply-chain ecosystem

Four Flutter applications serve consumers, internal teams, partners, and warehouses, sharing core and UI packages across ordering, field operations, inventory, and distribution.

Implementation scope
Mobile ecosystem & API integration
Platform scope
Android / iOS
  • Flutter
  • Melos
  • GetX
  • Dio
  • Firebase
Explore the approach
Grobax project presentation with application screens
Grobax project presentation with application screens

The context

A workflow worth connecting.

Consumers, field teams, partners, and warehouse staff have different workflows within the same trading and supply-chain ecosystem. A shared foundation keeps those applications consistent while each product stays focused on its users.

What the project covers

  • Grobax: catalog, checkout, addresses, and order tracking
  • G-Office: sales, market surveys, processing, and logistics
  • G-Partner: business activities, land, vendors, and payment information
  • G-Warehouse: inbound/outbound, picking, stock movement, and quality checks

Four applications · shared core + shared UI

  1. 01Grobax · consumer
  2. 02G-Office · internal
  3. 03G-Partner · partner
  4. 04G-Warehouse · warehouse

Each application uses shared packages and connects to backend services.

Inside the implementation

Engineering decisions.

01

Share foundations across four apps

A Melos monorepo manages four applications and two shared packages. Shared core covers networking, storage, models, and utilities; shared UI provides reusable components and assets.

02

Organize around business features

GetX controllers, screens, and widgets follow feature boundaries. Repositories connect those flows to REST APIs through Dio.

03

Support separate delivery environments

Staging and production flavors separate configuration. Distribution scripts support Android testing through Firebase App Distribution and iOS testing through TestFlight.

Scope & validation

The documented scope is the mobile ecosystem and API integration. Distribution scripts do not establish public store availability, backend authorship, or measured business results.

Platform targets or native project configuration documented in the source; store availability is not asserted.

Explore another approach.

On-demand transportCREB Plantation operations & payrollSistem Kebun

Have something in mind?

Let’s build something
that works together.

Tell me about your product, the people using it,
and the problem you want to solve.

Discuss a project