Field work cannot depend on chat
In Medellín a delivery, a route or a client visit happens far from the office computer. If the order lives on WhatsApp, the driver has no clear order and the branch does not know what was delivered. People call to ask what the system should show. A phone’s battery is enough for a simple app; it is not enough to rebuild the day from a message thread once there are ten stops.
Commissioning a native app in one language and a panel in another leaves two contracts and two databases that do not match. The product price changes at the office and the phone still shows the old one. For an SME that is expensive and it shows at the customer’s door. An Android app in Medellín has to read the same truth as the panel, not a copy pasted in the morning.
.NET MAUI against the same backend
The app is built with .NET MAUI and the server with ASP.NET Core. The field team sees what is theirs: the next stop, the order or the catalog item. The office sees the state when it changes. No second language and no second vendor for the phone. If the panel does not exist yet, you can start with the minimum flow — a €500 MVP — and grow. If the panel is already there, the app sits on it.
The scope says which screens go in the pocket and which stay on the web. We do not put full accounting on the phone. We deliver the app, the package to install it on the devices you define and the code in your name when payments are complete. Thirty days cover defects in that deliverable. Monthly support, €150 with no lock-in, is there if you want Android or flow changes not to freeze after delivery.
What you receive
- A list of app screens and of what stays in the office.
- An Android app in .NET MAUI for the agreed flow.
- A connection to the ASP.NET Core backend, new or existing.
- Source code in your name and thirty days of fixes.
Installation is tested on a real phone, not only the emulator, with an order or route walkthrough. If the app store is in scope, it is written down; if not, the app is installed on the business devices. We do not promise a Play Store release when it is not in the milestone.
Reference price
There is no single “app” tariff because it depends on whether the backend already exists. An MVP of the main flow starts at €500 and is credited if you continue. An office web application, if it also has to be built, starts at €4,500. The Android app is quoted as a milestone on that base, with a written scope. Support is €150 a month, with no lock-in. Reference amounts are in euros, on the pricing page.
An orders app case
The portfolio includes an Android orders app, built with .NET MAUI, so the order does not stay in chat. We do not put a client name on it because that sheet is a type of system, not an authorized brand. If your operation in Medellín looks similar — delivery, order taking, a catalog on the street — we start from that pattern and fit it to your states.
Questions about Android apps
Does the app work offline?
Only if the scope asks for it. By default the app talks to the ASP.NET Core server when there is data. An offline mode is quoted separately, because it changes how conflicts are resolved when the connection returns.
Does it also work on iPhone?
This page is about Android with .NET MAUI. Another platform is discussed if you truly need it; it is not included in the same milestone.
Can it show the catalog and take the order?
Yes, if those screens are in the scope. Price and stock come from the same backend the office uses, so the phone does not show an old figure copied by hand.
How do I start?
Write through the form or krats.tech@gmail.com. If you prefer WhatsApp, say so in the message. Tell us who carries the phone in Medellín and what the first screen must show.
I want the operation on the phone
Tell us the route, the order or the catalog that today is handled in chat. We see whether you already have a .NET panel or should start with an MVP. Contact form, or WhatsApp if you ask for it in the text.