SUMIT CHANDEL: Hi everyone, and welcome to this brand new
episode of "#AskFirebase."
I'm Sumit Chandel, and I'm originally from Montreal.
But despite having lived in the US for about 12 years now,
I still get confused by Fahrenheit all the time.
And here's our guest, Ryan Vernon.
Hey, Ryan.
Fun fact about Ryan is--
RYAN VERNON: I like to drink tea that's
been sitting out so long, that it grows something
on top of it.
SUMIT CHANDEL: That sounds a little dangerous.
RYAN VERNON: It's kombucha.
SUMIT CHANDEL: Kombucha?
Oh, yeah.
RYAN VERNON: Yeah, I make my own.
SUMIT CHANDEL: Oh, really?
RYAN VERNON: Yeah.
SUMIT CHANDEL: Oh, that's super cool.
Maybe I can try some of that.
Did you bring some for me?
RYAN VERNON: No, but tomorrow, maybe, I could.
SUMIT CHANDEL: Sweet.
All right, well, here's to trying
Ryan's home-brewed kombucha.
Now, you work in the UX and interaction Design Team,
is that right?
RYAN VERNON: Yes.
SUMIT CHANDEL: Cool, nice.
Well, we've got a few questions here that we can answer.
Ryan, are you up to helping me answer them?
RYAN VERNON: Answer them?
I'll try my best.
SUMIT CHANDEL: I think we can do it.
[LAUGHS] Let's do it.
So our first question comes from Odili.
And Odili asks, "What are some good examples
of custom metrics with Firebase performance
monitoring for the web?"
RYAN VERNON: We have a lot of great out-of-the-box metrics
like first contentful paint, the time to interaction,
and all those things are awesome.
And if you want to get really into it,
you can make your own custom traces,
which will allow you to do so much more.
You could see how long a user takes
to load a certain level, for example, or load a playlist,
and figure out is loading a long list hurting my churn?
That's a lot of things that give you
a good insight into your user behavior.
SUMIT CHANDEL: That sounds pretty powerful.
Is it difficult to use, or how would I set up a custom trace?
RYAN VERNON: It's pretty easy.
You have to go into your code and instrument
a start point and a stop point, and it'll
measure everything in between.
It's kind of like when you drive through those speed traps
the police have.
SUMIT CHANDEL: Except this sounds a lot more fun
than getting caught in a police trap.
[LAUGHS]
RYAN VERNON: It's fun until you get caught.
SUMIT CHANDEL: [LAUGHS] All right, OK, cool.
Hey!
SPEAKER: Next question!
RYAN VERNON: Dave asks, is MFA still coming as suggested here?
SUMIT CHANDEL: All right, well thank you
for the question, Dave, and thanks for keeping us honest.
So MFA, for those who aren't aware,
stands for multi-factor authentication.
And the link that Dave posted there is a link to the Google
I/O presentation that Marc and Ying gave
on some of the updates on authentication within Firebase.
So the answer to his question is that, yes,
multi-factor authentication support is still coming,
and we're still working on it.
For any developers who are actually interested in testing
it out in an early access program and providing some
feedback for it, you can sign up for that, actually,
at g.co/firebasealpha.
There's also a link just down below in the description
for to click on.
So if you're interested in checking this out,
you can just enter that and then give us some feedback.
But yes, it is some something we're working on,
so please stay tuned for it.
Thanks for the question, Dave.
RYAN VERNON: [SNIFFS] Do you smell that?
SUMIT CHANDEL: [SNIFFS] [SIGHS] I love the smell
of fresh-out-of-the-oven next question.
RYAN VERNON: The next question is from Pankaj about Firestore.
"Can you please explain pricing of using
Firestore with examples?
Is there a free tier and is there a pay-as-you-go model?"
SUMIT CHANDEL: Great question, Pankaj.
And actually, yes, there is both a free tier and a pay-as-you-go
model when using Firestore.
So the free tier, you know, is basically
when you're just getting started out with Firestore.
And let's say you're starting your development,
and you to test it out and see how it works.
And for the free tier, there are some pretty generous limits
for what's available there.
So to store data, there's a 1 gigabyte total limit there.
For document writes, deletes, and reads,
20,000 writes and deletes per day and 50,000 reads per day.
So those are pretty high limits.
So if you're just getting started out,
you can kind of play around with Firestore and see if it works.
Once you're satisfied-- let's say your app is growing--
that's when you might go to the paid tier model.
What's good to know about that, though,
is that the paid tier model, the pay-as-you-go model,
also includes the free tier model.
Those limits that I just mentioned,
if you're only operating within those limits and not going
beyond them, your bill will still be zero,
even if you're on a pay-as-you-go model.
If you surpass them, and if your app is growing,
hopefully, that means that you're also
getting some money out of it.
And at that point is kind of when there's a paid tier model
and you pay above those limits.
So that's kind of how it works.
For more details about, specifically,
how the pricing works, there are some links below to check out
on the Firestore pay-as-you-go model and to learn more about
that.
But that's kind of how both those tiers work,
the free tier and the paid tier.
So thanks for your question, Pankaj.
All right, and that's all the time we have today
for questions on this episode of "#AskFirebase."
Thanks, again, to Ryan for coming onto today's episode
and helping us answer all these questions,
and thank you all for submitting them.
If you have more questions, if you'd
like to ask us and have answered in the next episode,
let us know.
Post it in the YouTube comments, on Twitter, Stack Overflow,
whatever platform you like, and just
make sure to include that #AskFirebase.
And hopefully, we can get to it on the next episode.
Until then, we'll see later, and please
remember to like and subscribe.
All right, thank you.
RYAN VERNON: [SNIFFS] [SIGHS]