A few months after go live, production users start complaining that they randomly lose their session in a mobile app.

The conclusion from your testers is that users are logging out of a reactive web application in their desktop browsers, and 5 minutes later they lose the mobile session.

"IMPOSSIBLE!" - you say - "Logging out from the browser cannot possibly terminate the mobile session 5 minutes later, that's absurd and unheard of"

So you try to investigate it yourself and, sure enough, the tester was right. Logging out from the desktop browser indeed terminates not only the mobile session, but every other session of the user. Oh, you also find out that this is documented and deliberate: "When the end user logs out of an application, all sessions are terminated".

You investigate further, and begin to realize that it's impossible to preserve the mobile session after the user has logged out from a browser. It's also impossible for the user to use multiple browsers on different devices, or even multiple browsers on the same device, because any logout action would terminate all sessions in all browsers. This is unexpected behavior that contradicts how the web works.

You reconvene with your testers to brainstorm workarounds, but you're not taken seriously: "Surely this very expensive platform and market leader can support an application running on two browsers simultaneously!" All you can do is wish it did...

If this scenario has happened to you on any project, please like this idea and share with others. Together we can change how the Logout works, and enable this very basic feature which is having two independent sessions on distinct devices.