noxera.

The work

Three real projects,
and what tried
to break them.

Three, because these are the three we can show. Each one was built to work somewhere harder than a demo: a hall with no wifi, a phone on a metered bundle, a car, a power cut.

So this page is a rig. Pick a condition at the bottom of the screen and all three answer at once — including the one whose honest answer is “it doesn’t”.

The proving ground

Break them and see

The screens below are drawings of the real things, not live copies of them. They are here so a condition is something you can watch, not a sentence you have to take our word for.

Conditions

Conditions normal. Pick one and watch all three.

Ours · used daily

NOXERA — the assistant we actually use

The problem

Every assistant worth having lives on somebody else’s server, speaks like a call centre, and forgets you between sentences. We wanted one that belongs to us: knows our week, hears us while we are driving, and does not go quiet the second the line does.

What was built

  • Voice in, voice out — talking is the interface, not a text box with a microphone glued to it.
  • Memory that survives the conversation, so the next one starts where the last one stopped.
  • One assistant in three places — phone, car, laptop — carrying the same memory into each.

Three places, because you can count them. There is no other number on this page that we cannot point at.

See the NOXERA page →

Drawing of the phone screen

What it had to survive

Power cut
The laptop has a battery and the car has the car. This is software on the machine in front of you, not a service that has to be up somewhere else.
2G bundle
Speech in, a sentence back. Nothing on that trip is a page of images, so a thin line costs you a pause, not an answer.
360px phone
The phone is the main screen, not the cut-down one. If it cannot be run with one thumb it is not finished.
No line
It falls back to a model running on the machine itself. Smaller and slower than the one on the network — but it still answers, and that is the difference between a tool and a toy.

What we keep: this one is ours, so here is the honest version — it is the studio’s own product, used every day. If it broke at breakfast we would know before lunch. That is the entire reason it leads this page: we do not sell software we would not live with.

Client · live

Almado Safaris — the site people decide on

The problem

A safari is a serious amount of somebody’s savings, and the decision gets made on a phone, usually far from the place being sold. The photographs are the product — and photographs are the heaviest thing you can put on a page. The site had to carry them without punishing the person paying for the data.

What was built

  • The operator’s public site, at almadosafariskenya.com — their own words and their own photographs.
  • Laid out for a phone first and a laptop second, because a phone is where most people here browse.
  • A clear way through to asking a human, rather than a form that ends in silence.

No visitor numbers here. We have not measured them, so we are not going to print them.

Drawing of the site on a phone

What it had to survive

Power cut
It is a hosted site, not a machine humming in the office. A blackout at the operator’s desk does not take the business off the internet.
2G bundle
Words and layout arrive first, photographs at the size the screen asked for. The page can be read before the last image lands.
360px phone
Drawn at 360px and grown from there, because a small phone is the screen a visitor is most likely holding, not the big one it was built on.
No line
A page already open stays readable. What no site can do is invent a connection — sending anything waits for the line to come back.

What the client keeps: the domain, the hosting account, the code and the photographs — in their name, with the passwords handed over. Nothing about the site needs us to still be here next year.

Client · anonymised · sample data

Conference Ops — five days, no clipboards

The problem

A five day youth conference runs on paper. Who checked in. Who is in which company. Who missed the morning. Which young person has an allergy nobody can find at the exact moment it matters. By day three the clipboard and the spreadsheet disagree, and everybody knows it.

What was built

  • Check in — arrival marked once, visible to everyone who needs it.
  • Attendance — marked per activity, per day, standing up.
  • Companies — who belongs to which group, and who leads it.
  • Counsellor notes — written by the adults responsible, seen only by them.
  • Reports — headcounts, dietary and medical lists, contacts, exportable.
  • CSV import — for a roster that arrives as a spreadsheet.

Six, because you can count the list above. That is the only number in this case study.

Drawing of the register — invented rows

What it had to survive

Power cut
Every mark is saved the moment it is made, on the server, not held in a phone until somebody remembers to press save. A dead battery costs one phone, not one morning.
2G bundle
Pages of text and tables, rendered on the server. The heaviest thing on the screen is a list of names.
360px phone
It opens and works on a phone, and nothing on the critical path needs a mouse. A check in screen built for one thumb is the next thing on the list — not claimed here as done.
No line
It doesn’t. No line means no mark: every save needs the server. That is written on the list of what to fix rather than hidden behind a nicer sentence. Until it is fixed, the workaround is paper while the signal is out, typed in after.

What the client keeps: their own data. Records come in as CSV and attendance goes back out as CSV, so the organisers are never stuck inside the app to get at it.

Shown anonymised. No real young person’s data appears on this page, the rows above are invented, and we do not name the organisation or the conference. The whole point of a notes feature is that what gets written about a child stays with the adults responsible for that child.

What is not on this page

No testimonials

Not yet. The first client who says yes goes here, in their own words, with their own name on it. Borrowed praise is worth nothing.

No percentages

No “300% more enquiries”. We did not measure it, so printing it would be making it up. The only numbers above are things you can count in the lists themselves.

No unnamed logos

Work for a client who has not agreed to be shown stays off the site. That rule protects the next client as much as the last one.

Next step

Yours could be the fourth

Three is what we can show today. If you have something that has to keep working in a hall, on a boda, on a 2G phone or through a blackout — that is exactly the sort of thing we like being handed.

Start a project See what we do Questions first

Or write to us: support@noxeratech.com. One person reads it, and that person is the one who would write your code.