Skip to content

Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.

6.4 KB
Raw Blame

android-launch/: the Android announcement kit

The post that announces three.ws as an Android app, and the artwork for it. Everything here is generated, not hand-exported, so a change to the product or the brand re-renders rather than drifts.

npm run build:x-grid

That runs scripts/make-x-grid.mjs.

The four-image grid

X lays four attached images out in a 2x2 collage. The kit exploits one property of rectangles to make that collage a single picture: every quadrant of a rectangle has the same aspect ratio as the whole. So the composition is drawn once at 4096 x 2304 (16:9), cut in four, and each 2048 x 1152 tile is itself 16:9. X drops each tile into a cell of the same aspect and crops nothing, and the post reassembles into the image that was drawn.

It is the Seeker carousel idea turned through ninety degrees. That one (solana-mobile/scripts/make-screenshots.mjs) slices a 5400 x 1920 strip for a store listing that scrolls horizontally; this one slices a plane for a grid.

File What it is
kit/android-launch-master-16x9.png The uncut composition. Use it wherever a single image is wanted.
kit/images/01-top-left.png … 04-bottom-right.png The four tiles, in upload order.
kit/IMAGE-ORDER.md The order, restated where someone attaching the images will look.
kit/post.md The post copy.
kit/cmc-article.md The CoinMarketCap article: title, meta description, categories and body, paste-ready for the CMC form.
kit/cmc-cover-640x360.png The master scaled to CoinMarketCap's 640 x 360 cover size (gitignored, regenerated by the build).

Two rules the composition is built around, both learned from how the collage actually behaves:

  1. Upload order is the layout. X fills the grid 1, 2 across the top then 3, 4 across the bottom, in the order the images were attached. Attach them out of order and the picture reassembles scrambled.

  2. What may cross a cut depends on how big it is. This is the whole craft of the format, and it is worth reading before editing the layout.

    X puts a hairline gutter between the cells, roughly half a percent of a tile's width. Through a large, bold shape that hairline is invisible or reads as intentional. Through a face, or 12px of UI text, it reads as broken alignment: half a head on the left, half on the right, a line down the middle. A store carousel has no such problem, because it shows one panel at a time and an object leaving the frame simply continues offscreen. The grid shows all four at once.

    So the composition splits by scale:

    • The headline crosses, and it is the reason the post reads as one picture rather than four slides. It is drawn as two halves that meet at the vertical seam with a word space between them, so the cut falls between "Now an" and "Android app." and never through a glyph. Assembled it is one line across the full width; split, each tile still reads as a complete phrase.
    • The scenery crosses. The glow field, the light beam and the floor are soft and edgeless, so a gutter through them reads as continuity.
    • The phones never cross. They carry faces and small type, which is exactly what a gutter ruins.

    Both rules are enforced, not just written down. The renderer computes each phone's rotated extent, works out which tile it lands in, and throws if it comes within 96px of that tile's edge. It then measures the two headline halves in the page and throws if either reaches the seam. A layout change that would cut a phone, or close the word space, fails the build.

A consequence worth knowing: a 9:16 phone cannot fill a 16:9 tile, so a tile holding one phone looks empty. The two bottom tiles hold a layered pair each, a smaller one set back and dimmed behind a larger one in front.

The headline is sized by the page rather than hardcoded. The two halves are unequal ("Now an" against "Android app."), and each has the same room on its own side of the seam, so the wider half sets the size for both. Fitting their combined width instead runs the longer half off the canvas.

Why the ground is pure black

X's dark timeline is #000000. Anything lighter behind the composition draws four visible rectangles into the feed, and the gutters between them announce where the cuts are. At true black the outer edges dissolve, the gutters stop reading as borders, and the post floats in the timeline as one image.

Two consequences shape the whole design:

  • Nothing may fill the frame with a colour. The ground is radial glows over black that fall off to nothing before the edges, never a filled gradient.
  • The light has to stay dim. The gutter itself is black, so wherever the composition is brighter the gap cuts a visible line through it. Low contrast across a seam hides it; a bright field turns it into a crosshair.

Both are asserted after the render, because a colour tweak undoes them silently and the damage only appears once the post is live:

[x-grid] border 4/255, brightest seam pixel 29/255

The renderer samples the outer border and both seam lines and throws if the border exceeds 6/255 or the composition exceeds 40/255 anywhere a gutter falls.

The phones are drawn in real 3D for the same reason: on a flat black field a 2D-tilted rectangle looks like a sticker. Each is turned on its Y axis and pitched on its X under a 2600px perspective, lit from the upper left so the bezel has a bright edge and a dark one, with a specular sheen across the glass. The seam guard is unaffected, because a turn foreshortens the slab: a phone that clears the seam flat clears it turned.

The mark appears twice

Once large at the top left of the first tile, once quietly at the bottom right of the last. Tiles are opened one at a time and some clients render them as a list, so the first and last both have to carry the brand alone. A single mark in one corner leaves three of the four tiles unbranded.

The phones hold real product

Each phone in the composition is a real capture of the shipping product, reused from the Play listing run:

node solana-mobile/scripts/make-screenshots.mjs --target=play --keep-raw

That writes solana-mobile/publish-play/media/phone/raw/screen-*.png, which this script reads. Nothing is mocked or drawn to look like product UI, so the announcement cannot show a screen the app does not have.