Evan asked that more research and data is gathered before we should work on any upgrades or improvements to the mobile experience. For good reason! We need to make sure that there is a problem or need in the first place
The difference is the first one it is more about why did you use mobile and the second one is about what the goal of browsing the package site (not specifically why mobile)
I would personally like to see the package website to work better on narrow screens. I have a related problem even with a regular width desktop window, where code examples are frequently invisibly truncated. (Scroll bars not being shown by default is part of the problem, but it would be great if the examples were fully visible anyway.)
This is the second time I was thoroughly confused by the elm/http documentation because of the apparently missing decodeMetadata argument.