Erik Wittern

@dan_abramov @vercel @Netlify @Azure @Cloudflare @AWSAmplify @Firebase Here is an example configuration for @Firebase Hosting to serve a statically exported Next.js SPA with multiple HTML entries, including dynamic routes (e.g., /products/[productId]): gist.github.com/ErikWittern/9b…

@Firebase @puf Very cool to see `OR` queries! They allow, for example, to improve prefix string matches to be (slightly less) case-sensitive (cf. stackoverflow.com/a/75877483/102…).

🔥 Release Notes 📝 🕹️ Recent updates for game devs 🚚 App Distro: in-app feedback 🇳🇱 Firestore in The Netherlands 💙 Better error handling in Flutter 🌏 Automate project creation with Terraform 🏵️ Use OR conditions in Firestore queries Watch @puf 👉 goo.gle/3KdKtKd

It's a PWA, so it can be added to home screens and be used like an app. It's also client-side only. Topics are reflected in the URL and additionally persisted to local storage.

I wrote a small HN client, for fun. You can "subscribe to" topics ("React", "TypeScript", "ChatGPT" or similar) and view the most relevant posts & discussions for different time frames (1 day, 7 days etc.) hackerviews.app

@mbleigh I imagine such a feature fits very well with Firestore’s architecture, and is mostly a matter of making information on this level available via SDKs?!

@mbleigh For example, it would make it much easier to implement collaborative forms where in the client one wants to update (re-render) only form inputs whose value just changed.

Separate from query capabilities and relations, what kinds of UI patterns could use easier devx when using Firestore? e.g. pagination, infinite scrolling, "new data click to refresh" What do you wish we did for you but you have to work around instead?

Rewrites, in our case, are done for Firebase hosting. It’s not automatic, but easy enough to maintain.

This is exactly how we build getcouped.com. The experience is great. Our app is highly interactive, so the SPA model fits well, and hosting is cheap. However, we still benefit from build-time-rendered HTML files + JS chunks, allowing e.g. our blog to be SEO-friendly.

@bechtweets @dvassallo Ah, thanks for the explanation.

@erikwittern @dvassallo Yeah, that would be gross revenue.. But not “actual” as 90% goes to creators.

Substack had its most recent valuation at $650M with ~$22M in revenue. $650M put in US treasury bonds at 4% would yield $26M today. In profit.

@dvassallo @bechtweets $10/m with 2M paid subscribers should mean around 240M per year in revenue, no?

@bechtweets Assuming $10/mo per subscriber and a 10% cut:

If you want to rely on URL query parameters in React components in a reactive way, useSyncExternalStore makes it pretty simple when combined with a proxy object. wittern.net/blog/use-url-p…

It's the holiday season. Time to draft wish lists. In this case, for some amazing features that would oh-so-much improve the jolly #firebase services. wittern.net/blog/firebase-…

I wrote about how we combine @Firebase Firestore 🔥 with Zustand in Coup's React app. Our setup allows components to subscribe to updates of individual documents, even though we use a single Firestore query to listen to changes across multiple documents. wittern.net/blog/firestore…

When building an API, how to choose between REST, GraphQL, or RPC frameworks? Certain requirements can really drive the decision. Here is my (current) take: wittern.net/blog/choosing-…

@__xuorig__ Fully agree. The benefit is that cost analysis adds latency, so having to run it only once when “deploying” is a huge improvement over running it on every request.

@erikwittern Yes! I’m going to add a section on that. Combined with allow-listing, my feeling is they do help so that intentionally malicious queries are less of a problem however there is probably still a lot of value in running cost analysis and other safe guards at registration time.

Current thoughts on GraphQL rate limiting & security! xuorig.medium.com/a-guide-to-gra…

@Firebase Very interested in the new `firebase deploy` functionality for Next.js. Does it support server-side rendering (i.e., does it setup a Cloud Function running the Next.js server for that)? Or is it merely about deploying a site previously built statically (using `next export`)?

🥳 Did you catch Firebase announcements in the developer keynote? 🔥 Crashlytics support in Flutter 🔥 App Quality Insights window in Android Studio 🔥 New Extensions 🔥 And more! Watch the Firebase #GoogleIO product keynote to find out more → goo.gle/io22-firebase

@mbleigh - No more Cloud Function cold start performance issues when using (Firestore) gRPC SDKs (cf. issuetracker.google.com/issues/1580146…) - More configuration options for Auth Email Action Links (specifically, configurable expiration times) - Seamless hosting of Next.js apps (cf. Vercel or Netlify)

"Today, Firebase announced __________" What would be most exciting to you to fill in that blank? Joke answers welcome, but curious to hear real ones too.

@mxstbr @GraphCDN This is awesome! If I‘d still be doing research I‘d jump on this.

We've tracked billions of GraphQL requests from many different clients to many different APIs at @GraphCDN. I'm sure there are some interesting insights in there that we could share with the community… Does anybody want to work with us to analyze & visualize that data? 🤔