wbaumbach/tattletires
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
wbaumbach
2025-09-02 10:11:10 -05:00
parent 5eac9b466e
commit b3de7c9035
1 changed files with 0 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@@ -42,7 +42,3 @@ There were a couple roadblocks that I encountered when developing TattleTires.
2. How to manage users, authentication, and roles
I had never personally created an app that required users and user authentication so I was unsure on how to implement this within TattleTires. I knew that there are a lot of security risks when it comes to authentication, especially with store user login details. Even though I didn't expect this app to ever have any real users I wanted to make sure that I was building it under the assumption that there could be millions. I looked into create my own system and how to properly store login details, but I decided that because this app was meant to be used as a way to learn react native I didn't want to spend tons of time also learning how to implement custom authentication systems. I then looked into what was already out there in terms of user management systems and I found Clerk which offers a free tier that I thought would be perfect for my needs. I used their api to create my own login page, and used their metadata feature to specify the users role. This ended up being a perfect solution for my POC.
3. Routing in Expo
It took me quite a bit to understand how routing in expo works, and to be perfectly honest I still wouldn't consider myself an expert on it!