Device page wireframe design proposal #113
Replies: 2 comments 12 replies
Device pageThis thread focuses on the device page, which is the page users see when browsing the Device Database. In the example design, the viewer is not signed in. Purpose of the pageThe device page is primarily about understanding and discovery. It should help users quickly answer: At the same time, the Device Database depends on community contributions, so I made the edit action the primary call to action on this page to encourage participation. Structure and contentAt the top of the page, there is a summary section that highlights the most important information at a glance. The main body of the page shows the contributed device information. In addition to that, the design also includes: These are not part of the core contributed data. The idea is that we only show these sections once a device has enough contributed information to make them meaningful. The buyer’s guide is meant to surface highlights around privacy, choice, and sustainability, rather than acting as a traditional shopping guide. Basic info vs all infoI explored two content states for the device page: Basic infoThis represents the initial state of a device entry. In this example, no category has been assigned yet, so category-specific information is not shown. All infoThis represents a fully enriched device entry. A category has been assigned, in this case Light, which unlocks additional, category-specific specifications. |
Device edit pageThis thread focuses on the device edit page, which is shown when someone wants to contribute to a device. In the example design, the contributor is signed in. Purpose of the pageThe edit page is focused on contribution. It should make it clear what information can be added. Structure and contentThe edit page mirrors the same basic info vs all info concept as the device page. Basic infoRepresents the initial contribution state. Only general fields are shown when a category has not (automatically) been assigned. All infoOnce a category is assigned, additional category-specific fields become available, in this example for the Light category. |


Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi everyone 👋
As part of the roadmap, I’ve been working on initial designs for the Device Database UI and I’d like to get early concept feedback from contributors, especially designers and frontend developers.
This work is scoped for a first launch and is meant to check whether the direction fits the Device Database vision and goals before going deeper into details or implementation. To provide some guardrails what we want to aim for, we have made this document.
To keep feedback focused, I’ve split this discussion into two threads, one for the device page and one for the edit page. Each thread includes context, assumptions, and specific things I’m unsure about.
Screenshots are included in each thread, and I’ll also add a Figma link for those who want to explore the designs in more detail.
Please share your feedback
General feedback, concerns, and early reactions are all very welcome.
Some questions I have:
• Does it fits the overall Device Database vision?
• Does the edit action works well as the primary call to action?
• Are my assumptions around “known” data correct?
• Does the information structure feels clear, scalable, and implementable?
• Are there any concerns from a frontend or UX perspective?
All reactions