Raven Prism opened US preorders on October 29, 2026, with initial shipments expected in January 2027. For developers evaluating its interface, Raven’s current framework documentation highlights an important constraint: pure black cannot appear as opaque black on its additive waveguide display.
Company-issued October 29 announcement: preorder milestone and expected shipments
The background is still part of the scene
The framework’s color guidance says display light combines with light from the real world. Its starter guide describes black as transparent. The practical implication is that drawing a black rectangle should not be treated as placing an opaque dark panel over the physical scene behind the wearer’s view.
Raven Framework: display, color and waveguide guidance
There is a separate software-layering point. Raven notes that black button backgrounds can occlude other displayed content. Covering another part of the app’s drawing is different from blocking incoming real-world light. Keep those two meanings of occlusion separate when discussing a mockup.
Try a fictional note-card design
Imagine a fictional app that displays a short reminder: bring the blue notebook. Its designer places the message inside a black card and assumes the card will hide a patterned wall behind it. The reminder, card and wall are invented teaching examples, not an implemented Raven app or device test.
The assumption is the part to revisit. Make one sketch showing only the app’s drawing and another showing that drawing over the proposed scene. Ask what background the letters would actually be read against. Do not use a desktop screenshot with a solid black canvas as proof that the physical wall would disappear.
Now shorten the reminder, separate its icon from the text and compare two layouts while keeping the message unchanged. The exercise is to identify which change addresses clutter and which assumption concerns the display itself. It does not establish a universally readable font, brightness setting or color combination.
Use the simulator as an approximation
Raven’s README explicitly calls the desktop simulator an approximation of waveguide color appearance. It says actual appearance depends on factors including ambient lighting, display brightness, waveguide properties and perception. The starter project includes Day, Night and Raw simulator views.
Official starter project: simulator modes and display explanation
A useful evaluation note should identify the mode used and preserve the same content when comparing views. Record what was inspected: text visibility, overlap between app elements, or a proposed background assumption. Leave hardware appearance unverified until it has actually been checked rather than silently promoting a simulator observation into a device measurement.
Write a handoff that preserves the distinction
Attach the framework version, layout revision, simulator mode and unresolved questions to the design review. Keep drawing-order problems separate from real-scene readability. If a reviewer says the black card fixes the background, ask which background they mean: another rendered widget or the physical environment.
The documentation identifies the framework as an early preview, so recheck its current guidance before implementation. No SDK was installed and no glasses were tested for this article. Its purpose is to make the next design discussion precise enough that a visually convincing mockup does not answer a different question from the one being evaluated.
Review the fictional black card
