Quick answer
We write a fixed price and a timeline into the contract because the two technologies we work with make the work estimable before it starts. Flutter builds the iPhone and Android app from one codebase, so you pay SAR 3,999 for an app on the Apple and Google stores with a timeline that starts from 14 days depending on scope. Next.js builds a fast website that search engines read well, so you pay SAR 599 for the basic website, delivered within 48 hours of content and brand approval. The fixed price is not generosity; it is the result of repeatable work with the same tools.
One app for iPhone and Android from one codebase, and what it means for price and changes
Before Flutter, a mobile app was two projects: an iPhone developer writing Swift and an Android developer writing Kotlin, with every feature written twice, tested twice and fixed twice. Any quote in that world estimated two jobs, not one, which is why prices were open-ended and timelines elastic. Flutter, a framework from Google, writes the interface and logic once in Dart and produces two apps from the same source. For you as a buyer this means four things:
- The price is estimated once. The number of screens and features is the same on both platforms, so the estimate rests on one scope written in the contract. That is why we can publish SAR 3,999 for the app package on our website rather than in a special offer.
- A change is written once and appears on both. Changing a colour, adding a field or adjusting a checkout step does not pass through two developers, so changes after launch cost less and arrive faster.
- Testing happens once. We test the logic once and the display on two devices, rather than repeating the whole cycle.
- The timeline can be written down. When the work repeats with the same tools, the timeline becomes recorded experience rather than a guess, which is why the contract says "starts from 14 days depending on scope" and we hold to it.
Our apps built this way are live on the App Store and can be tried from our portfolio page, and Flutter is compared with the alternatives in Flutter versus React Native versus native.
Next.js, speed and visibility in search
A website built on a generic builder or template carries everything it does not need, arrives heavy on the visitor's phone, and is hard for a search engine to read because the content is assembled in the browser after loading. Next.js, a framework built on React, generates pages on the server or ahead of time at build, so the visitor receives a complete page ready to display and the search engine finds the text, headings and links on its first read with no waiting.
The owner notices the result in three places: speed on mobile, where the page appears before the visitor thinks about going back, which affects both retention and how Google rates the page; readability for search engines, since every page has its title, description and visible text in the source, which is what engines need to understand it (we promise nobody a particular ranking, but we give the engine something to read); and a fixed cost, because the basic website's pages are known (home, services, about, contact, policies) and share one structure, so the price is SAR 599 and the timeline is 48 hours from content and brand approval rather than "depends on the design".
When the website needs an admin panel, a payment gateway or user accounts, we build them in the same framework with React; details are under web development.
What the client owns at handover
A fixed price without clear ownership is half a deal. This is what is handed over in your name at the end of the project:
| Item | In whose name | Note |
|---|---|---|
| Source code (Flutter and Next.js) | The client | A complete repository you can hand to any other developer |
| Apple Developer account | The client | USD 99 per year paid to Apple; the app is published under your business name |
| Google Play account | The client | USD 25 one time, paid to Google |
| Domain | The client | Registered in your name, first year included in the price |
| Server, hosting and database | The client | First year included, with the security certificate and OTP messages |
| Payment gateway accounts | The client | mada, Visa, Mastercard and Apple Pay, plus Tabby and Tamara instalments, linked to your business bank account |
After the first year, renewal is your choice at 20% of the contract value per year with no automatic renewal; it covers operation and support under the contract and does not include new features or a new design. If you choose not to renew, the code and accounts are yours and you continue with whoever you like. All packages and prices are on pricing.
The limits of each technology and when we advise against them
A fixed price is possible because we work inside limits we know. Outside them, we tell you the tool is not the right one:
- Heavy games with 3D graphics and complex physics. Flutter draws excellent interfaces but is not a game engine; dedicated engines such as Unity fit better.
- On-device video and audio processing, such as a video editor or live camera filters. That needs intensive native code per platform, and its price cannot be fixed before analysis.
- Deep system integration, such as home-screen widgets or a watch app. Possible with Flutter but with native parts added, which moves it out of the package into a custom project.
- A single page that never changes. Next.js works, but you may not need a framework at all, and we will say so.
- An editorial site publishing dozens of articles a day with a content team. That needs a content management system connected to the site, a wider scope than the basic package.
In these cases we price after a free analysis session and write the value and duration into the contract, or tell you plainly that another provider suits you better.
How to read any company's technical quote
Whether you sign with us or someone else, five questions separate a good quote from the rest. What is the technology, by name? "Responsive app" or "latest technologies" is not an answer. Is the price fixed or an estimate, and if fixed, exactly what scope does it cover and what sits outside it? From which moment does the timeline start, signing or content approval? An honest quote says, because most delay comes from content rather than code. In whose name are the accounts and the code? If the quote does not say so in writing, assume the answer is "the developer's". And what happens in year two: how much is renewal, is it automatic, and what does it cover? The app package and its stages are described under app development.
