Make the call first, then write the code
Plenty of companies ask for “an app” when what they need is a fast website customers can install on their phone. We help you decide on concrete criteria (app stores, push notifications, offline use, device hardware) before you invest. We haven’t published a native app store case yet; we do have installable web apps in production.
These are the missteps we see most when someone shows up with the decision already made:
Building an app for a service people use twice a year: few install it, and those who do delete it.
Forgetting that an app store listing doesn’t rank on Google. If customers search for you there, you still need a website.
Budgeting for development only, and not for developer accounts, store review or keeping up with every new iOS and Android release.
Building two separate apps, one for iPhone and one for Android, when a cross-platform codebase or an installable web app would have done the job.
Asking for push notifications without knowing what you’ll send or how often.
It isn’t on the App Store or Google Play. It’s a website that installs to the home screen and can send push notifications, and for many businesses that’s all they need.
Medellín, ColombiaTravel
A tour operator in Medellín and the Antioquia region. Travelers browse tours and news on their phones, in English or Spanish, often while already on the road.
What we did
We made it installable as a web app: a manifest with adaptive icons, full-screen launch, a service worker and push notifications for new articles. It also has an AI travel assistant that hands the conversation off to WhatsApp.
Technology
Footer credit: “Diseño Web con ❤ por User Media”.
Sometimes you do. These are the signals we look for.
Four ways onto your customer’s phone, with very different costs and limits.
General comparison as of October 2026. Browser capabilities change with every iOS and Android release, so we re-check them when scoping your project.
These answers pick the technology. Without them, any recommendation is a guess.
A customer who opens it once to get a quote is a different problem from a driver who opens it fifty times a day.
Camera, location, Bluetooth, NFC or background work. Each one changes what a web app can and can’t do.
Whether showing the last loaded data is enough, or whether users must capture data offline for hours and sync it later.
Alerts with a clear reason: a new article, a status change, a reminder. Pointless notifications are how apps get uninstalled.
Sign-in, permissions and where personal data is stored, plus the privacy policy both app stores require.
New iOS and Android versions ship every year. We agree up front on who updates, tests and publishes.
We talk to the people who’d use it and map their tasks on the phone, step by step.
With those tasks in hand we weigh web, PWA, cross-platform and native, and recommend one, with our reasons.
Where possible we start with an installable web app: it ships sooner, updates without store review and shows whether people actually come back.
If usage shows you need a store app, we plan that step with what we learned, without rebuilding the backend.
Real reviews our clients left on Google.
Viviana Hidalgo Alvarado
October 2026
Dayanna david tapias
October 2026
Daniel Gómez
October 2026
Andrés Felipe Pájaro Martinez
October 2026
Sergio Andres Pájaro Martinez
October 2026
Johnattan Rodriguez
December 2025
Evelintoya1011 Montoya
December 2025
Diana C
November 2025
Rafael Castaño
November 2025
IVAN BLANCO
November 2025
Juan Jose Cano Giraldo
November 2025
Litografia Azabache
April 2024
Tomás Vélez
February 2024
Adriana Hernandez
February 2024
If customers search, compare and decide in one visit, a fast website does more: it ranks on Google and doesn’t ask anyone to install anything. An app pays off when people use it often or it needs phone features browsers don’t offer. Often the right order is website first and app later, if the numbers call for it.
A PWA is your website, installable and able to send notifications: one codebase, no app stores and instant updates. Flutter builds real iOS and Android apps from one codebase, with broader access to the phone, but every release goes through store review. If your use case fits within what browsers allow, a PWA is usually cheaper to keep running.
We haven’t published a native app store case yet, and we’d rather say so up front. If your project needs one, we walk you through what it takes: developer accounts in your company’s name (Apple charges an annual fee, Google a one-time fee), a privacy policy, review of every release and testing on real devices.
They work, with caveats. Since iOS 16.4, a web app added to the home screen can receive push notifications, but Safari restricts Bluetooth, NFC and background work more than Android does. If most of your audience is on iPhone, we test on those devices before deciding.
Yes. We’re in Colombia, on UTC−5 all year, which lines up with Eastern time in the winter and Central time in the summer. Planning calls happen over video, and you can test builds on your own phone as they’re ready.
The admin panel, database and integrations your app needs behind the scenes.
The foundation of our installable web apps: fast, bilingual and easy to edit.
Chat assistants and automatic alerts that work just as well on a phone.
For teams that will build and maintain their own app.
Tell us who would use it, how often and what it needs from the phone. We’ll tell you which option makes sense, what it takes to maintain and where to start.
Sketches, a reference app or usage data from your current site all help us decide faster.
We use cookies
We use cookies and similar technologies to improve your experience, personalize content, and analyze our traffic. By clicking 'Accept all', you consent to the use of all cookies.
