logo
ROSTerm company logo

ROSTerm for installers

Screens of the ROSTerm mobile app
Overview
About the project
ROSTerm manufactures engineering plumbing — pipes, fittings, valves and radiators. Nobody buys it off a shelf: installers, plumbers and site foremen pick it for a specific job. We are building them a mobile catalogue app: the specialist finds the item, assembles the list of materials for the project and sends the request straight to the manufacturer, past every other point of sale. There is no payment in the app — from there a manager takes the request over.
Task
Give professionals a tool that works on site, and route requests to the manufacturer itself. The manager needs a panel for running the catalogue, handling requests and awarding loyalty points.
Solution
A cross-platform Flutter app for iOS and Android, a Go backend with a single API, and a separate React admin panel.
Problems we ran into
  1. The user is on a building site — in gloves, often one-handed, on a bad connection. This is not another online shop: it needs large buttons, the fewest possible steps, a high-contrast interface and a cache that survives losing the network.
  2. The client keeps the catalogue in Excel. Typing hundreds of items into the admin panel by hand costs far more effort than it is worth.
  3. Standard online-shop mechanics do not fit: instead of an order there is a request, with its own lifecycle and its own owner on the client's side.
  4. Requirements arrived in iterations. The loyalty programme was rewritten several times over the project.
Project stages
Requirements as a product of their own
Two original specifications — the client's and our team's — were consolidated into a single requirements document. From there the project runs off its specs: the PRD, the feature registry, the feature specs, the architecture decisions and the development log live in their own repository and count as the single source of truth. The team checks against them before building anything, and the client sees the status of every feature on a dedicated Project Status page.
Design

A light interface with the brand's red accent: white background, large type, and red kept for actions, prices and statuses. The screens are laid out for one-handed use — search in the header, large category tiles, and an "Add to cart" button right in the product list.

ROSTerm app screen
ROSTerm app screen
Development
Flutter, Go and React
The mobile app is Flutter — one codebase for iOS and Android. The backend was rewritten in Go: standard net/http, PostgreSQL through pgx with raw SQL and no ORM, JWT with refresh tokens. The contract is fixed in OpenAPI, so client and server are built from one specification. The admin panel is a separate React application with TypeScript and Ant Design. There are no HTML forms on the backend: everything is managed from the panel, against the same API the mobile app uses.
Across those stages we built an app that covers:
Signing in by phone call

Nobody on a building site is going to recall a password, so signing in goes by phone number confirmed with a call through a telephony provider. Registration finishes with the profile: name, city and consents.

ROSTerm app screen
ROSTerm app screen
Home screen and catalogue

The home screen carries a carousel of promotions and new arrivals, a card for the active request with its status, and category tiles. In the catalogue, alongside the category tree, sit project collections — ready-made material lists for a typical job, put together by a manager.

ROSTerm app screen
ROSTerm app screen
Search, filters and the product card

Search works on both name and article number, from the first character typed, with filters by category and price and a sort order. The product card holds a gallery with video, the description, a specifications table, PDF datasheets and the points the purchase will earn.

ROSTerm app screen
ROSTerm app screen
Cart, and a request instead of a payment

The cart lives on the device and survives an app restart. At checkout the user picks one of two — the discount for their tier or spending points; the two are never combined. What comes out is not a paid order but a request, which a manager picks up.

ROSTerm app screen
ROSTerm app screen
Requests and their statuses

A list of requests filtered by status, and a detail screen: line items, quantities, total, the discount applied, the planned shipment date and a button to contact the manager. The manager changes the status in the admin panel and the user gets a push.

ROSTerm app screen
ROSTerm app screen
Profile and loyalty programme

Three tiers — Novice, Master and Titan — each with its own discount and its own points cashback rate. Points become spendable 48 hours after a purchase, no more than half of a request can be covered with them, and registering earns a welcome balance.

ROSTerm app screen
ROSTerm app screen
In the admin panel we made room for
  • Running the catalogue: categories, products, specifications, photos, documents and video
  • Bulk-uploading products from XLSX, with configurable column mapping and an error report
  • Handling requests and changing their statuses
  • Running the loyalty programme: tiers, manual awarding and deduction of points
  • Managing users, administrators and the audit log

The panel is an application of its own rather than forms on the backend: it works against the same API as the mobile app and deploys independently of it.

Testing and acceptance
Every feature comes with a test spec: the scenarios and the expected result are written next to the requirement, and a coverage registry shows what has been checked. The client runs acceptance against that same registry rather than against a verbal agreement.
Where the project stands
The work runs in iterations and is still going. Already working: the catalogue with search and filters, project collections, the cart and requests, sign-in by call, push notifications, and the admin panel with catalogue import from Excel. In progress: calling the manager from inside the app, and integrating the catalogue with the client's inventory system.
Results
Result
The client is getting a mobile app for iOS and Android, a backend and an admin panel that close the whole path — from picking materials on site to a request that reaches the manufacturer directly, with nobody in between. The project is in active development: the team works in iterations, and the client watches progress per feature group on the Project Status page, which is generated from the same requirements registry the team builds against. Technologies: Flutter (iOS and Android), Go and PostgreSQL on the backend, React with TypeScript in the admin panel, RabbitMQ and a dedicated worker for push notifications, and OpenAPI as the API contract.