We still have to build the desktop app with a build type, but that can be desktopextension and we can achieve the app specific differences using the overrides object and pre-initialisation as you've started to already.

We could rename the build type to desktop to make it less confusing why the app claims to be the desktop extension.

Thanks for the clarification, it all make sense now. I will rename it now

❤️

This was introduced due to the init browser changes on the submodule... I believe that we can set all of those to false (as the app should not fall into the path that will use this dependency).

(to set it to false, you need to add this to the override file and set all those values to false, and then re-run the lavamoat policies generation)

Thanks @cryptotavares, now I know how to override policies 🙏
Fixed

Nice one 😎