This story is a follow-up on A domain-driven Vue.js Architecture, where we introduced an architecture that’s based on Business Domains rather than technical concepts like components or store. If you haven’t already, we recommend to read it first as we will build upon that foundation for this one.
A Vue.js app typically needs to do a couple of things, no matter what:
One of our current apps…
In our blog, we will take you along on our journey of developing software, from overarching architectural ideas to some nifty tricks around the latest libraries and efficient team processes that are working out for us.
For one of our current Vue apps, we set ourselves a couple of goals that should ideally improve our long-term development performance. This story focuses on the architectural side of things. We’ve got subsequent stories about effective team processes, documentation and others in the making, so stay tuned and follow our Bauer + Kirch publication on medium. But first, let’s take a look at some of the goals that still function as our North Star to this day:
In our latest project, we recently faced the challenge of implementing loading states for a handful of deferred routes in a Vue app. As a full frontend framework, Vue provides its own router that makes it pretty straight forward to setup an app with some basic routes in just a matter of minutes.
However, it becomes a bit more difficult as soon as one wants to add some lazy-loading and appropriate loading states to the mix. In this blog post we are going to shed some light on some of the gotchas that, for us, were not immediately obvious from…