Our Single-Page Application is growing fine, yet it’s also starting to show its limits:

• There’s no way we can add, update, or delete our sample records
• We cannot properly implement our Login view, since it will require handling some sort of user authentication in terms of credential storage and session persistence, to say the least
• Truth be told, we can’t even say we’re actually showing something close to our original plan; our quizzes are still shallow items with titles and descriptions put together by a sample method providing some autogenerated data

It’s time to get rid of that provisional demo and start working on the real thing. We won’t use Angular for the time being, as what we need to implement has little or nothing to do with the client-side portion of our app. Nonetheless, we’re fully aware of the fact that most entities of the Data Model we’re about to build will have their correspondence in an Angular model class, just like we did in Chapter 3, Frontend with Angular, with the C# QuizViewModel and the TypeScript Quiz interface. As long as we don’t forget that we’re doing this for feeding Angular, we’ll be good.