Get in touch

Home/Projects/B2B mobile app

Case study · In development

A B2B mobile applicationfor medical laboratories

Tody customers order quality controls and reagents from a site with more than 15,000 active products. We are building an Android and iOS app for customers and for the Tody team that receives exactly the prices and rules of the site, with no second logic to maintain.

0.3–1 sproduct catalogue responsetest environment · 7 Nov 2026
0.2 slist of modules visible in the customer areatest environment
9 + 4screens designed for customers and for administrationanalysis on real data
~50 typesof customers, with pricing rules taken from the site6 currencies
The situation

A good site, but no API

The Tody B2B platform sells to laboratories, hospitals and distributors in Romania and abroad, with about 50 customer types, bonuses, advance payments and 6 currencies. The site worked only with a session and a browser cookie: there was no interface through which a mobile app could request data.

An app that calculated prices on its own would have meant a second logic to maintain, which would have produced different figures at the first change on the site.

What we are doing

An API in the same app

  • The JSON API runs inside the same web application and calls the same components as the order page: prices, bonuses and rules identical to the site.
  • The API components are kept separate, so a deployment does not restart the application.
  • In the test environment, access to the API goes through an HTTPS proxy that lets through only the app's requests.
  • Production has not been touched: everything done so far runs in the test environment.
App screens

What the app will do

Screens designed on the platform's real data: products, modules, customers by language, currencies, order and payment types.

For customers · 9 screens

  • home and search, with barcode or QR scanning
  • product list and product page with grouped variants
  • cart and checkout on a single screen
  • orders and invoices
  • EQAS reports and account

For the Tody team · 4 screens

  • dashboard with the day's status
  • new orders, with a phone notification
  • customer search
  • alerts
Status

What's done and what's next

Analysisreal data and architecture · done
Screens9 for customers, 4 for admin · done
First APIconnection, modules, catalogue · in test
Account and cartlogin, customer price, checkout · next
The appconnecting the app to the API · next

Short product titles

Long names written for search engines become a short title with code and attributes (range, number of samples), suited to a phone screen.

Grouped variants

In test, a search by analysis code returns 12 products, grouped under the same code, one for each monthly round.

Planned

  • token and biometric sign-in
  • catalogue stored on the phone, updated incrementally
  • push notifications
  • card payment through the site's payment page
Claude's role

What Claude did on the project

We work as on the Tody platform: one ticket, one conversation, everything in the test environment.

What Claude did

  • analysis of the platform's real data and the architecture
  • design of the screens and the API
  • the code of the first API components and their tests
  • the documentation and the list of next steps

What we did

  • chose the technology: React Native, Android and iOS
  • provided access to the test environment
  • verified the results
  • keep the relationship with the client

Nothing reaches production without a test, rollback steps and a person's confirmation. How we work with Claude →

Have an ordering site and want a mobile app?

Tell us what platform it runs on. We start from the existing logic instead of rewriting it.

Request an assessment →