/final-project

Primary LanguageTypeScript

FolioOne

Description:

Unleash the Power of Seamless Crypto Management - Your All-in-One Hub for Tracking Portfolios and Analyzing Data across Diverse Exchanges!

FolioOne - a solution for consolidating assets from various exchanges into a singular, user-friendly platform. Its core objective is to provide users with a comprehensive financial overview, facilitating in-depth analysis and continuous monitoring of financial changes.

Seamless login with Google, enabling the addition of exchanges (Binance and Kraken for now). FolioOne conducts a thorough portfolio analysis, presenting users with a visually informative pie chart depicting asset allocations. Additionally, prominent assets are individually highlighted, allowing users to navigate effortlessly through their entire portfolio. A live ticker ensures users to be consistently informed of real-time developments in the cryptocurrency market.

Designed to empower users with insightful and up-to-date financial information.

Responsive by nature responsive-screens

Analyze your assets analyze-data

Tech Stack:

TypeScript, React, Next.js, Node.js, NextAuth, Prisma, Redis, Tailwind, SASS

For the development of this application, I selected Next.js, an extension of React, as the overarching framework for both the Frontend and Backend. It's versatile, superior performance, and efficiency in terms of speed and build times. To enhance the application's robustness and minimize errors in production, TypeScript was implemented as a superset for JavaScript, ensuring type safety throughout the development process. Authentication was integrated using NextAuth, a specialized authentication library designed specifically for Next.js, ensuring a secure and streamlined user authentication process. For database interactions, I opted for Primas, a reliable Object-Relational Mapping (ORM) tool, simplifying data retrieval and manipulation. In addressing performance considerations, I implemented advanced caching strategies utilizing Redis to store exchange and asset data. This strategic use of caching not only reduced loading times on the frontend but also contributed to an overall enhanced user experience. In terms of styling, Tailwind and SASS were chosen over the more conventional StyledComponents in my opinion for their perceived advantages in developer experience and codebase readability.