An under-development NextJS web application that gives the user a snapshot of the day, personalized to their preferences. Authentication through Auth0.
This app is not available for public sign-ups (mostly due to very limited free API calls available) and is mostly supposed to be a proof of concept at the moment. If you would like to see it in action, please use these test credentials to log in and play around a bit. The user preferences section of the website is under development at the moment.
Twitter API update, Apr 20, 2023: Twitter's API v1 is deprecated, and their new API v2 does not yet have an endpoint for Trends. Implementing the trends functionality in snapshot is therefore not being considered anymore in the short-term. This functionality may be implemented using another social media platform, but that is a future enhancement and not a present concern.
- Next.js
- TailwindCSS
- Framer Motion
- Node.js
- Firebase Cloud Firestore
- Auth0
A Pub/Sub Firebase Cloud Function fetches news from the Pexels API every 30 minutes and stores the data in a Firestore database collection. The app fetches the items document from the photos collection of that Firestore database whenever the logged-in user goes to the / route of the app. The JSON is parsed, and then the image is fetched through its URL.
A Pub/Sub Firebase Cloud Function fetches news from the News API every 30 minutes and stores the data in a Firestore database collection. The app fetches the items document from the news collection of that Firestore database whenever the logged-in user goes to the / route of the app.
Because of the limits of free APIs/free tiers of those APIs. When we consider testing (both in localhost and in production builds) and a number of separate users, those API calls are going to add up, whenever any user reloads to the index route. One possible workaround is storing a bunch of data in the user's browser with their session, but I did not want to do that. Using a scheduled function means that calls to external APIs are done only so long as they are absolutely required (in this case, every 30 minutes for updating of data). Read calls to Firestore are much cheaper than calls to the API themselves, at least in my experience. Obviously, this does not matter if the app is only used as a hobby sometimes. But developing it from the intention of it going to public use and production means that such decisions should be made.
Coming Soon