TrueLogic.cloud

Apps and websites people can actually use

Native iOS and Android, cross-platform Flutter and React Native, and the web builds that sit behind them. Designed mobile-first, tested on real devices, and handed over with the code and the store accounts in your name.

Mobile app development

From a first MVP to an app already in the stores

We start from what the app has to do and who has to use it, then pick the platform strategy that gets there for the least money. Sometimes that is one cross-platform codebase, sometimes it genuinely is two native builds.

Native iOS development

Swift and SwiftUI apps built against current Apple guidelines, using the platform properly: widgets, notifications, background tasks, biometrics and offline behaviour that survives a lift with no signal.

Native Android development

Kotlin and Jetpack Compose, tested across the screen sizes and OS versions your users actually run rather than the newest flagship on a desk.

Cross-platform builds

Flutter, React Native and Kotlin Multiplatform where one codebase serves both stores. Native modules written when the framework runs out of road, so you're never stuck.

MVP for startups

The smallest version that can prove the idea with real users, scoped to a fixed price and built so the second version is not a rewrite.

Mobile UI and UX design

Wireframes and prototypes in Figma, tested on a phone in a hand before anything is engineered. Platform conventions respected rather than a web layout squeezed onto a small screen.

Backend, APIs and integrations

The half of an app nobody sees: authentication, APIs, an admin panel, push notifications, payments and subscriptions, on Firebase, Supabase or infrastructure we run for you.

Web development

From a five-page site to a full application

Marketing websites

The site most businesses actually need: clear structure, quick loading, strong search foundations and a contact path that works. Built to be edited without calling a developer.

WordPress development

Custom themes and blocks rather than a bloated bought template. Fast, secure, and set up so your team can publish without breaking the layout.

E-commerce

WooCommerce or Shopify builds with payments, shipping, tax and inventory configured properly, and a checkout that doesn't lose people on step three.

Custom web applications

Portals, dashboards, booking systems and internal tools. Built on a stack your future developers will recognise, with the deployment pipeline included.

Speed and Core Web Vitals

Diagnosis and repair for slow sites. Images, fonts, render-blocking scripts, caching and hosting, measured before and after so the improvement is provable.

Maintenance and support

Updates, backups, security patching, uptime monitoring and a monthly allowance of small changes, so the site doesn't quietly rot.

Mobile and web stack we build on

SwiftSwiftUIKotlinJetpack ComposeFlutterReact NativeKotlin MultiplatformReactNext.jsNode.jsLaravelWordPressFirebaseSupabasePostgreSQLGraphQLStripeRevenueCatFigmaTestFlightFastlaneCrashlyticsSentryApp Store ConnectGoogle Play Console

The first real decision

Native or cross-platform? It depends on what the app does

One Flutter or React Native codebase covers both stores and usually costs meaningfully less than two native builds, because the work is done once. For most business apps, content apps, booking tools and internal systems, that's the right answer and the saving is real.

Native earns its extra cost when the app leans hard on the device: heavy camera or sensor work, on-device machine learning, complex background processing, tight platform integrations, or animation that has to be flawless. Games are their own conversation.

We'll tell you which side of that line you fall on during scoping, and we have no incentive to push you either way. The quote is fixed before the work starts.

What we look at before recommending

  • How much the app depends on device hardware
  • Whether both platforms need to launch at once
  • How often you plan to ship updates
  • Who will maintain the code in two years
  • Whether an existing web app can be reused
  • What performance actually has to feel like

The process

How an app project runs

Discovery and scoping

A workshop covering what the app must do, who uses it, which platforms matter and what the first release genuinely needs to contain. Everything else goes on a later list rather than into the quote.

Feature list · platform recommendation · fixed quote · timeline

Design and prototype

Wireframes then a clickable prototype you can hold on a phone. Changing a screen here costs minutes, and changing it after engineering costs days.

Wireframes · Figma prototype · design system

Build in visible increments

Engineering runs in short cycles with a testable build in your hands throughout, over TestFlight for iOS and internal testing tracks for Android.

Fortnightly builds · TestFlight and Play testing access · full commit history

Test on real devices

Functional, performance and edge-case testing on a range of real phones and OS versions, including the poor connectivity and low battery cases that break apps in the field.

Device test matrix · crash reporting configured · fixes verified

Submit, launch and support

Store listings, screenshots, privacy declarations and review preparation, then monitoring, OS updates and iteration once real users arrive.

Live on both stores · store listing assets · monitoring · support plan

Standard on every build

The things that should never be an optional extra

Plenty of quotes look cheap because performance, accessibility and search foundations have been left out and will be sold to you later.

We include them, because retrofitting any of the three costs more than doing it once at the start.

In every website and app we deliver

  • Mobile-first layout tested on real devices
  • Semantic HTML, meta tags, Open Graph and JSON-LD schema
  • Sitemap, robots.txt and clean canonical URLs
  • Core Web Vitals in the green at launch
  • Accessible contrast, focus states and keyboard navigation
  • Crash reporting and analytics wired up before release
  • Store accounts and repositories in your name
  • Source code and documentation handed over

Web & mobile FAQ

Questions worth asking any development agency

How much does it cost to build a mobile app?

It depends on how many platforms you need, how much of the work is design rather than engineering, whether there's a backend and admin panel behind it, and how many third-party services have to be integrated. We quote a fixed price after a scoping conversation, and that price is what you pay. No hourly creep.

Should we build native or cross-platform?

One Flutter or React Native codebase covers both stores and usually costs meaningfully less than two native builds. Native earns its extra cost when the app leans hard on the device: heavy camera or sensor work, on-device machine learning, complex background processing or animation that has to be flawless. We'll tell you which side of that line you're on during scoping.

How long does an app take to build?

A focused MVP is typically six to twelve weeks from kickoff to store submission. A larger product with a custom backend, multiple user roles and payment handling runs longer, and we sequence it so something testable is in your hands within the first few weeks rather than at the end.

Do you handle App Store and Google Play submission?

Yes, including the parts that catch people out: privacy nutrition labels and data safety declarations, screenshots at every required size, age ratings, export compliance and the review notes that stop a rejection. We prepare the listing and stay with it through review.

Who owns the code and the developer accounts?

You do. The repository is yours, the Apple Developer and Google Play accounts are opened in your name with us added as a user, and every third-party service is billed to you. If we part ways you keep the code, the accounts, the users and the reviews.

What does app maintenance actually involve?

Apps decay if nobody touches them. iOS and Android ship major releases annually, dependencies need patching, and store policies change. A maintenance plan covers OS compatibility updates, dependency and security patches, crash monitoring and a monthly allowance for small changes.

How much does a website cost?

It depends on page count, whether you need a content management system, and how much of the copy and imagery you already have. We quote a fixed price after a short scoping conversation, and that price is what you pay.

WordPress or a custom build?

WordPress if non-technical people will be publishing regularly, because that convenience is worth the maintenance overhead. A hand-built static or framework site if speed, security and search performance matter more than daily editing. We'll walk you through the trade-off rather than defaulting to whichever is easier for us.

Will the site work properly on phones?

Every site we build is designed mobile-first and tested on real devices, not just a browser window resized. Most traffic arrives on a phone over an imperfect connection, so that's the case we optimise for.

Get a fixed price for your app or site

Tell us what it needs to do and roughly when you need it. We'll come back with a number and a timeline, not a discovery invoice.