From b3de7c9035cab2024b25b2d24308c9d5106959f9 Mon Sep 17 00:00:00 2001 From: wbaumbach Date: Tue, 2 Sep 2025 10:11:10 -0500 Subject: [PATCH] Update README.md --- README.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/README.md b/README.md index 18da1b8..df42488 100644 --- a/README.md +++ b/README.md @@ -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! \ No newline at end of file