I definitely get the annoyance. The problem is, a mobile version of this is a very different thing, to the point that it's essentially a completely new app. Displaying a broken interface just to display something isn't helpful, even if I realise it makes it harder on the Show HN audience - I generally check HN on my phone too!
For what it's worth, I'm not looking at user-agents or anything: it's cutting off at the point where the display starts looking awful. If you zoom out enough (plausible on a tablet, less so on a phone), then it will display as intended.
It's looking at the width, so that some fixed-width elements don't run into each other and wreck the display - if you expand the window a little it should work as expected.
For what it's worth, I'm also running Firefox on MacOS, so I'd expect that to work given the right window size.
This looks lovely, well done! Regarding the cut off, why not use:
min-width: 1199px;
overflow-x: scroll;
on the <body> element, and change the 100vw on the 'css-obv7rs' element to 100%? (And you may need some more tinkering, but you get the general idea.)
You can still put a mobile popup there ("this has been designed for a desktop"), but mobile users can pan around if they wish - degraded experience, but can use if they're desperate.
That's a good idea - hard to believe that I didn't think of "min-width" considering the amount of other CSS that had to go into this, I wish I'd come up with it myself 12 hours ago...
I've just updated it, everyone should be getting an updated version now (clearly there's interest!). Thanks for the thought!
For other mobile users, you can use Firefox+ublock to zap the overlay(Addon>ublock>element zapper> need to zap the entire screen a few times(not just the dialog) until icons are individually zap-able >swipe right twice to exit zap mode). It is designed for desktop and there is some overlap in charts, but looks usable, on first look nonetheless.
Whether or not I can zoom out enough on my phone depends on your website. If you set the mobile screen width in your meta tag to 1280 or something, instead of ‘device-width’, then I’ll be able to use the site fine, as long as I’m willing to zoom and pan a bit.
It's not just an annoyance, it makes your site literally unusable on a mobile device. What if I urgently need to access some details of my account and don't have laptop access. If I check "load desktop site" then load the site and let me deal with the broken UI.
This is a ridiculous "feature" and the fact that you are defending something like this is a major turn off on ever using this product. What other hill would you be "willing to die on" for some seemingly miniscule yet exceptionally annoying feature.
It's open source, not a product. You're coming off as entitled, and he can die on whatever hill he wants to die on. You can fork it, and even submit a PR that would do something like click a button to continue anyways (on a smaller resolution).
Maybe rude but not entitled. Nobody here cares about the product specifically, but it’s shooting itself in the foot and saying it’s a feature; that doesn’t sit well with many.
They don't mean literally nobody cares about the product, just that this conversation isn't necessarily related directly to the product but more about design in general. My original point is just that it's a design that locks people into using the app with a very specific medium and it locks people out of accessing it on another medium with no details about why.
That's a pattern that most people would agree they don't like and my comment is meant to be a criticism of that.
> That's their problem, no one else's.
It was posted in a public forum for discussion, is it really wrong to critique or praise the product in this setting?
I appreciate rapind's point so I won't comment along those lines, but I think it's worth explicitly saying that the UI doesn't work within a certain screen width: it would display nonsensically, and I'd rather display an explanation to someone new to it (and the link to the GitHub ReadMe, which hopefully helps a little) rather than complete garbage. I definitely don't consider this a "feature" - I think it's just the least bad option, given the lack of a proper mobile view. It's also the case that the idea of "urgent access" doesn't work so well without data syncing - I generally wouldn't expect people to copy the export file to their mobile manually, in which case this won't actually have the data from another device.
It's probably true that a summary of features or something would be more helpful for those coming across it anew. In this case though, this is mostly for my own benefit, and it's explicitly out of scope to make money off this: I'd prefer to spend time on additional features for users (ie. me!), rather than implementing something like a product showcase or proper mobile view. Hopefully it's useful/interesting enough when it can be viewed properly, that it's worth coming back to.
For what it's worth, I'm not looking at user-agents or anything: it's cutting off at the point where the display starts looking awful. If you zoom out enough (plausible on a tablet, less so on a phone), then it will display as intended.