So your original idea was correct.

i.e., this is correct:

userId // managed by our app
stFacebook // userId in thirdparty_users where third_party_id is "facebook"
stGoogle // and so on...
... // extra fields

awesome, I also just want to paginate via our own users table due to the extra fields

if ever I need the email on supertokens' tables, I can just always do a join anyway

Yea.. Also if you are directly paginating on your user's table, then you would also need to add userIds generated from emailpassword login into your table

yes, so I can reference the users from email/password 👌

and I think that's good segue to my next question, can't seem to find anything about the user changing emails

how would we go about that 🤔

do I do write operations directly on the

emailpassword_users

table and call email verification methods from the node sdk?

and probably delete the old "email" on the

emailverification_verified_emails

table, idk just spitting quick ideas on how to get to that

that feature doesn't exist yet 😦 So there are two things: - if a user uses social login and changes their email there and logs in again: then the email will be updated by us automatically. - if a user is using email password login: we don't have a way to update the email, but you can simple just change the email field in the

emailpassword_users

table.

and yes, you would also need to delete the userId (that we generate) from the

emailverification_verified_emails

table

This would mean that the user will have to verify their email again.. if you don't want them to do that, then you can add to the

emailverification_verified_emails

to add their new email as well.

aight, that's pretty easy to do so no issues there and I think it's good practice to verify the new email, unless there's more? xD

> I think it's good practice to verify the new email Yup it is..

also, cookies is a must here right?

yes. cookies is a must

And that's cause it's the best thing to do in terms of security.

how do native mobile apps deal with this, can't seem to find any sdk and the server can't set it either since it's not a browser that's running 🤔

native mobile apps have cookie management. We have SDKs for ios, android, react-native and flutter (though they need to be updated to work the the latest core version...)

oh, just found it, man I keep getting lost in the navigation here haha

yeaaa.. it is a little complicated. How can we improve the navigation?

ALso, the mobile SDKs will not work with the latest core and node SDKs. They need to be updated, and that's why we don't talk about them upfront in the docs..

well tbh, since you mentioned this, the current makes sense

but I'd like to see an option to just get down to the API references

yea.. but it's still complex (clearly)

take for example vue's docs https://v3.vuejs.org/

> but I'd like to see an option to just get down to the API references Cool. Can add it to the main docs, and put a LARGE banner saying this is not the first thing to see ideally hahaha

maybe just replace the "docs" with Recipes while having a dedicated "API Reference" link

hmmmm interesting. We can keep docs and api reference links separate.. using the term "recipe" upfront is confusing since no one really knows what that means