MN
Back to selected work

Floranow 2.0: from a redesign request to a platform

Reframed a marketplace redesign into a full B2B customer platform, and delivered it across web, iOS and Android.

The brief

Redesign the marketplace with a new interface, faster search and a few features.

The reframe

I proposed a customer platform instead, where buyers manage their business with Floranow: dashboard, orders, invoices, balance and finances, RFQ, marketplace and settings. I won CTO and stakeholder buy in for the new direction.

What I did

Led the design with the CTO and stakeholders. Architected and built the web platform in our monorepo. Authored the service contracts the backend built the microservices to, including a CMS and an offer supply management service.

Built the internal admin platform frontend: buyer management, segmentation, price groups, sales channels, delivery points, feature flags and CMS. Built the mobile app end to end in React Native.

The result

Launched October 2026. Customers fully migrated onto the new platform, zero failed transactions since launch. Delivered across three surfaces on one shared architecture. Lighthouse accessibility 96, best practices 96 and SEO 100. Bilingual with RTL Arabic.

Platform and security

Web, iOS and Android live in one monorepo (Turborepo, pnpm) with shared UI and domain packages. Four decisions shape how the platform stays secure and maintainable.

Single sign on and role based access control

Keycloak for single sign on over OAuth 2.0 and OpenID Connect, with role based access control.

Why:
Buyers, internal teams and suppliers use different apps: the customer platform, the admin portal and vendor portal features. One identity provider keeps sign in and permissions in one place instead of in each app.
Trade off:
Keycloak is one more service to configure, run and keep patched, and roles have to be designed before features are built on them.
Result:
One sign in standard across web, iOS and Android, with access granted by role rather than by app.

Contract driven integration

I wrote the service contracts first. The backend team implemented them as Java Spring Boot microservices, and the web and mobile apps use OpenAPI generated types.

Why:
Frontend and backend can build in parallel against an agreed contract, and a breaking API change shows up as a type error at build time, not as a bug in production.
Trade off:
Contracts take time to agree before code is written, and every API change goes through the contract.
Result:
Web and mobile share the same generated types from the shared packages in the monorepo.

Invoice payments through Telr

Online invoice payment through the Telr gateway, on web and on mobile.

Why:
Buyers settle invoices inside the platform instead of offline. One gateway for both surfaces keeps the payment flow in one place.
Trade off:
The platform depends on one provider for availability and for the payment methods it supports.
Result:
Zero failed transactions since launch.

CI quality gates

Tests, type checks and linting run on every pull request.

Why:
A change to a shared package can break web, iOS and Android at once. The gates catch that before merge.
Trade off:
Every pull request waits for the checks, and today the pipeline validates every app on every change.
Result:
Nothing merges into the shared codebase without passing tests, type checks and linting.

Architecture view

Business domain: a cross border B2B floral business serving the GCC, where buyers run their business with Floranow. Data domain: service contracts authored for the backend to build microservices to, including a CMS and an offer supply management service. Application domain: dashboard, orders, invoices, balance and finances, RFQ, marketplace and settings, plus an internal admin platform. Technology domain: one monorepo carrying web, iOS and Android, with the mobile app in React Native.

As Is: a marketplace to be redesigned. To Be: a customer platform across three surfaces on one shared architecture. Governance: contracts the backend builds to, feature flags, and a bilingual interface with RTL Arabic.

What I would do differently

The CI validates every app on every change. It should move to affected only builds.