How we build

Four engineering rules, checked every release.

EGGIE is still being built. These are the rules it’s built to and the numbers we test it against. Where something is a target rather than a result, we say so.

  1. Security
  2. Speed
  3. Hot fixes
  4. Privacy
  5. Under the hood

Security

Tested as if someone is trying to break in.

Before we write a service, we write down who might attack it and how. Then we test exactly those paths.

  • Attack tests on the critical paths: sign-in, permissions, chats, points, file uploads and the AI gateway.
  • Before launch, an outside security firm will run a penetration test. High and critical issues get fixed before we submit to the App Store.
  • Your account key is made on your phone. Only an encrypted backup leaves it, to your own iCloud. We can’t see the key.
  • Important account records are signed. Once EGGIE launches, an hourly digest of them will be written to a public ledger, so anyone can check them — and we can’t quietly change them either.
  1. Eggy ID openedsigned
  2. Joined a communitysigned
  3. Invite acceptedsigned
  4. Membershipsigned
Hourly digest
Public ledger

Planned for launch: anyone will be able to check a record against the ledger.

Speed

As fast as the chat apps you already use.

We set the bar at the big messaging apps and test on mid-range phones, not just fast ones.

These are targets, not results yet. We’ll measure them in the app and on the servers, and each milestone ends with a load test.

p95: 95 of every 100 are at least this fast.

Targets we test against

  • Open a chat ≤ 300 ms
  • Message to the other person (p95) ≤ 300 ms
  • App start to chat list ≤ 1.5 s
  • Reconnect after switching networks ≤ 2 s

Hot fixes

Most fixes, without an update.

Rules, text and switches live on our servers, so most changes reach you without a new version. They go out to a few people first and can be rolled back in one step.

  • Rules that change often — points, tasks, limits — live on the server, not in the app.
  • Help pages, FAQs and the Spirit’s prompts come from the server too, with defaults built into the app.
  • Code fixes are for bugs only and follow App Store rules (2.5.2). New features always go through App Store review.

Oovix servers

  • RulesPoints, tasks, limits
  • TextHelp, FAQs, Spirit prompts
  • SwitchesCan turn a feature off, never on
EGGIE on your phone Picks it up — no download
  1. A few people
  2. More
  3. Everyone

one-step rollback

Privacy

Only what the app needs.

We collect what EGGIE needs to work, and nothing for advertising.

  • We don’t sell your data or use it for targeted ads.
  • The Spirit uses OpenAI and DeepSeek only after you agree, and asks again if the provider changes.
  • Account keys, passwords and codes are never sent to AI.
  • Delete your account in the app; your data is removed after 7 days.

Under the hood

The technology, in plain words.

Your phoneAccount key

Hong Kong

App serviceAccounts, communities, points
Messaging serviceReal-time chat
Public ledgerHourly digest · after launch
AI providersOnly with your consent
  • Servers in Hong Kong

    On network routes tuned for mainland China, and close to Southeast Asia, so every request has less distance to travel.

  • A service just for messages

    Chat runs apart from everything else, built to hold many open connections at once, so messages stay quick when the rest is busy.

  • Keys stay on your phone

    Your account key is made on your phone and protected by its secure chip. The backup goes to your own iCloud, locked with a password only you know.

  • Records built to be checked

    Important records are signed and logged in order. Once EGGIE launches, an hourly digest will go to a public ledger, so a change after the fact would show.

Questions about how we build?