Hi, Grant.
Actually, that's news to me. Sure, I've played around with AppImages, RoxApps, self-extracting scripts, in fact all manner of portable formats over the last couple of years.....but this particular way of doing things, I came up with last year when I was helping a lovely old guy over at BleepingComputer.com with a 'portable'-Firefox that he wanted to be able to move from one 'puter to another.
I started on these portables after Fred published the portable-Firefox he'd cobbled together, except with his you enter the browser directory to click on a script. Well, this old boy wasn't too computer-savvy, but a sweet old guy for all that; very polite, helpful to a fault, and ever so grateful that somebody was going out of their way to help him, so.....I figured it might make it easier for him if I sym-linked the launch script out one level, and re-named it to make it more obvious! Which is what I did; and following success with getting the 'clones' working in portable format, too, I decided to stick with it. All my 'portable' packages have this 'external' LAUNCH button.
Remembering back to my own early days with Puppy, and mindful of the fact that the best way to grow and to attract new blood to the community is to make things as easy-to-use as possible, this is why I build so many portable packages now.....in addition to, of course, making them as easy-to-operate as I can.
-----------------------------------------------------------
Chromium-based browsers have a command line 'switch', --silent-launch, which lets you start the browser at boot time without actually showing; any time you click to run it thereafter, it's as near as dammit instantaneous.....because it is in fact already running. But this doesn't seem to work unless you have the browser installed in full, standard layout; I'd hazard a guess that the locations it looks in have to be 'in the $PATH'.....and the portables are anything
but standard.
Mike.
Brave's GUI. Probably violates copyright laws. 
So get it while you can. 
