Mobile apps for iOS and Android
Native-quality apps on both platforms, from user experience and accounts to App Store and Google Play release.
Services · Mobile & Web App
App development for iOS, Android and the web
We design and build apps for businesses, schools and organisations in Thailand — from the problem worth solving to the day real users arrive — with the same team that builds and runs AIVEQ and TUXA on the App Store and Google Play.
- iOS and Android
- Web apps and back office
- Start in 2 weeks
- Support after launch
Real screens from TUXA, an app our team builds and runs
What we build
Apps designed around the work users actually do
We don't start from a feature list. We start by asking who will use it, what for, and what outcome it should change — then decide what to build, and what not to.
Web apps and back office
Browser-based systems that work on desktop, tablet and phone, with admin screens, user roles and a database.
Learning and assessment systems
Online learning, question banks, assessment and adaptive practice — our strongest area, because we have built it for ourselves.
Dashboards and reporting
Reports for teachers, leaders, parents and teams that answer real questions, not just look good.
Proof you can check
Our own apps, available to download today
Before building apps for anyone else, we built and ran our own apps with real users. Download them and try them — both are published under the developer name IQX COMPANY LIMITED.
AIVEQ
LIVEAI-powered maths and science practice for Thai grades 4–7 that adjusts to each learner, with a view for parents.
See the product
TUXA
LIVEAn exam-prep navigator for Thai grade-7 entrance exams that reads how a child answers, then plans practice around where points are really lost.
See the product
Before you hire
How to choose an app development company: 6 questions to ask before you hire
If you are deciding who should build your app, these are the questions we would ask any company — including us. Clear answers tell you more than the lowest price.
Do they have their own apps that you can download today?
A team that has run an app with real users knows what breaks after launch, not just how to build. Ask for the links and try them yourself.
Will they talk to real users before quoting?
A quote built only from a feature list usually misses the work users do every day, which then returns as change requests.
At AI.ac.thOur first step is talking to the people who will use the system, not only the people commissioning it — and we don't take work where we may not.
Will they tell you what not to build?
A team that accepts every feature request inflates the budget, stretches the timeline and makes the app harder to use.
At AI.ac.thEvery brief we deliver includes a list of what we recommend not building, with the reasons.
Can you try the real thing during the project?
What users say when they see the real thing is always different from what they say about a picture. The later you see it, the more a change costs.
At AI.ac.thWe ship in rounds you can try before it is finished, and change it based on what real users tell us.
Who looks after the app after launch, and how?
Launch day is when real problems start to appear. A team that disappears after handover leaves the burden with you.
At AI.ac.thWe follow real usage in the first weeks, fix what gets in the way, hand over an administrator guide and propose the next round from usage data.
If you stop working with them, can another team continue?
If the documents and plans only work with one team, you cannot change teams even when you are unhappy.
At AI.ac.thDocuments from the Discovery Sprint are written so another team can build from them. No lock-in.
Work we don't take on
- Work that only wants someone to type code to a finished spec, with no questions allowed
- Work where we may not speak to a single real user
- Work that measures success by features delivered instead of what changes for users
Not because we are picky — we do this kind of work badly, and other teams do it better.
Want all six answers for your project?
Tell us the problem you are facing and we will answer these questions for your project directly. No spec needed.
How we work
From an unclear brief to an app people actually use
Our work runs in four steps, each with a clear deliverable, so you always know where the project stands and what you already have.
Understand the problem
We talk to the people who will actually use the system, not just the people commissioning it, map the current process end to end, and separate the real problem from its symptoms.
What you getA brief covering the problem, the users, the outcomes that must change — and a list of what we recommend not building.
Design the system
We design the data structure, access rights and key screens, starting from the tasks users do most often — not the prettiest screen.
What you getA clickable prototype, the data structure, and a development plan split into rounds.
Build and test
We ship in rounds you can try before it is finished, because what users say when they see the real thing is always different from what they say about a picture.
What you getA system tested with real users, with test documentation and a log of what was fixed.
Launch and improve
Launch day is not the end. We follow real usage in the first weeks, fix what gets in the way, and decide what to build next from what the data shows.
What you getA live system, an administrator guide, and a proposal for the next round based on usage data.
Start small
Discovery Sprint · 2 weeks
Step one of every app project, available on its own.
Not ready to commit to the whole project? Start with step one alone. At the end you will know what to build, what it should cost and how long it will take.
Talk about a Discovery SprintWhat happens in the two weeks
- Interviews with real users
- A map of how the work is done today
- Requirements ranked by what must come first
- A prototype of the key screens
- A budget and timeline estimate
- A straight answer on what not to build
- Delivered as documents any team can build from — no lock-in to us
FAQ
Frequently asked questions
What people ask before hiring an app developer
Where should I hire an app developer in Thailand?
Choose a team that can answer the six questions before you hire clearly: do they have their own apps you can download, will they talk to real users before quoting, will they tell you what not to build, can you try the real thing in rounds, who looks after the app after launch, and can another team take the work over. If you want to start with us, a 2-week Discovery Sprint gives you a prototype, a budget estimate and a plan before you commit to the whole project.
How is AI.ac.th different from a typical app development company?
We are a Thai team that builds and runs its own apps — AIVEQ and TUXA, both on the App Store and Google Play. The same team builds systems for schools, businesses and organisations and teaches AI-assisted development through AI Academy, so we design for the day real users arrive, not just for handover day.
How much does it cost to build an app?
It depends on scope, the number of users and the systems it must connect to. If you are not sure how big your project is, start with a 2-week Discovery Sprint: you finish with a budget and timeline estimate you can rely on before committing to the whole project. For typical market ranges in Thailand, see our guide to app development costs (in Thai).
How long does it take to build an app?
That also depends on scope. What we can say for certain is that the first step takes two weeks (the Discovery Sprint), and it produces a development plan in rounds with a timeline for the whole project. During development you try the work in rounds instead of waiting for the end.
Can you build for both iOS and Android?
Yes. Our own apps, AIVEQ and TUXA, are available on both the App Store and Google Play. If your project suits a web app better, we will say so — not every project needs to be a mobile app.
I don't have a requirements document. Can we still start?
Yes, and that is how we prefer to start. Tell us the problem you are facing; our first step is to talk to the people who will use the system and write the brief for you.
Can I do the Discovery Sprint and then not continue with you?
Yes. The documents are written so another team can build from them. There is no lock-in.
Do you support the app after launch?
Yes. Launch day is not the end: we follow real usage in the first weeks, fix what gets in the way, hand over an administrator guide and propose the next round based on usage data.
Do you build apps for schools and education?
Yes, and it is what we know best, because our own products are learning systems: online learning, question banks, assessment, adaptive practice and reporting for teachers, school leaders and parents.
What work do you not take on?
Work that only wants code typed to a finished spec with no questions allowed, work where we may not speak to a single real user, and work that measures success by features delivered rather than what changes for users. Not because we are picky — we do this kind of work badly, and other teams do it better.
Our services
Related services
Tell us about your project
No spec needed. Tell us the problem you are facing and we will help you see where to start — or whether you need to build anything new at all.