Dev Talks: Why We Transformed Native Access

When we discussed this feature, this was precisely what we had a chat about.

We'd definitely want an opt-in/opt-out feature, so users can decide whether they want this feature by default. We'd also need to be more granular in how we discern our product types, so that with install all, we'd leverage the user to go through a few more steps (if opted in to this feature) when trying to install all their products with flexibility in where what goes all in one go. How we do this is up in the air, but it was a watercooler feature discussion at the time anyway, not a super in depth one.

However, the other side of the coin is giving users plenty tools, but getting them used to a feature with more complexity to it: how much do we simplify the process if they DO want more control, without compromising the ability to dictate where they install all their products? We might have to sacrifice ease of use in the short term and get users familiar with how they can organize their installs, a feature they'll learn to master later.

And how would they organize their products? This varies per user. I'm the type to organize my directory as granularly as possible so I have quick glance access to things, but other users bundle them all in one place... So many different user journeys we'd need to unify under one flow.

So while it's an interesting feature, there's moving parts we need to consider, and likely need to test on some users once we have a POC ready.

Hey, Sorry to get back so late. It was before my time but if I recall correctly, Rosetta is needed for the Daemon Helper tool, which assists in keeping your session active and granting permissions. If we can/need to remove it is unclear, and unfortunately my devs are now out on holiday so I'm afraid I can't answer that part. Sorry!

Hey! Thanks for the feature requests:

• Moving products is on our features list for things we would love to get implemented this year, and while we have ux/ui designs ready for it, a lot of other things are unfortunately ahead of this at the moment, but thanks for reaffirming that this is a feature our users want.
• Yes! This is something that we could sneak in at some point, but again we haven't fully decided on it yet. People have a ton of products, and some that come part of a bundle that hasn't fit their usecase yet. There's a few things we need to consider before we can do this though.
• Yeah, great example of a current pain we'll navigate through the course of this year. iZotope has amazing products and great deals for all kinds of users, but we'll need to make sure that once either type of product is in NA2 that it becomes a little easier to manage. We'll be looking at this as part of our iZotope integration work this year. Thank you for highlighting this.
• This I believe links in to what we're hoping to release next. Currently, as I described in another post regarding start up times, we activate products on every startup. This is not necessary, as we can just remember the previous activation state the products were in. It still means you'll need to activate online, but I believe we could leverage this activation state offline afterwards. Offline in and of itself is a behemoth to tackle though, so we'll keep taking a look into how we can iteratively roll it out.