Zooming UIs in 2026: Prezi, impress.js, and why I built something different

There are essentially two established ways to use zooming in web interfaces today. They serve different purposes and make different tradeoffs. I built a third one, so I'll try to be fair about what each does well and where it falls short.

* Prezi Prezi pioneered the zooming canvas for presentations and remains the market leader in that space. It recently added AI-powered generation and text editing tools. It's a polished product with real traction.

But Prezi is a closed platform, not a library. You can't use its zoom engine in your own app. Pricing starts at $15/month for meaningful features, and exporting to PowerPoint flattens all zoom effects into static slides. A recurring complaint from users is that the zooming and panning transitions cause motion sickness. And fundamentally, Prezi uses zoom as a storytelling device between pre-arranged frames. It's not a navigation model. It's a presentation model.

* impress.js impress.js brought Prezi-like zooming to the open web. It's a presentation framework based on CSS3 transforms and transitions, directly inspired by Prezi. It was genuinely groundbreaking when it launched. Its architecture is step-based: you position "steps" in 3D space and the camera moves between them. That's great for presentations, but it doesn't help you build an app where users navigate by zooming into content. impress.js has no concept of dynamically mounting views, managing zoom depth, or handling navigation state. It's a slide deck engine with a zoom trick.

* Zumly This is what I built. Full disclosure: I'm the sole developer. The idea is offering an alternative to traditional page navigation using zooming. You mark an element as zoomable, point it to a view, and Zumly handles the transition and inserts new views. That's basically it.

I started Zumly in 2020 after leaving behind Zircle UI (a Vue zooming library), trying to take what I learned further. Framework-agnostic, focused just on the zoom part. Since then I've rewritten the engine several times, changed the approach more than once. Only now I'm actually happy with how it feels.

Views are dynamically mounted and unmounted during zoom transitions. In impress.js, all steps exist in the DOM simultaneously. In Zumly, you zoom into a trigger element, and the target view gets injected and scaled into place. This is closer to how routing works in SPAs than to how slide decks work.

The landing page is built with Zumly itself so you can get the feel before touching any code.

Curious if anyone else has thought about this space. What makes zooming UIs work or fail?

Landing page (built with Zumly): https://zumerlab.github.io/zumly

GitHub: https://github.com/zumerlab/zumly

91 points | by tinchox6 17 hours ago

