Designing for Different Devices (Viewport Size, Touch/Hover, etc.)

I’ll give you another example where this is currently not fully exploited and a little tricky - Categories page - on desktop leave as is but maybe turn it into a Latest page on mobile by hiding the Categories panel and just leave the Topic List - since only having the Categories view and no Topic List (on mobile) imho sucks (as a home page).

But then on mobile this wouldn’t be a “Categories” page anymore (despite the route name) :thinking:

This is now exacerbated by the fact that the force mobile home page theme component doesn’t work any more because you can’t identify the device during init.

I think therefore that the discovery routes may need some kind of rethink for interoperability and suitability for the prevailing device.

1 Like