How to Go From Zero to Serverless, Conclusion

Over the course of this series, we’ve built out a fully-functional serverless application using common web development tools. By using Backand to replace the server, we’re able to deploy our to-do list application to any provider that can serve files, rather than having to restrict ourselves to hosting providers that support a particular tech stack. While our app is rudimentary and largely comprised of programmer art, the concepts it demonstrates are powerful and can be used at the base for larger and more complex web application suites. In this conclusion to the series, we’ll discuss some of the improvements that we can make to our application. We’ll also look at building real-time behavior, as well as some considerations for deployment and hosting.
Improving the UI
There are two major problems with our user interface. The first, without being too self-deprecating, is the quality of the UI. We have elements available for all of the ideas we’ve chosen to express in our design, but they’re thrown together with an eye to demonstrating the concepts behind them, rather than with an eye to the usability of the end application. As the options here are literally endless, I will only call attention to the importance of spending a healthy amount of time designing your user interface prior to writing code, to ensure that the end product isn’t doomed to failure through a poor user experience.