Let’s Build a Svelte/Sapper App. Part 6: In the penultimate instalment of this series we are going to polish the application before going live. Part 6: Last Details
Part 6: In the penultimate instalment of this series we are going to polish the application before going live.
Photo by Limor Zellermayer on Unsplash
Last week we allowed our users to create new game pages when the game they are looking for it is not in the database. This is the penultimate part of this series, so we are going to polish the last details for the web application before going live.
If you want to jump straight to the code you can find it here.
To provide a better user experience we will add two small features.
The search bar will reset when the user goes to the create page, and to avoid navigating away by accident when clicking the search bar, it will be disabled. If the user is filling the data for a new entry and clicks or tabs to the search bar, they would lose all the data filled, which would give a bad experience.
Since the main goal of the web application is for the users to search games, when they click on the search bar, they will navigate to the list and the input will be focused.
Setting up a full Svelte Sapper project. This series will show the whole process from idea to production of a full Sapper project. This introduction explains how to set up the project.
Let’s Build a Svelte/Sapper App - Part 2: Building the list of searched games; that includes the database model, the API endpoint, and the rendering.