Join HIFI Labs and work on innovative projects with well known and iconic musicians. Past artist activations include Bruno Mars, Linkin Park, Jisoo / Zayn,Rüfüs Du Sol, Dua Lipa, and Mike Shinoda. We're looking for a Senior Fullstack Engineer passionate about design, user interactions, and privacy.
You'll work with TypeScript, React/Next.js, Firebase and explore new frameworks like Astro. Experience with Styled Components, continuous deployment and devops is a plus. We also play around with React Native / Expo.
Sound like a fit? Email us at pierre at hifilabs dot co
I know multiple people who worked / working at Mullvad and they take their business, security and privacy _very_ seriously. Not surprised to see them shine here.
Join HIFI Labs and work on innovative projects with well known and iconic musicians. Past artist activations include Linkin Park, Jisoo / Zayn,Rüfüs Du Sol, Dua Lipa, and Mike Shinoda. We're looking for a Senior Fullstack Engineer passionate about design, user interactions, and privacy.
You'll work with TypeScript, React/Next.js, Firebase and explore new frameworks like Astro. Experience with Styled Components, continuous deployment and devops
is a plus. We also play around with React Native / Expo.
Sound like a fit? Email us at pierre at hifilabs dot co
Sadly, this is the 3rd time everything is down when we're about to go live.
It's great that pages are still being served - but we are currently blocked by not being able to access our dashboard, configuring / prepping for a launch.
And we are enterprise customers - and I am not finding a way to reach out to customer support since .. the site is down.
I just want to point out to people who are new to Firebase that you can query your Firestore collections.
Also, Firestore Queries are cached by default, so if you try and fetch data that hasn’t changed, you shouldn’t have to pay for that read.
db.collection(‘Payments’).where(‘id’, ‘==’, ‘payment 1’).onSnapshot(console.log) // 1 read, then cached
Whereas specifying a document and then manually get it always counts as a read. Example;
db.collection(‘Payments’).doc(‘payment 1’).get() // always counted as a read
It's funny.
I've had multiple discussions with people who build apps using Firebase and then not being able to scale to 1000 concurrent people without the BE falling apart. I want to tell them that they've done something wrong, but since none of my apps haven't reached those kind of usage levels, I really don't know.
I think Firebase comes with a lot of power, and as long as so plan to scale, design your database model, have proper security rules and cache as much as you can, you can probably host a 1M concurrent users without getting scaling problems. Cost though, ooh yeez. :)