tinchox6

You can use driver none to avoid transitions. And I’m working on reduce motion

I turn of scroll events except on home assistant. You can enable or disable depending on your needs

Thank you!!

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.

Thanks! Both the depth indicator and the zoomable affordance are things I'm actively working on. Glad the spatial navigation idea resonates.

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.

Good call, hash routing was the quick path. History API is on the list.

Ha, noted. Pinch conflicts are a known pain point on touch devices, need to sort that out.

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.

Fair point. No visual cue for what's zoomable is a real gap. Thinking about how to handle that without cluttering the UI.

That means a lot, thanks. The iOS back gesture thing is tricky but would be really sweet to pull off.

Glad you liked it! That one was fun to build.

Thanks! Yeah, immersive demos and dashboards are where it seems to click best.

Thanks! The a11y angle is something I want to tackle properly. Noted the bugs too, the car one is a known issue.

Appreciate it! Breadcrumbs and back navigation are definitely on my radar.

Thanks! Speed was a big focus, glad it comes through. Your app looks really cool btw.

Thanks! Ive tried using HA API to get all the information and then parse it and render using this UI, but it was just an experiment. I dindt try using custom cards

Hey! I made Zumly. 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.

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

Still rough edges ahead. Would love to hear what you think about the interaction model and if the API makes sense.

Landing page: https://zumerlab.github.io/zumly

All isues fixed https://github.com/zumerlab/snapdom/releases/tag/v0.9.2

If interested I solved almost all issues you pointed out (speedy and accuracy).

https://github.com/zumerlab/snapdom/issues/3

I'm working on enabling a special full mode for those who don't mind the final size:

https://github.com/zumerlab/snapdom/issues/1

No problem! May you open an issue on the repo?

I tested it on Chrome, Firefox and Safari

Thank you for the suggestion!

Sincerely, I don't know if snapdom would work on a browser extension. I've never tested it on this scenery

Its a bit out of scope right now, but I thing it would be possible using some external libraries such as jsPDF or svg2pdf.js

It is pretty the same idea. There are many good solutions like dom-to-imge-more: the battle tested html2canvas, dom-to-image, modern-screenshot, etc. SnapDom is focused on avoiding long-taks whenever is possible because was designed to a zoomble UI engine that needs the capture doesnt affect the transition. But this is the first public version and there many things to adjust.

It requires user intervention and doesn't work for me.

Yes they are so good. But in my case I need to work only on the client side

Not tested yet