Skip to content
Plazoleta

Your customers need you on their phone, not in a browser.

Mobile Apps

This is the area where you don't have to take our word for it: you can download what we make. Jornia and LoverCast are our own products, in production, on Google Play. Nobody commissioned them and nobody reviews them: whether they're well or badly built is on us.

That includes the boring parts, which are the expensive ones: working without a connection, syncing between phone and TV without the user thinking about it, taking payments, and holding one codebase together across two very different screens.

What you get

  • Native when it matters, cross-platform when it suits

    We have no religion here. Native if the product lives off deep system integration; cross-platform if what matters is reaching two stores with a small team. The decision gets argued, not inherited.

  • Release and lifecycle

    Shipping to the store is the beginning. Reviews, minimum versions, OS migrations and the maintenance nobody puts in the budget.

  • Offline and sync, properly

    Working in airplane mode isn't a checkbox: it shapes the entire architecture. You decide it at the start or you pay dearly for it later.

Don't take our word for it

Our own product, in production. Download it and judge for yourself.

LoverCast

lovercast.app

IPTV player and organiser for Android and Android TV.

  • · One codebase for phone and Android TV, with two ways of being used
  • · Real-time sync across devices: start on your phone, carry on watching on the TV
  • · Metadata enrichment from external sources, plus offline downloads
  • · Payments and multi-device licensing with Stripe

A native Android trip planner.

  • · Native Android with Material You, not a cross-platform port
  • · Offline-first architecture: the whole itinerary lives on the device
  • · Home screen widgets

When we're not for you

  • If your product is used in a browser and you want an app «because you have to have an app». That's usually money thrown away.

  • If you need native iOS and Android, simultaneously and yesterday. With a small team that means picking one first.

  • If you expect to publish and forget. The stores force you to maintain, and that cost is real.

If you recognise yourself here, tell us anyway. I'd rather point you somewhere else in an email than have us both find out halfway through the project.

Questions

Native or cross-platform?
It depends on how much your product leans on the system —widgets, TV, notifications, graphics performance— and on how many people will maintain it. It's a business decision, not a matter of technical taste, and we argue it with your case in front of us.
Can I see something you've built?
Yes, and it's our favourite thing about this area: Jornia and LoverCast are published. Download them and judge for yourself.