Nathan Cole · Redruth, Cornwall
The short version
I design, build, test and ship native apps, websites and full-stack products from Cornwall. Seven of my apps are live on Apple’s App Store, and the work behind them reaches from the interface to authentication, payments, databases, cloud services, AI controls and release engineering.
What that means in practice
I am most useful where product, design and engineering meet: turning a real-world problem into a system people can understand, trust and keep using.
I can move from an unclear problem into product scope, interface design, data models, implementation, automated tests, cloud deployment and a releasable product. That breadth matters because the difficult failures often sit between those layers.
My work spans Swift and SwiftUI, React Native and Expo, Kotlin Multiplatform, React and Next.js, Node services, PostgreSQL, Supabase, Cloudflare Workers, R2, Render and the Apple release ecosystem.
I build AI as a controlled part of a real workflow: explicit consent, bounded inputs, structured output contracts, post-model validation, human confirmation, useful fallbacks and tests for what happens when the model is wrong.
The route here
Hands-on development across mobile products, websites, backends, cloud systems, AI workflows, geospatial platforms, scientific tools and data pipelines.
VectorPoint, Tiny Care, SiteMate, Hey, Love, Care Circle, PairPlate and The Brief are published under my own Apple developer account. Orbitarium is the next native iOS product in development.
I worked inside a high-volume global music-distribution platform across structured metadata, release checks, policy-led decisions, content operations and user support—experience that shaped how I think about production systems and data quality.
I am 33, based in Redruth and hold a 2:1 BA (Hons) in Music Technology from Falmouth University. Earlier management, sales and customer-facing roles taught me to explain difficult work in normal language.
Published work
These are public products with App Store listings, real interfaces and first-party build notes—not invented agency case studies.
UAP research without the noise.
Read the build note ↗Family sync · subscriptions · privacyCalm tracking for families.
Read the build note ↗AI day logging · business ops · secure syncThe trade desk in your pocket.
Read the build note ↗Private media · audio · trusted sharingLove, kept safe.
Read the build note ↗Care coordination · roles · privacyA private circle around someone.
Read the build note ↗Nutrition · AI estimates · social accountabilityNutrition, together.
Read the build note ↗Editorial systems · evidence · personalisationCalm news, clearly sourced.
Read the build note ↗Working toolkit
I have deliberately worked across several stacks because different products need different strengths. Native iOS, cross-platform mobile, web, backend and data work are connected disciplines in my projects, not separate hand-offs.
How I work
I start with the person, the awkward workflow and the failure that matters. Then I reduce the idea to an inspectable first release, make the risky assumptions explicit and build in slices that can be tested properly.
Security, accessibility, privacy, empty states, degraded networks, account deletion, payment boundaries and release operations are part of the product. I would rather explain a constraint honestly than hide it behind a polished demo.
The result should be useful software and a codebase whose decisions remain understandable after launch.
Have a product idea, an inherited build or a workflow that keeps wasting time?