I don't know much about databases, I've been asking a few questions about them lately to get a better understanding but I'm still a bit confused about what does and doesn't need one.

I'm making a simple application using HTML/CSS/JavaScript, it has a few quizzes and "tutorials" targeted towards children. I don't want the next tutorial/quiz to be unlocked until the previous one is pleted.

So for that would I need a database so that it "saves" when one is pleted? I don't need to save scores or anything like that, they just get to move on once they get a passing score.

I don't know much about databases, I've been asking a few questions about them lately to get a better understanding but I'm still a bit confused about what does and doesn't need one.

I'm making a simple application using HTML/CSS/JavaScript, it has a few quizzes and "tutorials" targeted towards children. I don't want the next tutorial/quiz to be unlocked until the previous one is pleted.

So for that would I need a database so that it "saves" when one is pleted? I don't need to save scores or anything like that, they just get to move on once they get a passing score.

• javascript
• html
• css
• database

• yes, the answers has the be on the server, otherwise everyone can see answers! – Prashant G Commented Mar 29, 2015 at 22:44
• 1 I have a friend who made something like this for a class he was in. He used pure JS. It depends on whether you want people to be able to cheat by going into their console and poking about. – Sumner Evans Commented Mar 29, 2015 at 22:45
• If you are not concerned with cheating, it is easy enough to record the client's progress using a cookie. They can go and edit the cookie to hop to the end, but it may suffice for your purposes. – Mitch Commented Mar 29, 2015 at 22:46
• 3 Given this is targeted toward children, I wouldn't be too concerned with a database for this. – Drew Kennedy Commented Mar 29, 2015 at 22:47
• 1 @roguerat, if I was the owner of a pany (which I'm not) I'd want to hire that kindergartener on the spot. :) – Sumner Evans Commented Mar 29, 2015 at 23:08

4 Answers 4

Any other requirements such as saving to a profile or needing to persist between sessions (e.g. changing of device)?

Browsers have localStorage APIs now which allow you to save a lot of the data (and keep it for a set duration of time). There are also good'ol'fashioned cookies which allow you save pieces of information as well.

Keep in mind that both of the above mandate the user use the same browser and allow these mechanisms. Obviously using "private"/"incognito" browsing would also affect saving status.

It's up to what you feel the requirements are.

EDIT Just saw your mention of a mobile app. If you're planning on allowing the experience to transcend devices, you'll need a database. otherwise, you'll be relying heavily on if they use cross-device sync (like Chrome and Firefox do with bookmarks, passwords, etc.)

If you don't mind that people can do a "view source" on the webpage or use every browsers' developer tools to find out the answers or move on to the next tutorial or quiz, then you can use cookies to store the user's status. Or you can use the preferable Web Storage API.

You might want to look at Firebase. Using just simple JavaScript on the web browser, you can have users with logins (or just allow them to login via Facebook or other services) very easily. And then you can store and retrieve data very easily as well, like quizzes, tutorials and results. This way nobody can see the answers even if they're adept at analyzing the webpage.

When you don't use database, before any check, you have to load all data in your static page.

So My sloution: store students situation in a cookie. On each page check cookie status and then use Jquery remove() to remove (Client-side) those parts of page that he/she can not access.

EDIT

This wont work when JavaScript is disabled.

There seems to be a lot of ideas but no clarifying on the database subject.

TL;DR is: No.

Now for the specifics. A database is nothing more than a way to store information. While traditional "SQL" databases (it is pronounced "Sequel" as in "My Sequel" for MySQL) have concepts of tables, where you define columns with items to store and saves each row with its value, much like an Excel file, some databases like Redis store key-value pairs and others lide MongoDB store JavaScript Objects.

You can store information in the source code (As Variables possibly) or in a file. A database is a way to organize that information.

With that said, in your case, you probably need a backend or an API. An API is basically a means of munication with a server through AJAX (JavaScript in the browser asks for stuff). That would be your way to retrieve information from the server as needed, so that users wouldn't see the answers before they answer.

With that out of the way, there are some options. FireBase (As noted on other answer) and AppBase are easy ways to integrate this concept with little effort. But they tie you and your information to their system, and they are mostly targeting more resource intensive apps.

Since you are using JS and seem to be enjoying your learning experience, I would suggest you consider suing NodeJS and defining the data as either a JSON file or a variable in JS. You keep working on your problem but add options and get to learn some stuff.

If you decide to integrate a database and possibly do some neat stuff, you have most of the groundwork done already.

If NodeJS picks your interest, Mean.IO and KrakenJS are, in my opinion, the best places to start, though they may both seem overkill in your specific case.

Do consider though: A database is just a small possible piece in a puzzle, and it's mostly a horrible way to name some of the software that tries to organize your information. Consider first if you need to organize information, and what and how do you need to organize, then start thinking if databases are the best way to organize it.