Native Access 2 is here

Still pretty bad. Every time I launch the app, it's "activating products" for 30 seconds, then spends another 30 seconds "loading products" before it finally becomes usable. Even when it's loaded, everything is slow, from switching tabs or views to showing release notes. Poor information density. Product names are truncated despite large amounts of empty horizontal space. And it sits there wasting 20% CPU the entire time it's open, even when it's doing nothing.

The categories are helpful. That's the one new feature I actually like.

What NA1 really needed was an uninstall feature, but instead of that, almost everything just got worse.

By the looks of the comments here - it looks as tho NA v2 is definitely not ready for prime time nor does it (At least at this stage) provide any significant value or reason to move from v1.

My Q: Can I remain on v1 as long as I need to? Or put another way - this thing is not going to be "pushed" to the masses and supplant v1 without my knowledge - is it?

Appreciate any insight on this.

Cheers

VP

What's the point of having a native app if it needs dependencies that require rosetta to be installed.

That's not how a "native app" works for me.

Now the real question:

Is the NTKDaemon package already optimized for M1 and you forgot to update the installer or does it need to be optimized?

I've given this a try, and it is much, much slower than the original NA. I asked a few migration oriented questions a few weeks ago but nobody replied, and I've learned the answer for myself -- NA2 is much slower, sits on "activating licenses" for 3-4 minutes, then "loading products" for 2 minutes, then finally my list of content appears. While I dont use NA all the time, when I do use it this is going to be annoying and I hope it can be fixed ASAP despite the apple M1 (which has been abandoned in favor of the M2, lol) migration issues.

Still no news from the helpline. My NA2 just won't load in my M1 Studio. OS 12.4

I wasnt suggesting NA's sluggishness was an M1 issue**

I typo'ed that, but for some reason the new forum system wont let me edit my own comment. Oh well.

Unfortunately it's still no improvement. Honestly, I don't use most of my NI products anymore since it is such a pain to maintain. Now it's not detecting all my libraries and I have to reinstall them before I can load my project again. No, just no 🤦‍♂️

Ah, gotcha. Well it is indeed plausible that the reason NI built NA2 with Electron (a web app framework, instead of a native app like NA1) was to reduce the amount of platform/architecture-specific code they need to write. However, there are lots of apps built with Electron that are far more complex and have very decent performance (like the one I spend most of my day using — Visual Studio Code). So I think the problem lies with a lack of developer experience/competence rather than the framework.