JAMES TAMPLIN: Hi, everyone, and welcome back to Ask Firebase.
I'm James Tamplin, a co-founder and product
manager on Firebase.
A fun fact about me is I first started programming
at the age of 12 using a TI-83 Basic in math class.
Needless to say, my math teacher wasn't pleased.
WOMAN: No.
[MUSIC PLAYING]
JAMES TAMPLIN: Our first question comes from mrpan4.
How did you meet Firebase co-founder Andrew Lee?
Andrew and I actually went to high school together.
We've known each other now for about 17 years.
After we both finished university,
Andrew gave me a ring, and we had dinner
at a small Midwestern diner.
And nine years later, we're still
working on making lives easier for developers with Firebase.
This next question comes from Harald Wesinger.
And Harald asks, is there a way to run my Cloud Functions once
every hour?
Great question, Harald.
Unfortunately, currently there isn't.
However, it's our number one most requested feature
for Cloud Functions, which we launched last month.
Stay tuned for more news on our Twitter, Facebook, and YouTube
channels.
Thanks for the question, Harald.
Next question.
TJ asks, can you check the progress on a database request
to know when it's finished?
Well, TJ, we have a couple of ways
you can kind of get at this.
First of all, when you write into the Firebase Realtime
Database.
You can attach an onComplete callback with your set request.
This will let you know when the write is completed to disk.
Alternatively, you can check out our Firebase Realtime Database
profiler that we released just a couple of weeks ago.
This will give you granularity at a path level
into both the latency and the bandwidth usage.
This way, you can get a little bit more insight
into what's going on with the Firebase Realtime Database.
Thanks for the question, TJ, and check the links
in the description for more information.
Next question.
Our next question comes from Saychun Kim.
What's the limit of Firebase projects that can be created?
Well, it depends.
We don't actually publish or document
the limit of projects that can be created,
since that number actually depends on inputs from our spam
and abuse teams.
However, a couple of things to note.
First, billing accounts or paid accounts
don't count towards this limit.
So if you're having trouble, you can upgrade to either
our Flame, which is our $25 a month plan,
or our Blaze pay-as-you-go plan.
Also, if you're still running into trouble,
please reach out to our support team,
and they can help you raise that limit.
Check out that link in the description below.
Next question.
Charles asks, where do you see Firebase in five years?
Well, Charles, in five years' time,
we're still going to be creating great tools that
make developers' lives easier.
Software is playing a bigger and bigger role in society
at large, and we want to help the people creating
that software.
We'll do this by allowing them to focus
on solving their customers' problems by letting them not
focus on low-level infrastructure,
by not making them stitch together
a myriad of growth tools.
While I can't comment on specifics,
I can give you a few general areas
of where we'll be focusing, the first of which
is more deeply integrating with Google Cloud Platform.
This lets developers start with Firebase
and then move seamlessly into Google's public cloud offering.
Second of all is focus on machine learning
and integrations there.
It's no secret that this is a big focus for Google.
With integrations, we can intelligently
provide recommendations to developers about next steps
they can take to grow their app or how they can better
improve their app quality.
It's going to be a great next five years for Firebase,
and we're excited to serve you, our developers, as best we can.
Thanks for the question, Charles.
Our last question comes from Gabe,
who asks, how has the culture of the Firebase team changed
since joining Google?
Well, Gabe, we were 23 people when we joined Google,
and now we're more than 10 times the size.
So things have certainly changed a little bit.
However, I would like to think that we've
changed Google more than we've changed ourself.
Specifically, we've changed Google's processes
towards building developer products,
trying to bring a focus on developers around the globe
rather than just Google engineers.
We've done this through things like one-on-one developer
feedback sessions, through a lot of meetups,
and through introspecting and dog fooding.
By preserving this culture, we'll
try and make developer offerings across Google
better for you, our developers.
So thanks for the question.
That's all we have time for today,
but thanks for all of your questions.
Do keep them coming on Twitter, YouTube Stack Overflow and more
with the hashtag #AskFirebase.
I'm James Tamplin, and we'll see you next time.
Stay tuned.
We love you, Charles.
I'm not sure what I'm saying now.
Yay,
Gabe.