AetherCurrent Studio hub + landing→editor→checkout funnel + A/B scaffolding
AetherCut v1.9.36 shipped on Feb 26, 2026.
What's new in v1.9.36?
- New /studio hub — AetherCurrent portfolio page listing all six sibling products (Vault, IronFile, Promethius AI, AetherCut, AetherMix, AetherLens) with per-project waitlist signup for upcoming and in-progress projects. Linked from the login footer and a new 'By the same founder' hero band between the manifesto and stats bar.
- Landing → editor → checkout funnel instrumentation — 17 new whitelisted events (landing_hero_viewed, scroll depth, guest/Google CTA clicks, exit-no-click, guest-save-nudge, premium-usage-pill, stripe_checkout_started/completed, studio-band clicks, A/B variant views). Admin dashboard at /admin/funnel gained three new sections with computed conversion percentages.
- Guest save nudge — non-blocking sonner toast after 2 minutes of guest editing with clips loaded, offering an inline 'Sign in' action so first-time visitors get a save prompt BEFORE the export intercept fires.
- Premium usage pill in the editor Header — amber early-warning badge that appears the moment a free user applies a Pro tool to a clip. Auto-hides for Pro users and when no premium fx are active. Fixes the 'surprise at export time' complaint.
- A/B variant scaffolding — deterministic 50/50 bucketing keyed off a persisted per-visitor UUID; sets <html data-ab-variant='A|B'> so CSS or component overrides can roll a variant without a redeploy.
- Whitelist admin dashboard now flows into a 2-column masonry at 1200px+ (3-column at 1600px+) with .card--full opt-out for banner cards, so the roster stops stacking as a single vertical column on desktop.
- AetherCut version tag on the /studio card auto-syncs to APP_VERSION here in changelog.js — no second edit required when you bump.
Making the new funnel and Studio hub useful on day one
The practical win in this release is not just that there are more events, but that the new /studio hub, the landing page, the editor, and Stripe checkout can now be read as one connected path instead of four separate surfaces. That matters because the failure modes are usually different at each step. A high landing_hero_viewed count with weak CTA clicks points to message or layout friction on the landing page. Healthy CTA clicks but a drop before meaningful editor activity suggests onboarding friction after entry. Strong editing engagement with weak stripe_checkout_started often means people are discovering paid features too late or too ambiguously, which is exactly where the guest save nudge and premium usage pill now become diagnostic instead of cosmetic. If you are checking the new admin sections for the first time, start by comparing ratios rather than raw totals: hero views to CTA clicks, CTA clicks to clips loaded, premium tool exposure to checkout starts, and checkout starts to completions. That sequence will usually tell you where to look next faster than browsing event counts one by one.
A good first implementation pattern for the A/B scaffolding is to keep the variant change narrow and tied to a single question. Because bucketing is deterministic per visitor UUID and exposed on <html data-ab-variant="A|B">, you can safely test presentation changes without introducing cross-session randomness. For example, if you want to know whether the new “By the same founder” band is acting like a trust signal or a distraction, one variant can keep the current band treatment while the other reduces its visual weight or changes its placement behavior. The useful part is not merely tracking A/B variant views, but reading those views against downstream behavior: did one variant improve guest or Google CTA clicks, did it reduce exit-no-click sessions, and did it have any measurable effect on editor entry or checkout initiation? That kind of test is much cleaner than broad “redesign” experiments because if it moves, you can attribute the movement.
There are also a few easy interpretation mistakes to avoid. The first is treating the guest save nudge as a conversion event by itself; it is better understood as a rescue point for users who have already shown editing intent. If it fires often but sign-in behavior does not change, the issue may be timing, copy, or the fact that users still do not perceive enough value in saving yet. The second is overreading the premium usage pill. Its job is to remove surprise, not to force upgrades, so an increase in premium-tool awareness paired with a short-term dip in export attempts may actually be a healthier signal than silent frustration at the intercept. The third is forgetting that /studio now participates in the same ecosystem of clicks and version visibility. Because the AetherCut card version auto-syncs from APP_VERSION, the hub is now a live trust surface rather than a static portfolio page. If people are moving from the studio band into /studio but not returning to the product funnel, that is useful information too: it can mean the band is creating curiosity without reinforcing why AetherCut is the right next click.
Which features does this release touch?
How do I get this update?
Open the editor and you have it. AetherCut runs in Chrome, Edge, Safari and Firefox. There is nothing to install, and you can edit without an account. Open the editor or see how it works.