Udemy

Free Svelte and Firebase Course: Connect a Catalogue to User Favorites

A catalogue becomes more interesting when it remembers what each visitor has selected. In this free Svelte and Firebase course, Guillaume Duhan uses a Pokedex example to connect a frontend interface with authentication, shared application state and stored favorites. The project gives JavaScript learners a concrete reason to work with components and remote data together.

Original navy, white and lime 3D catalogue of geometric item cards with favorites stars and search results connected to a cloud database, titled Free Svelte and Firebase Course, W Coursya branding and Guillaume Duhan credit, without people or franchise characters.
Free learning access

Listed as Free on Udemy when checked on 7 November 2026. No coupon or subscription trial is required for the listed lessons. Enrollment needs a Udemy account; availability can change.

About this course

A catalogue becomes more interesting when it remembers what each visitor has selected. In this free Svelte and Firebase course, Guillaume Duhan uses a Pokedex example to connect a frontend interface with authentication, shared application state and stored favorites. The project gives JavaScript learners a concrete reason to work with components and remote data together.

The English-language curriculum contains fourteen videos in one section, totaling one hour, fifty-eight minutes and fifty-one seconds. It begins with Svelte and Routify setup, moves through Firebase configuration and sign-in, and builds toward profile pages and autocomplete. The lesson sequence develops one application incrementally, rather than presenting unrelated demonstrations of individual features.

JavaScript basics are required. The course is labeled Beginner, but its pace is better suited to someone who can already follow functions, objects and browser interactions. Its April 2021 update also matters: this is an older project workflow, so use current documentation alongside the recording when choosing package versions or adapting syntax.

Official course Svelte.js & Firebase: Pokedex edition
Created by Guillaume Duhan
Platform Udemy
Language English
Level Beginner
Listed duration 118 minutes; 14 lectures across 1 sections
Completion terms Not included with a new free enrollment

What you’ll learn

Trace how authentication, a user document and a favorites list fit together. Explore reusable Svelte components, communication between components, shared stores, Firestore data access and an autocomplete interface, while keeping local UI state distinct from durable database records.

Skills you’ll gain

  • Component responsibility design
  • Svelte event communication
  • Shared state concepts
  • User document modeling
  • Favorites data flow
  • Autocomplete interface planning

Start with a catalogue and an identity

The opening lessons establish a Svelte project with Routify and configure Firebase. The instructor describes a supplied JSON dataset for the Pokedex example, allowing the application to begin with existing records rather than requiring a separate data-collection project. One downloadable resource is listed. Its contents and licensing are not established by this overview, and the example does not grant general permission to redistribute franchise artwork or data.

Authentication then becomes visible in the navigation bar. The authored lesson descriptions connect Google sign-in with login and logout controls, giving the interface a different state when a visitor is signed in. This is a useful place to distinguish identity from permissions: knowing which account is present does not automatically settle which records that account should be allowed to read or modify.

Make components cooperate

The component lessons break interface elements into reusable pieces, including a menu and a button. Events provide a way for those pieces to communicate. A menu action, for example, may need to notify the containing view so that the application can respond. This helps explain why a reusable component should expose a clear purpose instead of containing every responsibility of the page.

Trace favorites through three layers

The Firestore user-document lesson prepares for favorites associated with an individual user. Subsequent lessons introduce stores for shared user and catalogue data, retrieve records from the database and connect the favorites feature to a button in a list item. Following this sequence reveals three different responsibilities: retrieving data, making it available to components and recording a user-specific change.

A Svelte store and a Firestore document are not interchangeable. A store helps components share reactive state inside the running application; it does not, by itself, guarantee persistence after a reload or across devices. Firestore provides remote storage. When studying the favorites feature, identify which action updates the interface immediately and which operation is responsible for saving the selection.

Show the state of the application

The later lessons add loading indicators, list items and labels, then refine the catalogue and user profile pages. These details make data access easier to understand because the interface can show that a request is in progress and display the resulting record consistently. The autocomplete lesson rounds out the project by looking up catalogue entries by name and presenting matching results.

Separate interface behavior from data permissions

Firebase reduces the amount of infrastructure you need to manage, but serverless does not remove access-control responsibilities. Firebase’s current guidance pairs Authentication with Firestore Security Rules for mobile and web clients. Client-side navigation guards and hidden buttons are interface behavior, not a substitute for enforcing permissions on stored data. Treat the recorded project as a learning example, not a verified security configuration for public use.

The Svelte ecosystem has also evolved. Current documentation distinguishes newer APIs from legacy features and recommends incremental migration of older code. That does not make every older example unusable, nor does it guarantee that its dependencies will work unchanged. Compare the recording’s component and event patterns with the documentation for the versions you actually choose.

Map your own catalogue example

For an independent exercise, sketch a catalogue of three fictional desk accessories using your own labels and simple geometric thumbnails. Give two imaginary users different favorite selections. Draw what belongs in a shared catalogue record, what belongs in a user’s saved preferences and what only needs to exist in the current interface. Then add a failed-save state and decide what the page should tell the learner.

This exercise is a suggestion, not a supplied assessment or a test already run. The instructor mentions a course repository and notes that it may evolve, but its files have not been reviewed here. The confirmed learning scope is the listed video project and its public descriptions. No guarantee is made about a complete production application, current repository compatibility or professional certification.

Course viewing is free under the current offer. Firebase usage is a separate matter: its Spark and Blaze plans have different capabilities, quotas and billing arrangements. Review the relevant product terms before using a cloud project. The value of this course is the visible connection between components, identity and stored favorites, which you can investigate further without assuming unlimited free infrastructure.

Enroll Now ↗

Related courses for your next step

Frequently asked questions

Is this a first programming course?

No. JavaScript basics are required. It introduces a Svelte and Firebase project for learners who can already follow basic code.

Does signing in automatically protect all database records?

No. Authentication identifies a user; Firestore Security Rules and an appropriate permission model are also needed for mobile and web client access.

Are Firebase services included without limits?

No. Free lesson access is separate from Firebase plan capabilities, quotas and possible charges. Review current terms for the products you use.

Share this course

Questions & discussion

Share a useful question or correction. Comments appear after moderation. Please avoid personal or sensitive information.

Add to the discussion

Your email address will not be published. Required fields are marked *