AetherCutChangelogHow it worksPricingOpen the editor

Home / Changelog / v1.5.3

v1.5.3

Support AetherCut from the login page

AetherCut v1.5.3 shipped on May 3, 2026.

What's new in v1.5.3?

  • New 'Support AetherCut' section on the login page — donate without needing to sign in first.
  • Reuses the same Stripe donation flow (anonymous donations are supported on the backend)
  • Sits between 'Spread the word' and the footer — natural place for the 'if you can't share, support' progression.

Where the new login-page support option helps most

Adding a donation option to the login page changes the moment when support becomes possible. Before this update, a willing supporter still had to move through sign-in first, which adds friction at exactly the point where intent is weakest. Now the path is simpler: someone can arrive, understand what AetherCut is, choose not to create an account yet, and still contribute immediately. That matters most for people who are already convinced by a recommendation, a demo, or a shared project link, but are not ready to commit to registration. It also helps returning visitors who land on the login screen from bookmarks, old sessions, or expired auth states. Instead of treating that page as a dead end unless credentials are available, v1.5.3 turns it into a useful stop for people who want to help right away.

A practical example is someone who hears about AetherCut from a colleague, opens the app, and lands on the login page during a break at work. They may not have time to compare plans, recover a password, or decide whether to create an account on the spot. In older flows, that visit often ended there. With the new placement, there is now a clear middle ground between doing nothing and going through sign-in: they can support the project first, then come back later when they are ready to use it more deeply. The same pattern applies to people on shared devices, users testing whether the app feels trustworthy, or supporters who simply prefer to keep donation separate from account activity. Because the same Stripe donation flow is reused and anonymous donations are already supported on the backend, the experience stays consistent with the rest of the product rather than feeling like a separate or improvised path.

Placement on the page is doing real work here. Putting the section between “Spread the word” and the footer creates a progression that makes sense without forcing attention. A visitor first sees the lighter-weight option of helping by sharing, then, if sharing is not the right fit, sees a direct way to contribute financially. That order matters because it respects different levels of commitment. It also avoids one of the more common mistakes on login screens: placing support messaging so aggressively that it competes with the primary task of getting into the app. By keeping support below the share prompt and above the footer, the page can acknowledge support intent without making the interface feel like a donation gate. The result is more likely to feel like an invitation than an interruption.

For teams or solo makers evaluating whether to use this path themselves, the easiest way to get started is to think about the login page as a trust page, not just an authentication page. Visitors who arrive there are already making a judgment: does this product seem active, clear, and worth returning to? A visible support option can strengthen that impression if it is presented plainly and tied to a donation flow that already works elsewhere in the product. The main implementation pitfall is inconsistency. If the language on the login page suggests one experience but the payment flow behaves differently, people hesitate. Reusing the existing Stripe flow avoids that problem because the expectations around checkout, confirmation, and anonymity are already established. Another mistake is assuming every supporter wants an account relationship. Anonymous donations exist for a reason; some people want to help without creating another login, and v1.5.3 now meets them where they are.

There is also a quieter product benefit to this change: it gives AetherCut a better answer for edge-case traffic. Not every visit to a login page comes from an active user trying to authenticate. Some come from curious readers of release notes, people following social posts, past users checking in, or supporters sent by word of mouth. Those visitors are easy to overlook because they do not fit the standard account funnel. By exposing support on the login page, AetherCut acknowledges that interest in the project can exist before, after, or entirely outside account creation. That does not replace sign-in as the page’s main job, but it broadens what a successful visit can look like. In practice, that means fewer “come back later” moments turning into lost intent, and more chances for willing supporters to act while the motivation is still fresh.

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.

What shipped just before and after?

See all 111 releases · Follow the RSS feed