In the last couple of videos we have been working nonstop on the header.
And I think that we're now at a point where there's really nothing else that we can do with it right
now.
So we're going to pause working on the matter for just a little bit.
Unfortunately we are going to come right back to it very shortly.
But let's talk about another feature that we're going to start to work on.
That's going to eventually lead us back to working on the header.
I'm going to open up a diagram that we've looked at previously.
Remember we looked at this to get a better sense of what we are working on and what we're going to be
planning to work on in the future as well.
Now I've added a couple of extra steps on this diagram and as a reminder everything green is related
to the back end of our application.
Everything in blue is related to the client side of the app.
So we just finished up the client set up and the authentication system on client We're now going to
move on to handling billing within our application.
So building on our client and billing on the server.
When I say billing I'm talking about accepting credit cards or accepting payments from our users and
then somehow enabling additional features inside of our application based on the fact that they have
paid us money.
So as a reminder of why we are accepting money let's go back to our markets really quick.
OK.
So this mock up right here.
So remember we've got the head at the top.
I had said that we were going to have some button that says something like add credits on it a user
if they click this will be presented with some message or some windows something some form where they
can start to enter in their credit card details when they give us money if they give us like say five
dollars.
We will give them five credits in return every credit inside of our application allows our users to
send out one individual mass e-mail survey.
So if a user signed up for our application and they created these two surveys that we show up on the
mark on our mark mark up right here excuse me that means that they must have used at least two credits
one credit to send out this campaign another credit credit to send out this one.
So clearly we want to be able to accept credit cards.
We want to be able to accept payments.
We want to accept money.
And whenever a user sends us some money we want to somehow update their account and say OK here is the
new number of credits you have.
And then of course at some point in the future when we actually put together all this campaign stuff
like actually sending out surveys we should make sure that a user has a sufficient number of credits
and make sure that we subtract 1 credit for every survey that they send out.
Now the world of billing is really its own topic and we can really without a doubt make a course about
billing alone.
And we could probably talk for days about how billing works and how it works in web applications.
So we're going take a pause right now when we come back in the next section we're going to do a quick
discussion about billing and side of web applications.
We're going to talk about some general rules of thumb that we're definitely in a follow very closely
within this course and Emily Mulally come back after that and start to integrate billing into our application
specifically on the front end.
So let's take a quick pause.
Come back in the next section and start really diving into how we work with accepting credit cards from
users.