1P app starts with Firefox

@kaitlyn Thanks for inputs. In my case too starting firefox brings up the big app login window, which is pretty annoying. Anyway the logged in state stays for a short few minutes (the default being 10 minutes), so let the user chose when to login.

It is a pretty sweet feature that browser extension shares the logged in state with the app. But was not that the case in version 7 previously also though? The advantage I would say in version 7 was that if you need to login to the browser extension, you just login to the browser extension and the app communicates in the background with its app, where as now, to login to browser it brings up the app interface to login. I think if the previous workflow could be re-implemented, allowing one to login only when they want, to either app or browser extension separately while letting them share the logged in states in the background that would be pretty sweet actually!

1P_Ben Great to know that this feature is being debated. I think, a helper app could always run in the background to monitor and communicate login states between browser and app. If the app is not active, it only maintains the browser's logged in state, when available it communicates their states between each other, that is, initiating login or logout from wither app or browser extension gets transmitted to the other through the helper, unlike how the app seems to be now working as the communicator. The goal should be to let user have power to decide to run the app or the browser extension independently when they want, while letting those communicate with each other, if they both happen to be running.

App: 8.2.2-10.Nightly
Browser Extension: Firefox , 2.0.5