Web & mobile apps
Web and mobile apps, delivered in weeks
Veraplot designs and develops web and mobile applications with Next.js and React Native (Expo), backed by Python or TypeScript APIs on AWS. One senior team builds the web app, the iOS and Android apps and the serverless backend, with Cognito authentication, DynamoDB or PostgreSQL, and CI/CD from the first sprint. Projects are delivered at a fixed price, hosted in your AWS account, and the code is yours.
One team, every screen
Web, iOS and Android share TypeScript, components and business logic, so a feature ships on every platform together instead of three times.
Production from sprint one
Authentication, environments, CI/CD and monitoring come first, so every demo runs on real infrastructure rather than a throwaway prototype.
No hosting surprises
Serverless backends and Amplify hosting scale with usage: a quiet internal tool costs little, a busy customer app grows without a rewrite.
What you get
Product scope and key flows
User journeys, key screens and acceptance criteria agreed up front, so the fixed price covers a product everyone has already seen.
Web application
A Next.js app with server rendering, SEO, accessibility and analytics, hosted on AWS Amplify with a preview environment per branch.
iOS and Android apps
An Expo app with push notifications, offline handling and over-the-air updates, published to both stores under your own developer accounts.
Backend and API
FastAPI or TypeScript services on Lambda and API Gateway, with Cognito sign-in, roles and a DynamoDB or PostgreSQL data model.
CI/CD and handover
Automated tests and deployments, infrastructure as code, a store release process and documentation your developers can pick up.
The stack
Picked for your context, not for a partner badge. Open formats first, managed AWS services where they pay for themselves.
What users touch
Web and native, one language
- Next.js
- React
- Expo
- React Native
- TypeScript
- Tailwind CSS
What does the work
APIs that scale down to zero
- Python
- FastAPI
- Node.js
- AWS Lambda
- Amazon API Gateway
Who's who
Sign-in, roles and single sign-on
- Amazon Cognito
- Sign in with Apple
- Google Sign-In
- SAML
- OpenID Connect
What's remembered
A data model sized for the use
- Amazon DynamoDB
- PostgreSQL
- Amazon Aurora
- Amazon S3
How it ships
Every commit deployable, every release traceable
- AWS Amplify
- EAS Build
- EAS Submit
- GitLab CI/CD
- GitHub Actions
- AWS CDK
Typical use cases
Web and mobile product on one backend
A Next.js web app and an Expo app for iOS and Android sharing a single serverless AWS backend, with hosting and deployments on Amplify.
Operations back-office
A role-based admin console for operations teams, replacing spreadsheets and email chains with tracked workflows and a full audit trail.
Customer or partner portal
A secure portal where clients or distributors sign in to follow orders, documents and statuses, fed by existing ERP and data platform APIs.
Field app that works offline
A mobile app for teams on the move, capturing forms and photos without coverage and syncing automatically once the connection returns.
From first call to production
- 01
Discovery call
We map your systems, constraints and the outcome that matters. You talk to the engineer who will build it, not an account manager.
- 02
Fixed-price scope
A written scope with deliverables, milestones and one price, agreed before any code is written. No day-rate meter running in the background.
- 03
Build in short iterations
Working increments every one to two weeks, demoed on your data in your AWS account. Course corrections happen early, not at the end.
- 04
Handover and optional run
Code, infrastructure as code, runbooks and a walkthrough with your team. Run it yourselves, or keep us on support month-to-month or on a 1–3 year plan.
Questions buyers ask
How much does it cost to build a web or mobile app?
A fixed price, set once screens, user roles and integrations are scoped. You know the total before development starts, and our pricing typically sits 30–50% below equivalent ESN rates. Building web and mobile on one TypeScript stack with a shared backend also means you do not pay for the same feature twice.
How long until the app is in users' hands?
A focused first release, web or mobile, typically ships in six to sixteen weeks, with Apple and Google store reviews planned into the schedule. After that, we release in short cycles, and Expo over-the-air updates let many fixes reach users without waiting for a new store submission.
Why React Native with Expo rather than fully native apps?
One codebase for iOS and Android, sharing TypeScript with the web app, means faster delivery and a single team to maintain everything. Expo handles builds, store submission and over-the-air updates. For apps that need heavy 3D or unusual hardware access, fully native can be the better call, and we will say so during scoping.
Who owns the code and the store accounts?
You do. The repositories, the AWS account, the Apple and Google developer accounts and the domain are in your name from day one. We work inside them with the access you grant, so there is nothing to transfer at the end and no lock-in to negotiate your way out of.
Can the app use data from our ERP or data platform?
Yes, and that is often the point. We expose the data through secured APIs on top of your existing systems or lakehouse, with caching where it matters, so the app shows live orders, stock or documents without giving users direct access to back-end systems.