@robschilder this sounds interesting! Will investigate it today / tomorrow! Thanks.

Okay at least we have an answer that they definitely won't add Supertokens themselves!

Yeaaa.. not sure if they will want to merge a PR that adds ST for them either.

Alright.. and what about just an tRPC example from Supertokens itself? If you look at this other starter: https://github.com/t3-oss/create-t3-turbo, they're using Next-Auth to only authenticate for the Next.js app, not Expo, because they don't have a good example out there. If there won't be a Supertokens example, I think all future startups using this popular setup (or similar cross platform setup) will use Clerk because it's "officially" supporting such a stack. Meanwhile, Supertokens is more capable than Clerk but doesn't have the tech influencers promoting the solution meaning people don't know. Supertokens is incredible powerful for cross-platform apps because it has the header-based auth, it's multi-tenant, has account linking, has all social auth providers, etc.. It will work incredible well with multi-project schemas from Drizzle https://orm.drizzle.team/docs/goodies#multi-project-schema meaning one could have 1 auth backend, 1 database, for many different projects, as far as I understand. Showcasing this through the create-t3-turbo app would show many people the power of Supertokens I guess.

Yeaaaa. That’s true. We need to figure out a way to get them to be more open minded. But based on the comments, I’m not sure they will even add clerk to it.

Hey all, maintainer of t4-app checking in. Would Supertokens be intereted in a collab? We are moving away from Supabase to solve a big pain point for new users setting up the stack. My understanding is that Supertokens is further along, plus it has 2FA support. What do you think? https://github.com/timothymiller/t4-app

hey @.timothymiller sure! Would love to!

Links to reference implementations for React/Next & React Native would help. Of course, any PRs to add Supertokens support into the repo would be approved.

Integration with nextjs: https://supertokens.com/docs/thirdpartyemailpassword/nextjs/about Integration with react native is here: https://supertokens.com/docs/thirdpartyemailpassword/custom-ui/init/frontend Would love to contrubute the PR. Will check out the repo and existing auth in the coming days. But feel free to start and we can add onto it.

Creating a new supabase account per project to stay within the free tier, otherwise $25/month.

ahh right. Okay

Well for having different folders we have the same situation when we are using Capacitor. @nkshah2 knows all about this. But in the scenario of Capacitor we are not using a different SDK because it's both React. So basically they share the 'screens' which are created with Tamagui. So it's unified in that sense, just different folders

hmm. I see.

(also just a side note, I saw you shared the

app-dir

link, but they're still using pages router! 🙂 )

ah oops.

I think a lot of code can be re-used from the Capacitor-Supertokens example. So that's going to easy. On the web side, the new thing here will be the integration with tRPC

> On the web side, the new thing here will be the integration with tRPC Thats not such a big issue as long as the calls to the supertokens API are via http. Applcation APIs can us tRPC.

we are using a different

cookieHandler

with Capacitor indeed too, and there we also use their native storage solution (

capacitor-preferences

)

yea. So something similar

Solito may provide some inspiration here, as it basically provides a single React Native Web (RNW, like Tamagui also uses) component that switches internally based on the platform it’s running on: https://github.com/nandorojo/solito

Hey @.timothymiller So ive spent some time experimenting with Expo and turns out you should be able to use the supertokens-website (have not tested with web-js) SDK on both the native expo side and on the web with expo. Im not too familiar with the t4 setup so if you can give me a quick summary of it that would be great but if your setup is similar to the capacitor project that @robschilder has then you should be able to use the website SDK on both the web and mobile. The downside is that you have to build your own UI ofcourse but you would need to do that for React Native anyway.

@.timothymiller we should be able to figure out the integration by next week, and will make a PR for it!

Hey guys how is this going? I could help out with this if you need help. Maybe improving some UI with Tamagui or testing out recipes on devices

Hey! We have a draft PR ready: https://github.com/timothymiller/t4-app/pull/106. There are still a lot of comments i have added based on my review, so wait for them to be solved (should happen sometime next week)

Going to try out the Supertokens branch now. Would you say it's ready?

Yup. It is.

Amazing!