Integration widgets: display an image and a clickable list in the same widget?

Hi @Tlse-vins, thanks for the message and the mockup, it’s very clear!

I prefer to answer you frankly: I’m not going to evolve the widgets in that direction, and I think the problem isn’t the limit you’re encountering, but what you’re trying to fit into a widget.

A widget is not a product

A dashboard widget is a piece of information that you read at a glance, and possibly a button you press: today’s solar production, the status of the vacuum cleaner, the next movie releases. What you’re building is something else: a search, a list of results, a map, detailed cards, routes, a toggle between two views. It’s a complete application, and you’re twisting the widget vocabulary to make it fit into a dashboard card.

The limits you’re encountering (a single focal component, no link on a status, the List / Map button as a workaround) aren’t gaps to fill. They’re there exactly for that: to prevent a widget from becoming a page. If I allow image + card-list, the next request will be chart + card-list, then tabs, then filters, and we’ll have recreated an interface engine in the dashboard.

It won’t work on mobile

On a phone, the dashboard is a single column about 350px wide. Your card becomes a fixed image of 350 × 200px, without zoom, with numbered dots of a few pixels. Below come the list, then the buttons, then the search form: several scrolling screens in the middle of the dashboard, between the living room temperature and the shutters. Even if I lifted the limit, the result would be unusable where Gladys is most consulted.

What belongs in a widget

The “dashboard” version of your integration, in my opinion, is a single card-list: the nearest craftsmen for a trade and a radius chosen in the widget settings, with the detail panel (address, phone, “View the card”, “Route”). No search, no toggle. That, the current vocabulary does very well, and it remains readable on a phone.

And for the rest

The search tool with its map corresponds to custom integration screens (this topic), which are not yet specified. That’s where your use case will fit, not in the dashboard.

For the map itself, the planned track in the spec is a map component: the integration sends points, Gladys draws the map, with the theme, dark mode, and zoom.

A question by the way: what does the “Sponsored” badge on your mockup correspond to?