DevFIRE WEB
ENFRDEROHULB
Start a project

Services · for clients

We build yours like it's ours.

Web apps, mobile apps, AI features and design systems, made by the studio that runs four products of its own. Same team, same process, same standards. You see every screen before we write the code.

Start a project How we work together

What we build

Five ways to work with us

Each one comes with what you get, the stack we would reach for, and where we have already done it in our own products.

Web apps

Storefronts, dashboards, booking engines and SaaS products that load fast, rank well and speak your customers' language.

Typical stack

Next.jsTypeScriptTailwindPostgresSupabaseStripeVercel

What you get

  • Clickable mocks of every screen, approved before code
  • SEO built in: metadata, structured data, sitemaps, Core Web Vitals in the green
  • Multilingual routes and copy files, ready for translators
  • An admin for your team, with roles, if you need one
  • A preview link for every change, EU hosting at launch

Done in our own product

Portiaportia.ro · portia.lu

One Next.js app serves every merchant storefront, and refreshes a page the moment a merchant edits the menu.

View Portia

Mobile apps

iPhone and Android apps from one codebase, designed for one hand and a weak signal, and shipped through the stores for you.

Typical stack

FlutterRiverpodReact NativeSupabaseRevenueCatFirebase

What you get

  • One Flutter codebase for iPhone and Android
  • Offline-first where it matters, synced when the signal returns
  • Sign in with Apple and Google, push, in-app purchases
  • TestFlight builds you can try on your own phone every week
  • Store listings, screenshots and review handled

Done in our own product

Nomentousnomentous.app

Logging a rejection never waits for the network: hold to talk, let go, done in under ten seconds. A local queue syncs later.

View Nomentous

AI features

Vision, voice and generation that do one job well inside your product. Not a chatbot bolted onto the corner of the screen.

Typical stack

Google GeminiVertex AI EUFunction callingEdge Functionszod

What you get

  • A use case with a number on it: minutes saved, steps removed
  • Server-side calls in EU regions, model keys never in the app
  • Guardrails: structured output, validation, limits on what the model may do
  • A human check before anything in your data changes
  • A cost and speed budget per call, measured

Done in our own product

BeaconStepbeaconstep.app

Gemini drafts a full city quest in seconds, using only real places from OpenStreetMap. Every photo step is checked on the server, so nobody can fake it.

View BeaconStep

Design systems

One source of truth for colour, type and spacing that your web app and your mobile app both read. Change it once, it changes everywhere.

Typical stack

Design tokensTailwindFlutter themesHTML mocksWCAG AA

What you get

  • Tokens in one JSON file, generated into CSS, Tailwind and Flutter
  • Components with every state drawn: hover, focus, error, empty
  • Contrast checked automatically in light and dark
  • Logo and brand basics if you start from zero
  • A living reference page your team actually opens

Done in our own product

KachFitkachfit.app

The web app and the iPhone app share one token file and one four-language dictionary, with WCAG AA checks in both themes on every build.

View KachFit

Frontend lead

Frontend architecture and a senior lead for your existing team: structure you can grow into, reviews that teach, and a frontend that stops slowing your roadmap down.

Typical stack

ReactAngularNext.jsTypeScriptSanityStencilJS

What you get

  • An architecture review with a written report and a plan
  • Multi-tenant and config-driven UI engines that onboard clients in hours
  • A hands-on lead inside your team, part-time or for a phase
  • Code reviews, hiring help and onboarding docs
  • Performance and accessibility audits with fixes, not just findings

Done for clients in Luxembourg

Otto Kartye12+ yrs · fintech + telecom

Led frontend teams of up to 15 engineers on a KYC/AML platform, and built a multi-tenant engine that cut client onboarding from weeks to hours. Plus client apps under NDA that we can't name here.

Read Otto's story

Working together

Three ways to start

Pick the one that fits where you are. You can move from one to the next without starting over.

Best for new products

Fixed first phase

Scope, design and a working first version, with a fixed scope and a fixed price agreed in writing before we start.

  • Written scope after one call
  • Logo, tokens and clickable mocks
  • A working build on a preview link
  • Code and accounts in your name

Ends with a decision, not a dependency

Best for products in motion

Ongoing build

Reserved days every month to keep shipping: new features, store updates, monitoring and fixes, with a shared board you can read any time.

  • Monthly plan, adjustable
  • Weekly preview builds
  • Hosting, uptime and store releases
  • One short written update a week

Usually follows a first phase

Best for teams

Consulting days

Book days for an architecture review, an audit, or a senior lead working inside your team, on site in Luxembourg or remote.

  • Single days or a block
  • Written findings you keep
  • Works with your tools and rituals
  • English, French or German in the room

Luxembourg, Greater Region, remote

Prices come after the first call, in writing, for your scope. No surprises later.

How we work

You see it before we build it

  1. Talk

    One call about what you want to build, for whom, and what success looks like. You get a written scope and a fixed first phase.

  2. Design first

    Tokens, logo and clickable HTML mocks of every screen. You approve them before a line of product code is written.

  3. Build in the open

    Short cycles with a live preview link. You watch the real thing grow, not a status report.

  4. Launch + run

    Store listings, SEO, monitoring and EU hosting. We stay on after launch, the way we run our own products.

Questions

Asked before you ask

Something else on your mind? Write to us, Otto answers within two working days.

What does a project cost?

It depends on what you want to build, so we do not publish a price list. After one call you get a written scope with a fixed price for the first phase. Ongoing work and consulting days are priced the same way: in writing, before anything starts.

How long until we can launch?

A first phase usually runs a few weeks, not months. The written scope names the date, and the preview link shows you every week whether we are on track.

Who owns the code and the accounts?

You do. The repository, the hosting, the app store accounts and the domain live in your name from day one. If we ever part ways, you keep everything and it still runs.

Can you join our existing team and codebase?

Yes. That is what consulting days are for: a review of what you have, a plan, and a senior lead who works inside your team and your tools, in React, Angular or Next.js.

Where is our data hosted?

In the EU. Databases run in Frankfurt with row-level security on every table, and AI calls go to EU regions from the server, never from the phone. GDPR is part of the design, not a checkbox at the end.

Which languages do you work in?

Meetings in English, French, German, Romanian or Hungarian, and some Luxembourgish. Products ship multilingual from day one, with every string in one dictionary your translators can edit.

Start a project

Got an idea? Let's build it.

Tell us what you want to make and who it is for. Otto reads every message personally.

Write to us contact@devfireweb.eu