So today we're going to be talking about doing a tech stack tour.
This is for owners access only.
So if you're an owner of your platform, which all of you are, if you're watching
this, we're going to walk through what are some of the things that make this
really, really different than just, like I said, subscribing to some type of SaaS
product where you sign in and you pay your subscription and you get to use the
tool, you guys actually own an app that you have full access to, you have access
to the server, you have access to the database, you have access to all your
user data, and I'm going to show you all of that today so you can see how you can
access that.
We don't overwhelm you when you first sign on and start to use the platform.
We don't want to overwhelm you with all this techie stuff, but I do want to show
you where it is.
At least you know where it is.
And then if you ever have anyone who's either technical on your team, or even if
you're working with other developers in the future, you would at least know where
to go to give them access to it to make the changes and get the data out.
So let's dive into that.
One way that we've thought about this is that we are software developers, we've
built software, but we have running this entire software on your own tech stack.
So again, your own servers, your own database, your own image hosting, all that
stuff is being hosted for you.
You guys actually own that.
And so I'm going to show you how all of that is set up.
But what we're doing is we're essentially like publishing that software.
And then every time there's an update, we publish the new update to your apps for
you.
But after 12 months, if you guys decide like you're happy with the app as is, you
kind of could take that and just, you know, keep using that indefinitely without
having to pay anything extra, which is kind of cool.
So that's really different.
Of course, if you want updates and things like that, you can just stay in contract
with us.
But we're giving you guys the full control over that to make that decision.
Because a lot of these platforms, once you get all your users in, all your
content, you're kind of sucked in for life.
And so you can never leave because you feel like you're going to lose all this
stuff if you leave.
We just gave you that control, which we feel like you deserve as app owners.
So this is a little diagram.
It's overly simplified, but it should show a little bit of how this is set up.
And the blue box here, we have an app that we've created software, right?
We've taken that, we have various ways that we've created that code and we take
that code and we push it to a Google Firebase project.
And so this is where your whole app is kind of contained.
All the, most of the user data, the content, any of the posts, the comments,
the chat, the DMs, all of it is kind of contained here on a server, on a
database.
And then from there, we're, we deploy your app to an iOS into the app store, the
Apple app store.
We deploy it to Google play for Android, and then you also get a web app.
So that's, what's happening.
And every time we push an update, this is kind of how it flows.
So we start with the, the code up here, it pushes it down into your project.
And so what's above this line is, is ours.
And what's below the line is yours.
So you just continuing to get like updates for your own tech stack, and we're kind
of maintaining and managing all of this behind the scenes as if we were you, but
just know that you guys own everything that's, that's kind of below this line is
yours and you, and it's everything you need to kind of keep the app going.
So hopefully that makes sense.
And we'll definitely take some questions on this.
If you're just jumping in, I see David jumped in.
We're just talking about tech stack and kind of how the tech stack is built for
tribe.
And we're talking about the difference between like how we own some piece of it
and how you guys own your own tech stack.
And just want to make sure you guys have a, like some working knowledge of kind of
how it's set up so that if you ever wanted to work with another developer, if you
want to work with someone technical on your team, or you want to go in yourself and
get your hands dirty, you can do that as well in the techie stuff.
So I'm going to do a quick tour here.
I see David was on here.
I think Cheryl was on here as well.
So I'm going to use last year's single as our test group.
And when you sign into Firebase, I'll get you the links and everything here.
This is kind of what the dashboard looks like.
And this is essentially your app.
This is, you can see daily active users.
You can see retention, all kinds of cool stats.
What versions are running.
There's all types of like crash reports.
There's a lot of data in here.
And here you can see like the three apps I talked about.
Like there's your, the purple one here is your iOS app.
You've got, sorry, the Android app, the iOS, and then your web app.
They're kind of all set three sitting up here.
And so I'll jump into the database.
You see like Firestore databases here.
And again, I'm not going to go into all of this, but it is one, you just have a
concept that when you pull up your phone and you jump into your app and you load
posts in a particular group, the app is just reading what's coming out of this
database.
And there are, you know, thousands and thousands of documents and
database entries in here.
So you don't have to.
actually click into this and do anything with it,
but I just wanted to show you guys
that you have access to all of this.
So broadcasts, for example, are your posts in your group.
We have direct messages, we have chat messages
when people comment on a particular post,
you can see everything that's to do with that post,
the replies, all that's kind of contained in here.
When you're in your dashboard and you go to the content tab
and you take content and you push it to the app,
it's actually writing it into this tribe content database,
all your videos, your live streams,
all that's coming in here.
So just showing you that like a copy of everything is here.
If you ever were to like take your app or your data,
say go, you have it already, you don't need to export it,
you don't have to do anything to get the data,
it's already here, it's already owned by you from day one
and it doesn't go anywhere.
So if whatever reason you needed it or you wanted it,
it's kind of already under your own ownership
and you already have access to it here.
There's a few things in here,
I don't recommend necessarily anyone going in and doing this,
we do this all for you,
but I just wanted to show you when we change things
like your logo and there's various things
like your support email, who to email for support,
that's all happening in here
and we're able to just edit this, make a change,
hit save and it publishes and pushes that out
to all three of those apps for you.
So we can change things like copy changes.
So instead of calling the community, community,
you wanna call them groups
or you wanna call them something else, you can do that.
Same thing, so there's a bunch of little like variables here
that we can change and it makes your app customized
to how you wanna use it.
Again, pretty easy to break some of this,
I don't feel like you'd have to go in here
and this is not a tutorial on how to change things,
it's a tutorial on where things are
so that if you ever needed to do this,
I just wanna show that you guys are in control
and of course this is fully managed by our team,
by Avidy and the product people here
so you don't have to worry about that.
One cool thing here is the analytics dashboard,
this is probably looks a lot more familiar
if you've ever used Google Analytics,
if you ever had a website with Google Analytics,
we essentially have a version of Google Analytics
running for your entire app.
So you can pick a date range,
we could look at the last 28 days
and you can see kind of day to day
like what the group activity has been in here,
the bottom here is your daily users,
like how many unique people each day
were showing up to your app,
across all three of those platforms,
iOS, Android and the web
and then the week access, the seven days
is typically what we look at to kind of track users
because I think a week is a good cadence
of someone's like regular schedule
so if people are mostly working on the weekends
or doing this in the evenings
to work through your content,
a week tends to capture everybody
and then of course you can see the 30 day there.
So when we email this, we have a much simplified version,
we're pulling all the data out of here,
that's what our reports do is they pull all that data
and they kind of simplify it and summarize it
and that's what we send to you
but this is the same data essentially,
just if you wanted to go a level deeper,
you can see all of that here.
So you can see average engagement time for example,
like how long people are hanging out on your app,
is that going up or down?
This is looking very healthy
that people are spending a ton of time,
they're not just opening it for like a minute
and then shutting it off,
there's people that maybe are going in
and watching full sessions, trainings, things like that.
So I won't go through like all of these,
there's an insane amount of data like I said
and you can see like we're in the,
one really cool thing under analytics
is there's something called real time analytics
which is always one of my favorite screens to look at
but you can see like right now,
like who is using the last year single app,
you can see that these are,
this is, you can kind of zoom in here,
I think, sorry, that's,
but you can zoom in on that
and kind of see like where in the country
are people actually using the app right this second
and it's kind of in the last 30 minutes here,
so pretty cool and kind of what's going on
sort of right at this,
like in the last 30 minutes for the app.
So I think that's always cool.
If you ever had like an actual office
and everybody I think is remote,
if you had an office and you want to put this on a TV,
we did this for one of our clients
where you just had this whole graph like on a TV
and every time you walked by it was like,
you could see like who's using the app right now
or who's using the platform, pretty cool.
Yeah, I'll just show you storage,
there's also, this is kind of where all your people's images
when they post an image, they post a video,
it all gets stored in here
and that is pretty much, I think if you go to build,
there's like hosting.
So recently we have moved to actually using Firebase
as the host to simplify it even more.
and further for you.
So when we push an update to your web app,
it actually gets hosted here as well inside of Firebase.
Previously, we were using a different way
to host that that was not under your ownership.
So we've kind of moved that as well.
In the last couple of weeks, we've moved that under here.
And so where you manage your domain name, things like that,
is all under the hosting.
So I think that's everything.
I'm just going to skim this really quick.
There's a lot of other things, as you can imagine here.
Performance, Crashlytics, this is
what our team is using to get crash reports.
So I know you guys spend a lot of time telling us about bugs,
and you saw this thing.
And that's very, very useful, because that's more
from a user experience bug.
But sometimes, they're just coding things that are failing.
And so the app is pretty smart.
It actually reports on the user's behalf.
When there's error messages, it will post things here
into this Crashlytics report.
And we can go in and see specific data
on what is not working, what's been fixed.
So we can have little patches and updates
to make sure that it's an even faster experience.
Just one thing on the crash, if you ever do click into it,
do not panic.
It does say crash-free users.
Oh, wait, does that mean only 26 people, 27% of people
are crash-free and not having any issues?
That sounds horrible.
Their definition of a crash is just
like an image is either blank, or it's not actually
like the whole app is crashed, and you have to reopen it
or anything like that.
So we do want to get those down, because it helps
us identify real problems.
But some of these things are typically like an image.
Like a user hasn't set their profile picture yet,
so it shows a gray image, because they
don't have an image yet.
So we're working on little things
to make sure people upload their profile picture, for example.
So you can check in.
But I just wanted to show that to you,
because when our team goes through and looks at crash
reports and some of the performance,
we're looking at it like there's an insane amount of data.
This is just the last seven days that we're
looking at right here.
But we can click way into every single instance of every error
that's ever happened in the app.
And so we're monitoring this regularly
to look and see what are small things we
can do to improve the experience.
And it just generally makes the app a lot faster and more
reliable.
So that's all in there.
And I think that's probably what we'll cover.
This is your app.
Like I said, if you want to, if you go to the Project Overview
and Users and Permissions, I've got David.
We just added you this morning to this.
You probably get an invite for it.
But you can go up here as the owner,
and you can invite anyone on your team
to have access to this if you want.
It is tied to a Google account.
So this is our team that's all added.
But anyway, that's where you would go to add stuff.
So anyway, that was the quick tour of Firebase.
And that's kind of where the hub of your app is.
And I'll just show this as well, because you may,
this is one of the benefits.
If you're ever to take this over, the project cost,
like we covered the project cost for you guys, of course.
But if you go back to June, for example, it's very affordable.
Everything you're seeing here is very cheap to keep going.
And it's built this way so that if you ever
scaled your group from, say, 1,500 people to 15,000 people,
the cost is going to be pretty cheap.
You're not paying it per user cost.
Like, you're paying for actual usage here.
So of course, we just cover this.
And this is all attached to our own cards.
And we cover this for you guys as part of your 12 months.
But I just wanted to show that to you if you ever do take it
and just want to lock the app in and use it
as is after the 12 months.
I mean, it's like cheap, basically
the same price as hosting a website
to keep all of those apps running.
Pretty cool.
And of course, it goes up.
Our biggest clients are probably spending a few hundred dollars
if they have 15,000, 20,000 people.
The range is pretty small.
So it's not too expensive.
But anyway, that's all here.
OK, so that's that.
I'll show you as well your tech stack.
We talked a little bit about it.
We call it client apps, so your web, Android, iOS app.
That's the apps that your clients use.
The server and database we talked about, Firebase,
is where you access all your data.
And of course, you've got Tribe CMS
is where you can load in video content and live stream
content like that as well.
We'll drop this link as well.
It's console.firebase.google.
If you just search for Firebase in Google,
it'll be the first thing that shows up.
And I will show you this really cool tool as well.
This jumping around the database in particular
is quite painful.
Just searching and finding things
is sometimes a little difficult.
There's this really cool app called FireFoo,
which is basically like a simplified version.
And it kind of puts it in like a table kind of view.
So you can kind of see things like you
would in like a spreadsheet when you're looking at the data.
And so a lot easier to find things.
things, it's pretty powerful to, you know, to find, to use that.
So that's what our, that's what I use personally when we're working on the
counts to jump in and make quick changes for you guys are a great tool.
So that's good.