Thoughts Uncategorised UX

DAW music software authorization affecting creative flow

With every virtual instrument and effects going the authorization-software route, the creative process is burdened by software updates, patches and oh-surprise download updates… Internet connection required. 😟

Now before considering “oh a cool plugin”, do I really want to jump through all the hoops to have that extra piece of code running in the background.

There’s more. They default check-mark to sharing computer-specs and activity back to their servers. They are effectively pushing the security burden on the users instead of themselves.

Overall it’s a pretty aggravating user experience. Every platform has their own steps, which doesn’t even allow for a convention to ease effort. I hope that software providers shift their security model in a user-friendly format in the future.


Here are the steps when one of my software updates require an entirely new download.

  1. Download a new software version, from a web page.
  2. Unzip file
  3. Select install
  4. Accept terms
  5. Wait for internet connection verification
  6. Find credentials
  7. Type in credentials
  8. Find serial number
  9. Enter serial number
  10. Select download instrument / effect
  11. Boot up music software (DAW)
  12. Find plugins
  13. Route them to activate them

Authorization software on desktop
Collecting authorization software.. for my software.
More waiting.
Yet another step.
Almost there you would think.

Grieving code repository ideas

Some code never see the light they deserved in order to shine. Some code could be beautiful and comes out lazily written. Here are two ideas of platforms that could give more attention to these two very different conclusions.


GitHub, but instead it’s a cemetery repository for good code that never ended up being used. Developers and designers can leave condolences and eulogies. Help with the grievance process of wasting those precious hours of work.


GitHub, but instead it’s entirely anonymous and code is up to roasting. Where ugly code is ripped apart and optimized. Tears will flow. Phoenix will rise. Developers will be roasted.

Dirty pages

It’s OK to have chip grease in books. Also fine are rain marks, writing scribbles, crooked highlight and folds. As long as you eventually read the book, that’s what matters most. Just make sure it’s yours.