Progress Update (Life):
1) Just a quick update, nailed my forensics test (Monday) with a 93%.
2) Nailed my Calc exam (Applications of Derivatives: 92%, Function Analysis: 82%)
3) I have my AP Macroeconomics tomorrow with AP Psych right after that.
4) Next week I have finals for AP Mirco, AP Calc, AP Psych, AP Computer Science A, Forensics, and Langauge Arts.
5) What this means is that progress updates are going to be taking place at irregular intervals until everything settles, so sorry in advance.
Progress Updates (Fintech Platform):
1) I have the connection to MongoDB established and have data being added to the DB from the signup forms. Data is taken from the forms, encrypted, and then sent to the database for storage. At the moment only the password is encrypted but I might change that. This means that I can begin moving to the next thing. At least once I fix a small little bug. Currently, it goes to a test DB and not the DB for this current project. I am going to have to figure out how to change that, but I have studying to do right now.
2) I also got started on building/scoping out what the dashboard should be. I have a simple prototype setup in Miro, but I am going to need to go more in-depth for this storyboarding. Below I will include photos of the Sign Up, login, and Dashboard pages.
How am I going to Handle The Dashboard?
1) Visuals/Page Navigation:
-I am going to set up a revolving component architecture. I have no idea if this is a thing, or not. Or even if it is smart, but here is the thought. There will be a JSX page called dashboard, I will then import all of the page components into JSX file, and then systematically turn them on and off depending on what the user is viewing, and what they want to be doing. These components will then be filled with their own. I am calling the parent components panels, which will be built like normal pages, then imported, and turned on/off when the user navigates. This should make things faster, but I am not sure. If not, I can default back to standard page navigation with the already prebuilt panels.
2) Data:
-I am going to have to do some more research into proper data management and database structures, but the idea is that users will have a plentiful amount of data that they will be able to interact with which should make it easier to make informed decisions.
How am I going to handle user Auth?
1) Persistent Authentication for Navigation
-IDK if that is what it is actually called, but how to make it so that they stay logged in while they navigate the site (until they close the tab). I have been reading about these things called JSON web tokens. It will allow me to cache a security code that will allow this to take place
2) Future Authentication Methods:
-I want to use the login with Google, Meta, epic, LinkedIn, etc. But this will require that I do more research. For the moment I will just stick with the basics, and add on as I progress.
3) Encryption:
-At the moment I am just encrypting passwords (I only collect Passwords, UserName, and Emails), but I will naturally encrypt all sensitive data. But the question is if I encrypt all (Usernames, emails, etc), or just the sensitive stuff? I will have to do further research on proper data collection methods.
Conclusion
Thats all for now, you can look at the photos below if you are interested, otherwise that's me signing off. Bye!

Comments
Post a Comment