Unsolved questions

[ ] How would all the cases in the page be covered?
[ ] We would ideally like to cover the above without them having to deploy many instances of SuperTokens.. how is that possible?
[ ] Is there any missing case that is also seen irl? For example, like people have specific subdomains per client, do they have specific paths per client (instead of subdomains), like example.com/user1/.. and example.com/user2/..?
[ ] Do people use APIs specific to a logged in user? I don't think so.. but maybe?
[ ] Wouldn't we ideally want the login page to be completely handled by us? As opposed to them creating a website just for the login page to use our react component..

Rishabh's thoughts on setting config

It takes a lot of cognitive effort to set the configs up for the various use cases. The only one that's easy is when everything is example.com, and even then it's hard to know all the behaviours and to make sure things are according to what you like.
On the frontend, dealing with websiteDomain and the onSuccessRedirectURL is very confusing.. it's not clear what will happen when.
Perhaps no need to have path somewhere and url somehwere.. make all of it URLs?