24 comments

  • justinc8687 11 hours ago
    As someone who suffers from vestibular migraines, unfortunately visiting the demo site instantly made get dizzy. I highly encourage you to implement the "@media (prefers-reduced-motion: reduce)" media query to handle accessibility [1]. I'd hopefully expect the zooms to turn into normal links or failing that, either slow down or have some kind of non-vestibular-attack-inducing flow.

    Here are some other good resources: https://www.a11yproject.com/posts/understanding-vestibular-d... or https://web.dev/articles/prefers-reduced-motion

    I don't say this as criticism as I'm sure you've never heard of these issues before, but something I'd encourage you (or anyone who relies on animations) to implement into their package.

    [1] https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/A...

    • tinchox6 11 hours ago
      You can use driver none to avoid transitions. And I’m working on reduce motion
    • 8organicbits 11 hours ago
      [dead]
  • DrScientist 2 hours ago
    Has anybody built a UI around the opposite? Shrinking?

    ie rather that zooming in on the content of interest, shrinking the content not of interest?

    Long time ago I used to use https://www.windowmaker.org/ as my X11 window manager and one of the features I really liked was the ability to shrink a window to an icon and place that icon on the desktop for future retrieval ( a bit like having the whole desktop like the MacOS dock ).

    I find such an interface easier to navigate than one where you zoom in and out - where the it's too easy to lose overall context, and where navigation is a bit too linear/hierarchical.

  • sijmen 16 hours ago
    Interesting way to use zooming as a way to transition deeper into sub-dashboards. The navigation from "Mission Control" -> "Satellite" -> "Subsystem" feels oddly intuitive and fun. I would maybe opt for keeping a consistent navbar/sidebar, to support out-of-zoom navigation. And if we are dealing with a lot of power-users some breadcrumb to quickly go back to any zoom-level. But overall, i think this could totally work.
    • tinchox6 14 hours ago
      Appreciate it! Breadcrumbs and back navigation are definitely on my radar.
  • epaga 15 hours ago
    I really love this (and miss the days when Prezi was simple and straightforward).

    I've written an app myself along sort-of similar lines, but it's less a presentation app and more a thought organizer (works on all Apple platforms). https://mindscopeapp.com

    I think what proved key for my own "zoomable" UI was cross-linking, search, and speed/snappiness. Make the animations too heavy and it just slows you down. Zumly seems really great in this regard. Well done!

    • tinchox6 14 hours ago
      Thanks! Speed was a big focus, glad it comes through. Your app looks really cool btw.
  • ericmcer 14 hours ago
    Really cool, like others are saying this makes you feel like you are interacting with all the pages at once instead of one page at a time.

    I did notice that forward doesn't seem to work. I.E. If I click into a page, it zooms in, press back it zooms back out, press forward it flickers the url but doesn't have normal forward behavior.

    I also don't know if you want to support `open in new tab` but that would be a hard req for many people.

    • tinchox6 14 hours ago
      Good catch on forward navigation. Architecturally I don't keep a history of already-visited views, so forward has nowhere to go. It's something worth tackling though, especially for programmatic navigation flows. Open in new tab is on my radar too.
      • ericmcer 13 hours ago
        Under the hood aren't you pushing things into the browser history as navigation happens? I wouldn't try to rewrite the history api myself but just make sure you `pushState()` as navigation happens.
  • lateforwork 15 hours ago
    Love it. But there is a significant usability issue: Lack of signifier (aka affordance). How do I known when something is zoomable? Because there is no signifier, I am frequently disappointed when I click on something and it turns out it is not zoomable.
    • ericmcer 14 hours ago
      that would be more on the consumer of the library than on the library imo.

      Like I wouldn't expect any other frontend router library to decorate links for me in a certain way.

    • tinchox6 14 hours ago
      Fair point. No visual cue for what's zoomable is a real gap. Thinking about how to handle that without cluttering the UI.
      • handfuloflight 11 hours ago
        Maybe an icon on hover or a small static icon but the latter could get repetitive, the hover would solve the repetition.
  • mochidusk 15 hours ago
    I'd say this is more of an interesting take on page transitions. I was expecting mouse wheel scroll to zoom, so I instinctively scrolled expecting some kind of zooming effect.

    I remembered there was a website featured here on HN that had an interactive tour of the scale of the universe ranging from the very microscopic world (if I remember correctly I think it even went down to Planck length) all the way to the macroscopic (black holes, galaxies). I'd be interested in such a zooming library that achieves something like that.

    • tinchox6 14 hours ago
      Yeah the scroll expectation comes up a lot. Scale of the Universe was scijs I think, different beast but a great example of zoom done right.
  • tosti 16 hours ago
    This looks seriously impressive. Also, I wonder what the a11y implications are. I don't miss Macromedia Flash hell at all. This is HTML5, so with a bit of effort it could look beautiful and still cater to the visually impaired.

    Edit: I can't scroll any of the showcases. Probably deliberate, but a cut-off UI can be annoying.

    Edit2: I opened the yellow car on the production line and going back the page got all offscreen and looks messed up

    • tinchox6 11 hours ago
      I turn of scroll events except on home assistant. You can enable or disable depending on your needs
    • tinchox6 14 hours ago
      Thanks! The a11y angle is something I want to tackle properly. Noted the bugs too, the car one is a known issue.
  • handfuloflight 11 hours ago
    My jaw did drop. This could pair really well with a hybrid bread crumb + menu that gives you an escape hatch or granular on demand traversal. Love it!
  • cjlm 14 hours ago
    I think about this space a lot, see Eagle Mode: https://www.youtube.com/watch?v=G6yPQKt3mBA
  • TheTaytay 14 hours ago
    This is indeed seriously impressive. I keep wanting to keep my entire knowledgebase on a canvas so that I can "think" or navigate spatially. Thisis neat.

    In the main landing page, as I was clicking around, I kept wishing to have a legend to show me either "how deep I am" or "how do I get out of here?", and like someone else commented, I would love an affordance showing me what was clickable/zoomable.

    • tinchox6 14 hours ago
      Thanks! Both the depth indicator and the zoomable affordance are things I'm actively working on. Glad the spatial navigation idea resonates.
  • bschwindHN 11 hours ago
    It's extremely easy to break your landing page with the back swipe gesture on mobile safari.
  • jareklupinski 11 hours ago
    very well made :) for documentation and specific dashboards this has a lot of great uses

    i played with a similar concept back when everyone was starting to 'drill down into big data' on their ipads, and i never came up with a clever way of drilling 'sideways', or allowing people to go between one 'insight' from one deep level and tie it into another without zooming all the way back out and then back in, contextual 'wormholes' (all handmade), or breadcrumbs (messy after enough layers)

    one thing i'd add to the demo is detecting where i'm hovering over while scrolling to scroll into that part (on a mouse), scroll out works

  • tzm 15 hours ago
    I think zooming is effective when it's used in isolation for discrete things. It does add a sense of delight, but there is a functional usefulness of this that I'm trying to wrap my head around.. perhaps a transition effect for an immersive demo, etc.. nice work.
    • tinchox6 14 hours ago
      Thanks! Yeah, immersive demos and dashboards are where it seems to click best.
  • theflyinghorse 13 hours ago
    HA! I Love it! It's a been a while since I felt this sort of joy exploring a new way to navigate
  • drob518 16 hours ago
    Interesting. At one point I pinched my iPad to zoom out of habit and it got very confused. But yea, interesting.
    • tinchox6 14 hours ago
      Ha, noted. Pinch conflicts are a known pain point on touch devices, need to sort that out.
  • christoff12 13 hours ago
    > remains the market leader in that space

    TIL

  • tracker1 16 hours ago
    Would suggest using history-api navigation over the hash based routing.
    • tinchox6 14 hours ago
      Good call, hash routing was the quick path. History API is on the list.
  • eisfresser 15 hours ago
    The Home Assistant showcase looks fabulous.
    • tinchox6 14 hours ago
      Glad you liked it! That one was fun to build.
  • solarkraft 15 hours ago
    I have great respect for people pursuing their special interests with such perseverance - you clearly care about zooming UIs.

    And so do I (just to a lesser extent)! It’s a great way to express hierarchy.

    One thing I encountered is that it becomes all buggy after using the slide-back navigation gesture in iOS Safari. Yet this being natively handles would be a really cool thing to me, like those iOS “close back to thumbnail” gestures you sometimes see when scrolling up/down that I haven’t really seen replicated anywhere else.

    • tinchox6 14 hours ago
      That means a lot, thanks. The iOS back gesture thing is tricky but would be really sweet to pull off.
  • cynicalsecurity 16 hours ago
    Doesn't work correctly in Firefox.

    Feels sluggish, but maybe this could be fixed by reducing the transition time.

    But why? People usually don't notice such transition effects and it doesn't affect user experience in any meaningful positive way. It feels absolutely unnecessary.

    Maybe you could re-use it as a mod for some game engine. This feels appropriate for video games; not for web-sites.

    • solarkraft 15 hours ago
      I have the exactly opposite view, possibly with the same amount of conviction. It feels very necessary to communicate hierarchy and where things are coming from and going. It communicates a lot of important information and continuity. In real life, you don’t have things suddenly appearing and disappearing all the time. That’s not how our brains are conditioned.
    • tinchox6 14 hours ago
      Firefox issues are real and I want to fix them. On the "why", fair to be skeptical, it's not for every UI. But I do think it makes sense when hierarchy needs to feel spatial.
    • jvdvegt 15 hours ago
      Weird, seems to work fine in Firefox on Android.
    • heyethan 5 hours ago
      [dead]
  • kabir_daki 13 hours ago
    "Zooming UIs in 2026: Prezi, impress.js, and why I built something different"
  • syaz2 15 hours ago
    [dead]