You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's designed primarily as a desktop app, and I was thinking I wouldn't mind adding mobile support later... But these days I'm debating whether to block mobile entirely or add a warning.
I'm thinking most people would decide not to do a npm install on their mobile browser if they knew it could potentially download +50MBs of packages (especially if over data).
There's also a memory usage concern:
Android: beta support for Chrome, Chromium-based browsers and Firefox. Depending on your device, large projects may run into memory limitations.
iOS and iPadOS: beta support for Safari since iOS 16.4. Large projects may run into memory limitations because the memory usage for a web page on a mobile device is more constrained. In this case, we recommend switching to a Desktop browser that is less constrained and has more memory.
Activity
privatenumber commentedon Jul 28, 2023
It's designed primarily as a desktop app, and I was thinking I wouldn't mind adding mobile support later... But these days I'm debating whether to block mobile entirely or add a warning.
I'm thinking most people would decide not to do a
npm installon their mobile browser if they knew it could potentially download +50MBs of packages (especially if over data).There's also a memory usage concern:
https://developer.stackblitz.com/platform/webcontainers/browser-support#mobile-browsers
realityzero commentedon Aug 17, 2023
Although mobile view does not make sense for the user base, but it's harmless to show a pop up that signifies
Best experience in landscape modeprivatenumber commentedon Aug 17, 2023
Yes, I plan on adding a warning modal soon.