Project 35 / Physical

Solari AI Egg

An intelligent object with a place in the room.

Concept artwork for Solari AI Egg
Studio concept artworkAI hardware / 3D printing / Wireless charging
Project stageExploration
Available to exploreEngineering study
Creative directionAPX Build

The idea

Build an approachable desk object that communicates its state clearly, responds to deliberate interaction and returns reliably to a charging nest. V1 is a button-to-talk device with a small display, speaker and visible listening indication. Unattended listening and custom wireless charging are deferred until the interaction and thermal design work.

An intelligent object with a place in the room.

The connection

Industrial form, interaction design and ambient computing are treated as one problem. The egg and nest are part of how the device is understood, handled and returned to rest.

How it could work

01Deliberate interaction
02Stateful assistant
03Display, voice and light

Use a removable internal chassis inside the printed shell. Keep the battery away from heat-producing electronics and allow service access without breaking the object. Place microphone and speaker so the shell does not turn them into an echo chamber. Treat audio processing and AI response generation as a replaceable service; loss of service should produce a clear offline state.

A wired or contact charging dock is the baseline. Wireless charging is an optional second experiment because coil alignment, separation, metallic ballast and heat interact. If used, select a documented matched transmitter/receiver system with foreign-object and thermal protections. Never infer safety from the shell feeling cool at one point.

What would prove it

Make a weighted shell mock-up and perform 50 dock placements from realistic approach angles. Run 20 scripted interactions including a cancelled request, unavailable network, service timeout and low battery. For charging, monitor cell and electronics temperatures with contact probes while operating and charging, using the component manufacturers' limits.

Proposed gate: at least 48 of 50 placements seat correctly without wobble; every cancelled interaction stops capture; every failed request exits to a usable state within a defined timeout; thermal and electrical measurements stay within all selected component ratings. No battery runtime or charging-speed claim is justified until measured.

The path to a complete build

  1. Validate grip, stability, opening method and display visibility with an inert shell.
  2. Demonstrate the interaction using external power and an explicit button.
  3. Integrate audio and measure feedback/echo in the actual enclosure.
  4. Add a serviceable battery/dock, then separately evaluate wireless charging.
  5. Keep an interaction log, thermal trace, docking results and assembly drawing with the prototype revision.
Open the engineering notebook

Components, interfaces and calculations

Prototype with a development compute board or existing phone, small display, button, status light, microphone, speaker/amplifier and external USB power. Add a protected battery, chemistry-matched charger and power-path arrangement after current measurements. Keep weighted ballast mechanically secured and outside any proposed charging field.

Define IDLE, LISTENING, PROCESSING, SPEAKING, OFFLINE and MUTED states. Button release or cancellation must stop capture. A physical mute control should disable the microphone path where feasible, with visible feedback. Keep service credentials off public firmware and document where audio is processed.

Scope and development questions

Plan 5–8 sessions for the wired prototype. Quote the display/audio, compute and power system separately; shell iterations and replacement batteries need their own allowance. Resolve desired offline behaviour, hand-held versus permanently docked use and acceptable service costs before choosing compute. The most useful first result is a dependable interaction, not an elaborate shell around an unreliable assistant.

Reference basis

This case study develops the project concept into a proposed build route. Numeric gates are design targets; completed hardware tests are not claimed.

From the notebook to the world

See a connection?
Let’s make it happen.