Robust
Well-known member
I don't see any issues with an XF SSO solution. But I also don't see it happening.This could be improved with a Single Sign On solution but also this can/will bring many problems with it again.
It would make logging into sites easier, but if you use a password manager, it'd only really save you a few clicks and speed up registration. It'd provide some neat features though (like checking if a user is licensed without a license key, which I don't ask for myself, slows down the flow).
But for the effort, the gains are probably not worth it. In all honesty, time spent on developer sites will probably be minimal especially if better tools within XF are made to do automatic updating (with foreign developer sites), support and bug reporting (i.e. all the reasons you go on a developer site). I think a hyperlink to a page that doesn't require login for support & bug reporting suffices.
For automatic updating: some kind of XF-defined standard for developer sites to implement would be very useful. Something that can poll for version changes and support automatic updating. This would encourage forum owners to stay updated much more, without the hassle of going to dev sites.
Minimising time on dev sites via means like this to make it a better UX for customers, while not creating inconveniences for the developer, is probably the best way to solve the issue presented in the OP imo.