Drinkit · Android

Android Engineering

Roadmap and a live look at the dodobrands/drinkit-mobile-android codebase

Updated 2026-09-17

Roadmap

Backlog2
In Progress6
Done3
Loading…

Tools

  • Scoutcode-metrics analysis

Team

Media

Weekly releases

A release every week instead of every two. The pipeline is not the bottleneck — confidence is: a weekly train only works when regression is automated end to end.

Design System: components

A component library shared with design: a live catalogue of components in the app, and process guides for working with the design system. Tracked by the two theme-vs-hardcoded shares.

Design System: palette rebuild

Progress: 10%

The colour palette refactored together with design, and the new dark theme built on it.

AI Tooling

Progress: 60%

Deliver faster without lowering quality: agent code review, shared rules and skills for the coding agents, project documentation the agents can read, and a way for them to navigate a large codebase without drowning in it.

Navigation 3

Progress: 5%

Screens inside a feature navigate with Navigation 3, and each feature owns its navigation instead of sharing app-wide graphs. Tracked by Navigation 2 vs Navigation 3.

Monitoring

Progress: 70%

Crashes and freezes reported with alerts and a response policy, performance traces collected and kept, and one health dashboard over all of it. The research phase is done.

Offline mode

Progress: 70%

Without internet the customer can do everything except pay. First slice: the main screen — promo and menu open from what the app already has, so it starts without waiting on the network.

KMP in the app

Progress: 5%

Write shared code once instead of twice. Neither app is ready to move even its data and domain layers: platform-specific dependencies are woven through them. First step is an inventory of those dependencies and a roadmap to a state where data and domain can move.

Screenshot testing

Every UI preview doubles as a screenshot test, so a visual regression is caught in the PR that causes it; over a thousand screens and components are covered. Tracked by Screenshot tests.

Release automation

Release branches are cut on schedule, builds are published to Google Play and AppGallery without manual steps, and the team is reminded when a release is due.

Swagger contract codegen

Network contracts are generated from the backend’s API specs instead of being written by hand and drifting away from the backend.