Astra
Two release trains, zero new features — Astra has been in pure maintenance mode since spring.
A side-by-side editorial comparison of Aseprite and Figma — release velocity, themes, recent moves, and the top alternatives to consider.
Steady 1.3 maintenance, with the Lua API quietly becoming Aseprite's extension point.
Aseprite is deep into a long 1.3.x maintenance line: v1.3.18 landed in July after three betas stretching back to February, followed within the hour by a 1.3.18.1 crash-fix patch and, two weeks later, a one-line 1.3.18.2. The substantive work in 1.3.18 splits three ways — performance (undo/redo now keeps doc::Objects in memory), discoverability (Preferences search, configurable tooltip delay, clearer layer groups in the timeline), and Lua API growth (custom file formats for load and save, eyedropper in app.useTool). By volume, bug fixes dominate: tilemap selection, zoom distortion, crash paths.
Figma is layering AI deeper into Make and Draw while smoothing out the desktop experience.
The most recent stretch is split between AI-feature enrichment and UX polish. Figma Make added voice-to-text input and question cards for more conversational control while building. The AI image flow (Make Image, Edit Image) gained richer reference handling. Draw consolidated more tools into the same mode so designers stop bouncing between contexts. The desktop app picked up faster file transitions — links open in place, recent work is searchable, the next file pre-loads.
Aseprite is deep into a long 1.3.x maintenance line: v1.3.18 landed in July after three betas stretching back to February, followed within the hour by a 1.3.18.1 crash-fix patch and, two weeks later, a one-line 1.3.18.2. The substantive work in 1.3.18 splits three ways — performance (undo/redo now keeps doc::Objects in memory), discoverability (Preferences search, configurable tooltip delay, clearer layer groups in the timeline), and Lua API growth (custom file formats for load and save, eyedropper in app.useTool). By volume, bug fixes dominate: tilemap selection, zoom distortion, crash paths.
The cadence is beta → final → patch, with identical fixes backported across the 1.3.17.x and 1.3.18.x branches — several entries here are branch twins carrying the same two or three fixes. The one directional thread is extensibility: the Lua API version moved 39 → 40 and now lets third-party code register sprite load/save formats the core used to own exclusively. Separately, "refactors needed for new layer types" appears across two releases as internal groundwork with no user-visible effect yet.
Expect the 1.3.18.x patch train to keep absorbing crash reports at this pace, with the next feature release cashing in the new-layer-type refactors that have been landing quietly.
The most recent stretch is split between AI-feature enrichment and UX polish. Figma Make added voice-to-text input and question cards for more conversational control while building. The AI image flow (Make Image, Edit Image) gained richer reference handling. Draw consolidated more tools into the same mode so designers stop bouncing between contexts. The desktop app picked up faster file transitions — links open in place, recent work is searchable, the next file pre-loads.
Two arcs. Make is maturing as Figma's natural-language design surface — voice control and structured questions move it from prompt-only to conversational, and the image reference work makes the generation loop more controllable. Around it, Figma is doing the unglamorous quality work — Draw tool surfacing, desktop transition smoothness — that compounds into a stickier daily-use product.
Expect Make's conversational surface to keep absorbing input modalities (likely structured form fields and asset uploads next) and the FigJam-as-coding-agent-whiteboard angle that surfaced just before this window to expand into more agent integrations. Draw will probably continue collapsing tool modes until it feels closer to one canvas with progressive disclosure.
Other Design products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Aseprite or Figma.
Two release trains, zero new features — Astra has been in pure maintenance mode since spring.
A component library turning into scaffolding for AI apps
The editor now prints to a CVS counter, and that is the second business bolted on this summer.
Webflow is building for the answer engines, not just the search results page.
The 10.6 alphas are an Angular tooling rebuild wearing a version number.
Every image reader is now assumed hostile, and the fuzzer proves it monthly
See all Aseprite alternatives → · See all Figma alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Aseprite and Figma are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Aseprite and Figma are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Design products to evaluate alongside.
Top Aseprite alternatives in Design are ranked by recent ship velocity. Browse the "Aseprite alternatives" section above for the current picks, or visit /alternatives/aseprite for the full list with editorial commentary on each.
Top Figma alternatives in Design are ranked by recent ship velocity. Browse the "Figma alternatives" section above for the current picks, or visit /alternatives/figma for the full list with editorial commentary on each.