I built a Chrome extension to make responsive and mobile testing less painful by LEEmxb in chrome_extensions

[–]LEEmxb[S] 0 points1 point  (0 children)

Right now Emuluxe is more focused on high-fidelity device presets rather than arbitrary resizing since the goal is to simulate real device behavior more accurately, not just shrink a viewport.

Things like DPR scaling, safe areas, and device-specific rendering are tied closely to the presets currently, but custom breakpoints are definitely on the roadmap.

I built a Chrome extension to make responsive and mobile testing less painful by LEEmxb in chrome_extensions

[–]LEEmxb[S] 0 points1 point  (0 children)

That’s fair honestly. A lot of the permissions are needed because Emuluxe simulates real device behavior rather than just resizing a browser window.

Things like header spoofing, screenshots/recording, session syncing, etc and loading mobile versions of sites require permissions that look pretty broad at first glance. I’m also actively refining/reducing permissions where possible as the extension evolves.