Feedback - Komplete Kontrol 3.0

So this may come across as a long read - but I want to be as clear as possible, and perhaps provide some tiny insight to those on this thread, which wasn't meant to be a "HEY WHAT THE F" but more feedback on some issues.

@Matt_NI Really appreciate the willingness to engage and respond - that's a big improvement on interaction with users from NI.

I also think it's fair to separate user experience from user journeys. For those that don't know what a user journey is; it's mainly utilised when desinging software. For example, a user journey might be:

"As a user, I want to delete presets in the Komplete Kontrol browser."

or

"As a user, I want to display either presets, or the plugin with the press of a button."

Using user journey's you can prioritise in development, sometimes into Must have, Nice to have, or Not essetnial. This thinking helps define how software is developed, and I will admit, apps/executables are way different to my experience- software platforms (although I work with a team who code, and I design).

Firstly, I can understand when some things are less important for different development sprints; and where they might appear in subsequent sprints. I hate sprints as a designer, but understand why they're used and for the most part, they work as intended.

I think, where Matt's hit the nail on the head here, is that we're power users on this forum. I might be quite unhappy with some of the omissions forn KK3.0, because User Journey prioritisationn has led to some poor user experience. But as power users, we might use more of what's not implemented as yet, while the average user has a great expreience.

The quesiton I would ask of @Matt_NI is what kind of interaction was had with users at the design stage? Did NI speak to the average user and power users, one of those groups, or not at all? It just feels like some of these things were easy wins to be had.

The reason I say this, is that I understand the need to bring all software, wherever possible under the same tech stack. Uniform browser experience is probbaly the biggest hurdle to developing multiple software lines in tandem, rather than in silos, as teams move from one project to the next.

At the very least, there's a lot that can be learned for an upcoming update to Maschine, where you cannot simply implement the new browser, because to do so would change the excepted norms of workflow and display from every major DAW out there.

Not yet, apparently, but confirmed as planned in the AMA. This is a gamechanger, for me.