SQL and database design
Almost every app eventually becomes a question about data. We design schemas and queries that stay fast as the product grows, on the server and on the phone.
SELECT 'Hello, Paris';How we use SQL
On the backend we work mainly with PostgreSQL, designing tables, indexes and migrations together with the API rather than as an afterthought. We read query plans before adding hardware, and we keep migrations reversible. On mobile devices SQLite does the heavy lifting behind Room on Android and Core Data or GRDB on iOS, storing things like scan history so an app stays useful without a connection. We also write the reporting queries that turn raw app events into numbers a product owner can act on.
What we build with SQL
- PostgreSQL schema design and migrations
- Query optimisation using execution plans
- SQLite storage on Android and iOS
- Reporting queries for product decisions
- Backup and restore procedures
Questions about SQL
Do we need a server database for our app?
Only if data must be shared between users or devices. Many utility apps keep everything on the phone with SQLite.
Our queries are getting slow. Can you help?
Yes. We start by measuring the slowest queries, then fix indexes and query shapes before discussing infrastructure.
Discuss a SQL project
We reply from [email protected]. Send any documents to that address after your first message.