The difference from Moldova is that in Romania an app for the general public can make sense. The market is large enough.
Which does not mean it does. The question is not whether users exist, but why someone would install your app instead of opening the site.
If the answer is "to look at the products", the answer is that they will not.
Real reasons people install an app
It gets used often. Delivery, transport, banking, loyalty. Something returned to weekly, not twice a year.
It has something the web does badly. Notifications that arrive, payment in one gesture, offline working, scanning.
It replaces a card or a document. Loyalty, subscription, ticket. The classic reason to install and the most durable.
It is a work tool. Couriers, reps, technicians, drivers. Here user numbers do not matter at all — what matters is the time saved per person.
What is specific to the Romanian market
Real competition. In almost any category there is already a well-known app. That changes the strategy: you win on one specific function done well, not on "the same but ours".
Payments and subscriptions. The ecosystem is more mature, with more processing options and recurring subscriptions as normal practice.
Store rules applied strictly. Apple and Google policies on digital payments, permissions and data apply as everywhere, but with more scrutiny on apps that carry transactions.
Higher quality expectations. Users compare against apps built by large teams. A slow or unstable app gets one star and does not recover.
What we build
A native or cross-platform app, depending on the purpose. A link to your systems — orders, stock, invoicing. Notifications, payments, offline working where needed. Store publication under your company's accounts, not ours.
What stays yours at the end is described here.
The cost nobody quotes
Building an app is a one-off expense. Keeping it alive is not.
Apple and Google change the rules every year: minimum SDK versions, new privacy requirements, forms declaring what data is collected. An app left untouched for two years reaches a point where it can no longer be updated, and sometimes gets pulled from the store.
A realistic budget includes one revision a year, even if you add no features. Whoever leaves it out of the quote will ask for it anyway, later.
Questions
An app or a website optimised for phones?
If the user returns weekly and needs notifications or fast payment, an app. If they come a few times a year for information, a website. Most projects are the second case.
Native or cross-platform?
Cross-platform for most business apps, native when graphics performance or heavy hardware access matters. The decision comes from the requirements, not from preference.
Who owns the store accounts?
Your company. Developer accounts are opened in your name from the start; otherwise the app is not yours, whoever wrote the code.
How long until it is in the store?
Development depends on scope. Publication takes days for Google Play and is unpredictable for the App Store, especially on a first version.