MS WebX is an IT company. We build websites and web platforms, native mobile apps for iOS and Android, and we integrate AI into them — together with the SEO work that makes what we build findable. We also run our own products on the same platform we build for clients, which means the foundation is proven in production before anyone else depends on it.
You describe the goal, not the technical solution. We ask questions until the scope is actually clear, then put it in writing before anything is built. If we think what you asked for is the wrong way to reach your goal, we say so before you pay for it — that conversation is cheaper than the rebuild it prevents.
Do the website and the mobile app share the same backend?
Yes, and more strictly than that phrase usually means. The API is defined once in PHP, and both the TypeScript client for the web and the Dart client for the app are generated from that definition. Neither is written by hand — the linter rejects a hand-written API type. So the app cannot quietly drift out of sync with the server: a mismatch breaks the build instead of breaking production.
Is the 18-language support real, or machine translation on top?
Real. Every page exists as its own row per language, with its own text and its own URL — this FAQ lives at /frequently-asked-questions in English and at /de/haeufig-gestellte-fragen in German, not behind a translation parameter. That means each language can be written the way people in that market actually search, and it can be corrected in one language without touching the other seventeen.