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
At the moment the playground is using a single breakpoint (default is 1024) to handle line-length, collapsibility (although that is going to change, see #14) as a simplistic way to handle “responsive”.
However, we’ve discussed having different components for mobile (e.g. sheets) so there’s the overarching issue of defining what mobile is, especially as the lines can be blurry nowadays.
Although generally not recommended, it’s one of these challenges for which it’s kinda difficult to ignore user-agent sniffing, especially as solutions that provide views are already available for React and our use case is a lot more complex than checking for a screen size…
Of course the biggest challenge is trying to design a good abstraction or something simple enough that we don’t have to keep track of new hardware in order to modify things specifically for it.
Will share some thoughts later but in the meantime, feedbacks and thoughts obviously welcome as it’s not an uncommon issue and some people will have already tackled that.
The text was updated successfully, but these errors were encountered:
At the moment the playground is using a single breakpoint (default is
1024
) to handle line-length, collapsibility (although that is going to change, see #14) as a simplistic way to handle “responsive”.However, we’ve discussed having different components for mobile (e.g. sheets) so there’s the overarching issue of defining what mobile is, especially as the lines can be blurry nowadays.
Although generally not recommended, it’s one of these challenges for which it’s kinda difficult to ignore user-agent sniffing, especially as solutions that provide views are already available for React and our use case is a lot more complex than checking for a screen size…
But I’m guessing we will perhaps have to refine that even further with media queries and device features/capabilities.
Of course the biggest challenge is trying to design a good abstraction or something simple enough that we don’t have to keep track of new hardware in order to modify things specifically for it.
Will share some thoughts later but in the meantime, feedbacks and thoughts obviously welcome as it’s not an uncommon issue and some people will have already tackled that.
The text was updated successfully, but these errors were encountered: