Up to this point, we have done our best to keep the layout as simple as we could, so we could focus entirely on the server-side and client-side coding aspects of our app: ASP.NET Core Web API Controllers, Angular 2, C#, and TypeScript. Keeping the layout to a minimum is generally a wise approach when we're learning something new, it also has a few downsides, though, the biggest one being the blatant fact that our application is rather unattractive, to say the least: there is no user, client, or customer that wouldn't say that... or worse.
It almost entirely depends on what we're planning to do with the project we've been working on; as we just said, while we're working our way through tutorials, demos, or sample projects, it's not bad at all, for at least a couple of good reasons:
- We will greatly benefit from keeping our focus on .NET and Angular 2, leaving the rest for later; applying styles is something that w can easily do whenever we feel like it, even if we don't have a decent grip on stylesheet language already.
- It's generally a good idea to restrain ourselves from doing any relevant style implementation until we can fully understand where and how to do that conveniently; to put it in other words, we shouldn't do styles until we find a suitable approach for doing that within the given scenario and/or environment.
That's why we chose to take this path in the first place; we're definitely in the learning phase, after all. However, since we planned to build a production-ready native web application, we can't restrain ourselves from applying some styling any longer; there's no way that our imaginary product owner would be satisfied otherwise. It's time to dress our (mostly) naked doll and make it as pretty as we can.