firebase-js-sdk VS Tailwind CSS

// public/firebase-messaging-sw.js // Give the service worker access to Firebase Messaging. // Note that you can only use Firebase Messaging here. Other Firebase libraries are not available in the service worker. importScripts('https://www.gstatic.com/firebasejs/8.10.1/firebase-app.js'); importScripts('https://www.gstatic.com/firebasejs/8.10.1/firebase-messaging.js'); // Initialize the Firebase app in the service worker by passing in your app's Firebase config object. // https://firebase.google.com/docs/web/setup#config-object firebase.initializeApp({ apiKey: 'api-key', authDomain: 'project-id.firebaseapp.com', databaseURL: 'https://project-id.firebaseio.com', projectId: 'project-id', storageBucket: 'project-id.appspot.com', messagingSenderId: 'sender-id', appId: 'app-id', measurementId: 'G-measurement-id', }); // Retrieve an instance of Firebase Messaging so that it can handle background messages. const messaging = firebase.messaging();

// Import the functions you need from the SDKs you need import { initializeApp } from "firebase/app"; import { getAuth } from "firebase/auth"; // TODO: Add SDKs for Firebase products that you want to use // https://firebase.google.com/docs/web/setup#available-libraries // Your web app's Firebase configuration const firebaseConfig = { apiKey: "AIzaSyDs5ConzFDM2yGvweN-sZdAPFAlowyCDhE", authDomain: "reactmoviepp.firebaseapp.com", projectId: "reactmoviepp", storageBucket: "reactmoviepp.appspot.com", messagingSenderId: "719848561957", appId: "1:719848561957:web:254facecfb591921474ecc", }; // Initialize Firebase const app = initializeApp(firebaseConfig); export const auth = getAuth(app);

