Websites and web apps
Sites and applications with Next.js or SvelteKit and TypeScript. Headless CMS so clients edit their own content, internationalisation, and forms that land where they should.
Full-stack developer
I'm Arnau. I sign as nauran. I design and build products end to end: from the API contract to the phone screen, and from the container to the backup.
01
Sites and applications with Next.js or SvelteKit and TypeScript. Headless CMS so clients edit their own content, internationalisation, and forms that land where they should.
Native clients with React Native and Expo for iOS and Android, built to work offline and to share the data contract with the server.
Docker, Cloudflare, CI/CD, backups and monitoring. Services deployed with care, easy to operate and to recover.
Workflows built on language models: extracting data from images, bots, and coding-agent sessions coordinated under clear rules.
02
What I have going on: client work and products of my own that I am getting ready for a public release.
Multilingual website with a CMS for a tattoo artist
Sales landing for her online course, gallery, blog, booking and contact in four languages (EN, RU, HY, JA). The artist manages every piece of content from an embedded Sanity Studio, no code involved.
VisitExpense manager with receipt OCR and bank reconciliation
Snap the receipt, a vision model extracts the data and you review it before saving; bank statements are imported and matched against what was logged. Native mobile app sharing an API contract with the server. In development, with a public release planned.
Real-time workout logging with stats
Sets, reps, weight and technique notes from your phone, with rest timer, supersets and a plate calculator. Keeps working on flaky gym Wi-Fi thanks to an idempotent write queue. In development, with a public release planned.
03
Every non-trivial change starts with a short document: what, why and how it is verified. Architecture decisions are written down as ADRs.
Nothing gets integrated without typecheck, lint, tests and build passing on the actual commit. Linear history, one task per branch.
No secret in a commit or on the command line. One identity per machine, keys in hardware, and an audit trail of what goes in and out.
Every repo states where it stands and what is missing, so anyone, human or agent, can pick up where it was left.
04
Have a project, or want to talk about one of these? Drop me a line.