Share your UX feedback for the developer section!

At the end of this month we’re doing a hackathon to improve the UX of our developer section.

I’m sure y’all have ideas for how the developer experience in the platform could be made more clear, usable, and understandable – please share them here!

Some examples of feedback we’re looking for:

  • I expected to be able to CMD-click this button to open in a new tab, but it wasn’t possible :wink:
  • I don’t understand what this text means
  • I use X feature a lot and wish it was more accessible
  • X layout doesn’t work on my small screen

Looking forward to seeing your ideas!

4 Likes

One example of a quick fix for your hackathon might be:

  • App Settings feature cannot be named or renamed. They are always named “New feature” in the UI.

Some others:

  • All things that look like they should be links (rather than click events) should please be converted into HTML links
  • Have some overview screens for vendors with multiple apps, so we can see analytics, monetisation, and other screens for all our apps rather than having to click click click to find all these.
  • If an app feature can be configured on the command line, rather than in the UI, then make that command line feature. Developers like the command line
  • if app features could be described by an app manifest in JSON or Yaml, rather than setting up in the UI, then build something that can read the manifest and do all the things that the UI configuration can do. This would be a massive productivity enhancement

I think that’s enough for now, but I might edit this with more.

1 Like

Have some overview screens for vendors with multiple apps, so we can see analytics, monetisation, and other screens for all our apps rather than having to click click click to find all these.

:100: I would also like to see a better and way more detailed dashboard for all of our apps at _.monday.com/apps/manage – displaying the most relevant data at a glance in almost “real-time”.

The most recent updates on the app analytics and sales pages are already a great improvement into the right direction.

Prevent the release of a version of an app that’s using monday-code if the code for the version has never been deployed.

Yes, really. I did this today.

Luckily it doesn’t break anything as the previous version continues to be served, but you get a broken version and then have to create a new version, deploy it and then release it to get out of the hole you’ve dug.

This is a small part of another story that I’ll probably post at some point.

It’s absolutely insane that after granting a discount, there’s no record of it in the developer section. This creates so much confusion with users who didn’t understand how to apply the discount / discount expired. Please add a table so we can see which accounts received a discount and which one are expired