← All projects
Co-developed projectWebsite (new tab)Business portal (new tab)

Lobapp

A delivery platform for customers, couriers and restaurants.

Identified technologies
GoFlutter / DartNext.js / TypeScript

My contribution

Developed with Ana Luísa Pacífico. Lobapp is the current technical project name. The final product will use a different name.

People and partnership

Development and partnership.

Developed with Ana Luísa Pacífico. Lobapp is the current technical project name. The final product will use a different name.

Credits provided by Breno Mayder · 2026-11-01

Architecture overview

Central Go API with PostgreSQL/Redis, three Flutter apps and three Next.js surfaces. Shared contracts and identity connect seven channels with separate access roles.

Technical structure

Technology by module.

Central Go API with PostgreSQL/Redis, three Flutter apps and three Next.js surfaces. Shared contracts and identity connect seven channels with separate access roles.

What each part does and which technologies support it. A module in the code does not mean all its features are complete or published.

01 / Existing code

API

GoPostgreSQLRedisOpenAPI

Shared business core.

Authentication, catalog, orders and integrations are organized in a central API with channel contracts.

02 / Existing code

Customer app

FlutterDart

Customer experience.

Discovery, purchase and order tracking channel in development.

03 / Existing code

Courier app

FlutterDart

Courier experience.

Separate mobile channel for delivery work and tracking.

04 / Existing code

Restaurant app

FlutterDart

Restaurant mobile operations.

An app with restaurant-specific context and permissions.

05 / Existing code

Platform administration

Next.jsReactTypeScript

Platform administration.

Separate UI for internal operations and management.

06 / Existing code

Restaurant portal

Next.jsReactTypeScript

Restaurant portal.

Restaurant management website, separate from the admin.

07 / Existing code

Website and shared resources

Next.jsTypeScriptOpenAPIDesign tokens

Website, contracts and identity.

Public website and shared types, contracts and brand tokens.

How the parts connect

Apps and websites use a central API. Shared contracts keep channels consistent.

Data and integrations

The architecture includes PostgreSQL, Redis and S3-compatible storage. Payments, maps and notifications have separate gates.

Quality and operations

Separate Go, Flutter and web checks, versioned SQL, contracts and per-channel review. No commercial release is claimed.

Code and repositories

Repository · access required (new tab)

Skills in this project

Languages and backend ↗Web, mobile and experience ↗Databases and integration ↗Cloud and infrastructure ↗DevOps and delivery ↗Architecture, quality and AI ↗
Let’s build something

Do you have a similar challenge?

Tell me what you need. The WhatsApp draft includes this project as a reference. You can edit it before sending.

Talk on WhatsApp ↗
/→

Keep exploring

Contact

Good work starts with a conversation.

Let’s talk