Frequently asked questions
What people want to know before contacting us.
We have gathered the questions we receive most often about app development, system development, price, process and what sets a good development partner apart from a poor one. No hype, just honest answers.
App development.
Questions about mobile app projects, cost, technology, the App Store and maintenance.
How much does it cost to build an app?
The price varies with complexity. Simple internal tools are less expensive, while apps with integrations (BankID, ID-porten, ERP), offline mode and dashboards cost more. Complex apps with real-time features, push notifications and complicated role and access models are at the higher end. We give a fixed price after a scoping phase where we define requirements together, so you know the final sum before we start.
How long does it take to develop an app?
The timeline varies with scope, from scoping and design, through development, to testing, approval and publishing on the App Store and Google Play. We deliver in sprints so you see progress throughout and can adjust priorities as you go.
Should I build a native app or a PWA?
If you need native hardware integration (advanced camera, BankID app, NFC, background updates) or App Store visibility, build native. If you need to distribute internally within a company without App Store friction, want to update frequently, or have a limited budget, a PWA is often the right choice and delivers much of the native experience at lower cost. We discuss this at the first meeting based on what the app needs to deliver.
Do you build in React Native or native Swift/Kotlin?
We use React Native with Expo for most apps we deliver. It gives a native feel, shares code between iOS and Android, and reduces both development time and maintenance cost. For apps that require heavy 3D graphics, specialist hardware or deep OS integration, we build native in Swift or Kotlin. We have experience with both.
Do you handle App Store and Google Play publishing?
Yes. We set up Apple Developer Program and Google Play Console if you do not have them, manage certificates and provisioning, submit for review, respond to questions from Apple and Google, and keep the app updated when policies change. You always retain ownership of the accounts.
System development.
Custom internal systems, professional tools, CRM/ERP and integrations.
What is the difference between a standard CRM and a custom system?
A standard CRM covers generic processes quickly and at low cost, but you have to adapt your business to the tool. A custom system follows YOUR process, integrates seamlessly with your existing systems, and can automate unique workflows. It pays off when you have many users, a workflow that standard tools do not match, or integration requirements that become complicated in SaaS solutions.
Can you integrate with the specialist systems we already have?
Yes. We have experience with integrations against existing specialist systems, ERP and CRM, as well as public services such as Altinn, ID-porten and BankID. If you use a particular system, talk to us and we will assess what is possible and how best to connect.
How long does it take to build an internal system?
The timeline depends on scope. An MVP of a specialist system with a defined set of features, role-based access and a few integrations goes faster than a full case management system for a large organisation. We deliver in sprints so parts go live along the way, you do not have to wait until everything is complete before you see the first benefit.
What about security, GDPR and privacy?
Privacy and security are built in from the start. We encrypt data at rest and in transit, maintain audit logs on sensitive data, and tailor the security level to the needs of each individual project. Hosting is on Norwegian or EU/EEA-based infrastructure. We take security seriously and test critical systems before going to production.
What happens if STUDIO X no longer exists in five years?
You own all source code, all databases and all infrastructure from day one. We build with open, well-documented technologies (TypeScript, Postgres, Next.js, React) so any competent developer can take over. We write onboarding documentation and maintain an SLA for knowledge transfer. You are never locked in.
Price, process and contracts.
How we work commercially: fixed price, scoping, maintenance and payment models.
Do you offer fixed prices?
Yes. We believe fixed pricing is the only honest answer when the client needs predictability. We first go through a scoping phase where we define the requirements, identify risk areas and agree on what is in and out of scope. After that we give a fixed price for the development. Changes during the project are handled as clearly defined change orders, no surprises.
What is the difference between a fixed price and an hourly rate?
A fixed price gives you predictability: you know the final sum before we start. An hourly rate gives maximum flexibility but can escalate. We recommend fixed pricing for defined deliverables (MVP, new app, system) and an hourly rate for ongoing further development and operations after launch. Most of our clients start on a fixed price and move to a monthly maintenance agreement once the product is in use.
Do you require long-term binding contracts?
No. Standard maintenance and further development agreements have three months' notice. We want you to stay because we deliver value, not because a contract holds you back.
What is a scoping phase and why do I need one?
A scoping phase is paid work where we map users and processes, create wireframes and prototypes, identify integrations, assess risk and set a realistic scope. The result is a fixed price you can trust, a clear scope document, and a design prototype you can show internally. The scoping phase is the best insurance against projects that go off the rails.
How do you handle changes during a project?
Changes happen in every project. We handle them by logging all requests, assessing them against the existing scope, and delivering a short written change order with price and timeline before we do the work. You stay in control, nothing is done without your approval, and you are never surprised by an invoice.
AI, LLMs and automation.
Claude, GPT, RAG, chatbots, automation, and what works for B2B.
What is the difference between a chatbot and a RAG solution?
A simple chatbot answers based on the general knowledge in the model, and often hallucinates about internal matters. A RAG solution (Retrieval-Augmented Generation) fetches relevant documents from YOUR knowledge base before answering, so the responses are grounded in your internal data. For B2B use we almost always recommend RAG. It gives control, traceability and dramatically lower risk of incorrect information.
Can we use our internal documents in an LLM without giving them to OpenAI?
Yes. The major providers offer enterprise agreements where data is not used for training and is stored in the EU. Alternatively we can run open-source models on Norwegian or EU/EEA-based infrastructure where no data leaves the region. We design the architecture based on the sensitivity level of your data.
Which AI model do you recommend: Claude, GPT or something else?
For Norwegian B2B use we recommend Claude (Anthropic) for complex reasoning, long documents and quality on Norwegian text. GPT (OpenAI) for high volume and a broad developer ecosystem. Gemini for Google stack integration. Mistral or Llama if you need to run locally. We choose based on the nature of the task, not hype, and we design so the model can be swapped out later.
How much do we save by automating with AI?
It depends entirely on the task. For tasks such as report generation, supplier checks and parts of case processing, AI assistance can cut time spent significantly. As a rule of thumb: if a task involves reading and synthesising text, a good portion of the work can be automated with the right setup. We assess the concrete potential together with you.
Choosing a development partner.
What you should look for when choosing someone to build for you.
Why choose STUDIO X over a large consultancy?
At STUDIO X the team that delivers the project works with you from the first meeting. You get no junior developers who were not at the sales meeting. We have lower overhead than the large firms and we give fixed prices with genuine accountability. If you need a large consultancy apparatus all at once, choose a large firm. If you want a small team of experienced people who take real ownership of your product, we are the right choice.
What questions should I ask a development partner before signing?
Ask: Who specifically works on the project and what is their background? Who owns the source code and the accounts? What happens if we want to end the engagement? How do you handle scope changes? Which three reference clients can I call? What does a realistic project estimate look like, can I see an example? Answers that are vague or unclear are red flags.
What should I have ready before contacting you?
You do NOT need a requirements specification. You need: a short description of the problem you want to solve (one to two sentences), who the target audience is, an approximate timeframe and a rough budget range. That is enough. We work out the rest together in the scoping phase.
How many developers work on a typical project?
An MVP team is typically small: a designer, a couple of developers and a project owner. Larger projects are staffed with more developers and an architect. We keep teams small because coordination costs otherwise become too high. If a project needs more, we split it into several parallel teams with clear interfaces.
Are you office-based or do you work remotely?
Hybrid. We have offices in Sarpsborg and Oslo where the team meets several days a week. We are happy to travel to clients for kick-off and workshops, but ongoing collaboration happens via Slack/Teams and video. We have experience working with clients across Norway and Europe.
Question not answered?
Send us a short description of what you would like to know. We reply personally, within a short time.