Internal assessment of product experience, accessibility, and design-system readiness
RapidAir is a capable domain-specific CAD product with strong core mechanics already in place. The audit found that the product does not need a conceptual reset. It needs the surrounding experience, accessibility posture, and system consistency to rise to the level of the engineering underneath it.
The strongest path is not to replace the editor. It is to fix the accessibility blockers, standardize the non-CAD interface layer, and then modernize the surrounding experience with a clearer design system.
The natural migration path is clear: resolve the critical accessibility issues first, adopt Optics for the surrounding Rails and application UI layer, and keep the specialized CAD skin where it still serves the product well.
Those strengths matter because they show the product already understands the user's task. The audit is about sharpening the wrapper around that task, not discarding the product's best instincts.
The first sprint should be small, decisive, and compliance-oriented. Four issues deserve to move before any broader visual modernization:
These are high-impact, low-ambiguity fixes. They improve real usability immediately and remove blockers before design-system work begins.
RapidAir currently carries two visual systems at once: CSS custom properties in some areas and compiled-away SCSS variables in others. That split weakens maintainability and makes theming harder than it needs to be.
The practical move is to standardize the surrounding application chrome and shared interface components first, while leaving specialized CAD behavior intact until the common layer is healthier.
The editor is the strongest surface. The weaker moments appear before and around it: onboarding, account flows, visual hierarchy, and responsive behavior.
This order keeps the work honest. It removes risk first, creates a cleaner foundation second, and only then spends design energy on broader experience lift.
The first RapidAir run established the artifact trail future audits should preserve: the original raw audit, a detailed internal report, a polished presentation artifact, and a clear translation from findings into design direction.
Keep the raw audit, the finished audit document, the published presentation, and any prototype or deployment that helped make the recommendation legible. The farming system is strongest when the whole chain remains inspectable.