Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated:
1
00:00:01,400 --> 00:00:09,110
In this section, we learned all about creating forms, as well as being able to create user sessions
2
00:00:09,350 --> 00:00:15,580
and authenticating users with signing in with email and password, as well as signing it with Google.
3
00:00:16,100 --> 00:00:20,510
And we also had our sign up page where we're able to create a new user.
4
00:00:21,440 --> 00:00:27,710
Now, if you noticed, there were two places that we had to remember or store user information.
5
00:00:28,130 --> 00:00:30,740
The first one was Firebase, right.
6
00:00:31,310 --> 00:00:37,640
We needed to remember a user so that when they come back one day, maybe tomorrow or maybe a year from
7
00:00:37,640 --> 00:00:39,490
now, we have their information.
8
00:00:40,010 --> 00:00:48,680
So a backend database like we used in Firebase is a way for us to remember that information of the user.
9
00:00:48,920 --> 00:00:51,530
So initially we stored that information there.
10
00:00:52,100 --> 00:00:59,720
But once we have it in the backend, we now need to get access to it on the front end because on the
11
00:00:59,720 --> 00:01:03,390
front end, we also have to remember that information.
12
00:01:03,680 --> 00:01:05,630
So when a user signs up.
13
00:01:06,600 --> 00:01:08,500
And they click sign up.
14
00:01:09,030 --> 00:01:12,330
Well, we're going to store that information in our firebase.
15
00:01:13,480 --> 00:01:20,410
However, when a user comes back and lets say signs in with Google or signs up with email and password,
16
00:01:20,890 --> 00:01:26,200
we check our firebase data and say, hey, does this user exist?
17
00:01:26,410 --> 00:01:35,310
And if they do or if they sign in with Google, I want you to store that state of the user in our app.
18
00:01:35,320 --> 00:01:43,600
Remember that information in our app so that as the user starts to move through our e commerce website,
19
00:01:44,080 --> 00:01:47,790
we have that information so that they can check how they can update their card.
20
00:01:48,460 --> 00:01:54,070
So by the end of this section, I hope you understand the importance of remembering a user where something
21
00:01:54,070 --> 00:02:01,300
like a back end and then requesting that information from the back end so that you can store it as state
22
00:02:01,540 --> 00:02:09,330
on the front end and be able to use it to allow the user to have a proper shopping experience.
23
00:02:10,300 --> 00:02:13,960
We have a long way to go, so let's keep going and I'll see you in the next section.
2567
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.
Afrikaans
Akan
Albanian
Amharic
Armenian
Azerbaijani
Basque
Belarusian
Bemba
Bengali
Bihari
Bosnian
Breton
Bulgarian
Cambodian
Catalan
Cebuano
Cherokee
Chichewa
Chinese (Simplified)
Chinese (Traditional)
Corsican
Croatian
Czech
Danish
Dutch
Esperanto
Estonian
Faroese
Finnish
Galician
Georgian
German
Greek
Guarani
Haitian Creole
Hausa
Hawaiian
Hebrew
Hmong
Hungarian
Icelandic
Irish
Italian
Japanese
Javanese
Kazakh
Kinyarwanda
Kirundi
Kongo
Korean
Krio (Sierra Leone)
Kurdish
Kyrgyz
Laothian
Latin
Latvian
Lithuanian
Luganda
Luo
Luxembourgish
Macedonian
Malagasy
Maltese
Maori
Mauritian Creole
Moldavian
Mongolian
Myanmar (Burmese)
Montenegrin
Nepali
Norwegian
Pashto
Persian
Polish
Portuguese (Brazil)
Portuguese (Portugal)
Quechua
Romanian
Romansh
Russian
Samoan
Scots Gaelic
Serbian
Sesotho
Setswana
Seychellois Creole
Shona
Sindhi
Slovak
Slovenian
Somali
Spanish
Swedish
Tajik
Tamil
Thai
Tigrinya
Tonga
Turkish
Turkmen
Ukrainian
Uzbek
Vietnamese
Welsh
Wolof