Before You Begin 🎯 Before you start, there are a few prerequisites you need to take care of: **Add Firebase to Your Project**: If you haven’t done so already, you need to add Firebase to your project. You can follow the steps in this [link](https://firebase.google.com/docs/web/setup) to get started 🎉. **Upgrade to the Blaze Plan**: The JustPass Firebase extension requires the Blaze (pay as you go) plan. If you haven’t upgraded your project yet, you should do so now. **Install or Update the Firebase CLI**: The Firebase CLI allows you to install and manage Firebase extensions from the command line. Make sure you have the latest version installed. **Enable Cloud Storage**: The JustPass Firebase extension requires Cloud Storage to be enabled for your project. You can check if it’s enabled from this [link](https://console.cloud.google.com/apis/api/firestore.googleapis.com/overview). **Find Your Firebase Project ID or Alias**: You will need either your Firebase project ID or a previously configured project alias to install the extension. You can run the appropriate command from your local app directory to find these. **Get Your JustPass Keys**: Go to the JustPass.me Dashboard and copy the following keys. You will need them to configure the extension: — JUSTPASSME_ORGANIZATION_NAME — JUSTPASSME_ID — JUSTPASSME_API_SECRET Step 1: Installing the Extension Once you have taken care of the prerequisites, you can proceed to install the JustPass Firebase extension. Here’s how you do it: **Set up an Empty Extensions Manifest**: Run the following command to set up an empty Extensions manifest: firebase ext:dev:init 2. **Install the Extension**: Run the following command to install the JustPass Firebase extension: firebase ext:install justpassme/firebase-extension --project=Replace \\ with your actual Firebase project ID.` Step 2: Deploying the Extension ✅ After you have installed the JustPass Firebase extension, you can deploy it to your Firebase project by running the following command: firebase deploy — only extensions` You have now successfully added passkeys authentication to your Firebase project using the JustPass Firebase plugin 🎉 ✅. Make sure to keep it safe, as you’ll need it for granting access to users. If you have any questions or run into any issues, feel free to reach out to [email protected] for assistance. Happy coding! 💪

**Add Firebase to Your Project**: If you haven’t done so already, you need to add Firebase to your project. You can follow the steps in this [link](https://firebase.google.com/docs/web/setup) to get started 🎉.

// Import the functions you need from the SDKs you need import { initializeApp, getApp, getApps } from "firebase/app"; import { getAnalytics } from "firebase/analytics"; import { getFirestore, gitFireStore } from "firebase/firestore"; import { getStorage } from "firebase/storage"; // TODO: Add SDKs for Firebase products that you want to use // https://firebase.google.com/docs/web/setup#available-libraries // Your web app's Firebase configuration // For Firebase JS SDK v7.20.0 and later, measurementId is optional const firebaseConfig = { apiKey: process.env.NEXT_PUBLIC_FIREBASE_API_KEY, authDomain: "twitter-v1-6a0d8.firebaseapp.com", projectId: "twitter-v1-6a0d8", storageBucket: "twitter-v1-6a0d8.appspot.com", messagingSenderId: "334598974996", appId: "1:334598974996:web:a16f62518c1c5af1044101", measurementId: "G-Y5F3Q3QG2X", }; // Initialize Firebase const app = !getApps().length ? initializeApp(firebaseConfig) : getApp(); const db = getFirestore(); const storage = getStorage(); const analytics = getAnalytics(app); export { app, db, storage };

Auth persistence Issue Firebase SDK - https://github.com/firebase/firebase-js-sdk/issues/6050

Connecting to firebase is as simple as copying and pasting the credentials (that Firebase gives you) into your frontend app. Here is a link to the documentation. If you need help, simply make a more detailed post about the issues you are running into.

First, you need to make sure that you have a working Tailwind CSS project…

Tailwind CSS

With better CSS approaches like TailwindCSS and Vanilla Extract (which we're heavily using) it's much easier to maintain the UI and make sure it doesn't change unexpectedly. No more conflicting CSS classes, much less CSS specificity issues and much less CSS code in general.

This app was built with Svelte Kit, Tailwind CSS, and many other technologies. For a full rundown, please visit the GitHub repository

Unlike Tailwind, which has over 77,000 stars on GitHub, Mojo CSS has about 200 stars on GitHub. But the Mojo CSS documentation is fairly good and you can find most of the information you’ll need there.

JavaScript React Flowbite Tailwind Firebase - Auth, Database, and Hosting Vite

- Performance is a feature.

Another common interpretation of brutalism is aesthetic, reacting to overly complicated user interfaces by creating simpler, more direct ones. Tailwind CSS (https://tailwindcss.com), one of today's most popular CSS libraries, promotes this approach in its component examples. There's also a neat library I've seen recently called "Neobrutalism Components" for React that I like (https://neobrutalism-components.vercel.app), providing components with a similar look and feel to Gumroad. This might more accurately be called 'Neo-Brutalism,' as noted in the comments.

A more engineering-centric interpretation of Brutalism focuses on form, structure, and efficiency, drawing significantly from brutalist architecture principles. Apart from the user interface itself, most mobile, desktop, and web applications are extremely bloated and often perform worse than sites from 10 years ago did. While one HTML file might be "less brutalist" than the original HN site, it is substantially more brutalist than any HN mobile app in existence, and offers nearly identical functionality.

A broader interpretation of brutalism, which could be termed 'Meta-Brutalism,' is embodied in the overall experience on this site through UX flows. Yes, in the strictest sense, the original HN site is more Brutalist in many ways, but it only shows 30 articles at a time and does not function as a PWA. For this site, the experience of reading 10 stories is arguably less brutalist, but for quickly browsing through several pages and skimming articles (which is how I read HN) it is a lot faster, and in my opinion, more Brutalist.

My primary inspiration was addressing software and tool bloat in UIs rather than strictly adhering to every principle set forth by David Bryant Copeland. I don't find it convincing that this site "isn't brutalist" compared to really any other experience apart from the Main HN site, and I would argue the overall experience is more brutalist in its performance and scrolling behavior.

As a side note: I generally don't like Brutalist architecture that much although I believe it is unfairly maligned. I visited the Salk Institute once and enjoyed it though (https://www.archdaily.com/61288/ad-classics-salk-institute-l...).

- Staff Software Engineer ($275k/yr): https://tailwindcss.com/careers/staff-software-engineer

We're small, independent, and profitable, with a team of just 6 people doing millions in revenue, and growing sustainably every year. You'd work directly with the founders on open-source software used by millions of people.

If you like the idea of working on a small team that cares about craft and isn't trying to achieve VC scale, I think this is a pretty awesome place to do your best work.

Instead of Booststrap, I used Tailwind CSS as the CSS library.

Tailwind CSS: A utility-first CSS framework for rapidly building custom designs.