# Sonora — Sound-Wellness App | Our Work | QQuantum.ai

> Sonora: we designed and built sonora.com and its backend, produced the iOS and Android app assets and supported the prototype. Measured figures, honest scope.

Source: https://qquantum.ai/work/sonora

[Our work](https://qquantum.ai/work) Sonora

Live · 2026 · Consumer wellness · Mobile + web

# Sonora A sound-wellness app, free and ad-free.

Website, backend and app assets.A free sound-wellness app, described by its publisher as AI sound therapy that reads a short vocal sample at the start of a session and generates a soundscape for that moment. We designed and built the website and its backend, produced assets for the iOS and Android apps, and supported the application prototype.

- Cognitive AI Ltd
- 2026

[Visit sonora.com →](https://sonora.com/) [App Store →](https://apps.apple.com/app/sonora-ai-driven-sound-therapy/id6742666392) [Google Play →](https://play.google.com/store/apps/details?id=com.Sangen.NEO.AI) [Press kit →](https://sonora.com/press)

WHAT IT IS

## The app listens first, then generates the sound.

A free sound-wellness app, described by its publisher as AI sound therapy that reads a short vocal sample at the start of a session and generates a soundscape for that moment. We designed and built the website and its backend, produced assets for the iOS and Android apps, and supported the application prototype.

Sonora describes itself as AI sound therapy: by its publisher's account, the app reads a short vocal sample at the start of a session and uses it to calibrate what it plays, generating a soundscape of binaural beats, Solfeggio frequencies and nature recordings for that person in that moment rather than picking from a library of pre-rendered tracks. Those are the publisher’s claims about the product, not ours; we built the website around it.

It ships free on iOS and Android with no subscription, no premium tier and no advertising, in a category where much of the competition is paid. That is a product decision with consequences for the build: there is no paywall to hide behind, so the first session has to be good and the site has to convert on the strength of the idea alone.

Sonora is published by Cognitive AI Ltd, part of the Coherence group.

- **Client**: Cognitive AI Ltd
- **Live**: 2026
- **Sector**: Consumer wellness · Mobile + web
- **Platforms**: Web · iOS · Android

THE CONSTRAINTS THAT SHAPED IT

## Four constraints, decided before anyone opened an editor.

Four things about this project decided most of the engineering. They are worth stating because they explain the choices that follow: a build like this is mostly the consequence of its constraints.

- 01 No paywall to hide behind The app is free, with no subscription, no premium tier and no advertising. There is no trial funnel and no upsell to carry a weak first impression, so the site has to do the persuading on its own. That pushes effort towards clarity and speed rather than towards conversion machinery.
- 02 The audience arrives on a phone A wellness app is found on a phone, frequently on a cellular connection, often at the end of the day. A heavy page is not a slow page here — it is an abandoned one. Performance stopped being a quality metric and became the primary design constraint.
- 03 The product claims belong to the publisher Sonora’s account of what the app does — the vocal sample, the generated soundscape — is theirs, and we had no basis on which to assert it independently. So the site presents the product in the publisher’s voice and our pages describe it as their claim. That is a writing constraint with a real effect on the copy.
- 04 One design system, three destinations The same visual language had to work on the marketing site, in the iOS App Store and on Google Play, each with its own dimensions and review rules. Producing those separately is how brands drift, so they came out of one system.

WHAT WE BUILT

## Five things we built, and the one we did not.

1. The website, designed and built from scratch Art direction, layout and front-end build across the marketing site, the science and learn sections, and the press kit. No template, no page builder. We built it
2. The website backend Laravel application behind the site — content, the press kit, forms and the deployment pipeline. We built it
3. Performance and technical SEO Bundling, image formats, font strategy and markup built for Core Web Vitals rather than retrofitted afterwards. The measured figures on this page are the result. We built it
4. iOS and Android app assets Store and in-app visual assets produced for both platforms from a single design system. We built it
5. Prototype support We worked with the client on the application prototype ahead of the production build. We built it
6. What we did not build The vocal-biomarker analysis and the audio generation engine are Cognitive AI's own work, as is the app itself. We built the website, its backend and the app's visual assets, and supported the prototype. Not ours

THE DECISIONS THAT MATTERED

## Three choices, and what they cost.

01

### No front-end framework.

The site is server-rendered with progressive enhancement, and the JavaScript that ships is the small amount that genuinely needs to run in the browser. The measured figure below — a couple of kilobytes — is not a target we set and then celebrated; it is what is left when you decline to send a framework to a phone. The cost is real: interactions that a framework gives you free were written by hand, and a team used to component state would find the codebase unfamiliar. On a marketing site with a handful of interactive moments, that trade came out clearly in favour of the visitor.

02

### Performance designed in, not tuned afterwards.

Image formats, font strategy, bundling and markup were decided at the start rather than retrofitted once a score came back red. The honest caveat is on the page: our own measurement puts modern image formats at four fifths of the images rather than all of them, and that remaining fifth is a known gap rather than a rounding error.

03

### An application backend for a site that could have been static.

The site sits on Laravel because the press kit, the content and the forms all need somewhere to live and someone non-technical needs to change them without a deploy. A static generator would have been faster to stand up and worse to live with a year later. We do not sell a house stack — this was the right answer here and would not be on every project.

STACK

## What it is built with.

- **Application**: Laravel PHP 8.4 Blade
- **Front end**: Vite Modern ES modules Progressive enhancement
- **Assets & delivery**: WebP imagery SVG logos and icons LiteSpeed HTTP/2

Chosen for this project. We are not a Laravel-only studio and do not sell a house stack.

MEASURED

## Measured performance, with the method.

- **JavaScript shipped**: 2.4KB
- **CSS shipped**: 17KB
- **HTML document**: 20KB
- **Time to first byte**: 599ms
- **Images in modern formats**: 80%

Measured on 7 September 2026. Taken from a cold request with Accept-Encoding pinned to gzip. Transfer sizes are compressed bytes over the wire, first-party assets only. Figures move a little with compression negotiation and network conditions. Run the commands to check them — the numbers should land close to these.

curl -sS -o /dev/null -H 'Accept-Encoding: gzip' -w 'TTFB %{time_starttransfer}s HTML %{size_download} bytes\n' https://sonora.com/ curl -sS -o /dev/null -H 'Accept-Encoding: gzip' -w 'JS %{size_download} bytes\n' https://sonora.com/build/assets/app-DRdBa2Y6.js

SCREENS

## The live site, screen by screen.

sonora.com — mobile, 390×844

sonora.com/science — 1440×900

On a phone

App screens published by Cognitive AI Ltd in their press kit and used with their permission. The app itself is theirs — we produced its visual assets and supported the prototype.

Questions

## Questions about this build.

### Did you build the AI?

No. The vocal-biomarker analysis and the audio generation engine are Cognitive AI’s own work, and so is the app. We built the website and its backend, produced the visual assets for the iOS and Android apps, and supported the application prototype. We are specific about this because a portfolio that implies you built the whole product is worth nothing the moment someone checks.

### How was the performance achieved?

By deciding it up front rather than optimising afterwards. Images are WebP, logos and store badges are SVG, the JavaScript is bundled through Vite and kept deliberately small, and the markup is server-rendered so the first paint does not wait on a framework. The figures on this page are what that produces — you can re-run the measurement yourself with the command in the method note.

### Can we see the code?

The repository belongs to the client, so no. What you can do is read the page source of sonora.com, which is the honest version of the same question: bundle sizes, markup structure and asset strategy are all visible from the outside.

### Do you only build in Laravel?

No. Laravel suited this project — a content-driven marketing site with a backend, a press kit and forms, shipped quickly by a small team. We pick per project and we do not sell a house stack.

### Can we talk to the client?

Ask us on a call. Whether a reference is available is the client’s decision rather than ours, and we will not promise one on their behalf.

Keep reading

- [Case study Podswap](https://qquantum.ai/work/podswap)
- [Design AI Web Design](https://qquantum.ai/creative-design/ai-web-design)
- [Work All of our work](https://qquantum.ai/work)
