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
I don’t understand what this text means
I use X feature a lot and wish it was more accessible
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.
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.
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
The preview window is very small, basically impossible to develop on a laptop without going into the developer console and hiding some elements. Already mentioned that about a year ago here.
Links should be links, whether in the development window or marketplace.
Single page to view all monetized apps data.
Option to upload one zip for all views. Some apps are the same across all views. The reason is to make the user choose which view is most convenient to use. Currently, a developer will have to upload the same zip file for all views for every new version.
Option to have a dev url and prod url for integrations and automation development. Very easy to push a dev url to production because you forgot to change it.
remove this old “App Notification Webhooks” section from “General - Basic Information” page:
This is left over from when we had separate install/uninstall URLs specified here. In 2022 The “Manage - Webhooks” page was added and the above section was deprecated and we were required to move to the new App Events Webhook.
This appears to now just be a piece of “dead” reminder this moved two years ago - there are probably many devs who have never seen the install and uninstall url fields that were here.
On the flip side, on the “Manage - Webhooks” page - its still called “New” nearly two years later.
These seem like the kind of very low hanging fruit a hackathon can fix
Another simple one I think. Allow us to reorder input and output fields in an integration action/trigger. While it seems trivial, being able to reorder so that various related blocks have the same order makes it easier to troubleshoot if something is missing or incorrect. Plus it soothes OCD.