![]() ![]() For me-a CTO who started out as a backend developer-it looked gorgeous. ![]() In fact, the default theme he created is still with us to this day as one of the themes. He wasn’t a graphic designer but it didn’t matter. One of my colleagues, Karol Bzik, created the Default UI frontend. Secondly, I just took the Vue.js application boilerplate (generated by `vue-cli`) and started coding the project right away. Firstly, I knew it had to be an open-source project because it would need support from a large community. From a time perspective, I made a few decisions to help get things started. Starting the project, the sheer scope of what we wanted to do made me unsure that we would even succeed in releasing version one. to harvest the architecture as a result of building the first application. We first built a killer application and only afterward extracted a framework out of it. ![]() I’ll share some of the lessons to help you make more informed decisions based on our experience. We went a completely different way with Vue Storefront and I must say we learned a lot in the process. You should only release after these phases to complete. The common rule of thumb is that with the framework you should precisely design it, document it, and ask the opinion of the community. With a framework, the expectations are much higher because it will be used as a foundation for other applications and products. Every startup works this way.īuilding a product, however, is a different challenge than building a platform or software framework. You see and validate the results, and then adjust the assumptions. The second reason for simplifying things and building a quick MVP is that it keeps the team motivated. However, it’s very hard to achieve-even with the greatest product-if you are in a crowded space that already has solid leaders. If the product is good enough, you might even advance the market, find yourself as a category leader, or even create a monopoly. “Zero to one” is all about why being first to the market, going from zero (not having a product) to one (having a product). It’s often very difficult to start a new endeavor because, at first, it might look very complex and overwhelming. And once you’ve got some progress, don’t forget to get it out of the door: Release it. If I were asked to give a single piece of advice that would bring success in a software project, I’d say: Just get it started. ‘Designing a headless frontend framework for enterprise applications’ is a free resource aimed at CTOs, CEOs, and developers who are looking to undertake a headless build and want to know how to get the most from their resources.įrontend Frameworks eBook sample: Designers and Harvesters You can download the book now and, to give you a taste, here is a sample chapter. ![]() To help others build better headless frontend frameworks, we have collected our knowledge and experience from building Vue Storefront into a brand new ebook called ‘Designing a headless frontend framework for enterprise applications’. Vue Storefront, itself now part of the MACH Alliance, was developed fast and was the first PWA solution of its type to market, which helped it to gain the leadership position that it still holds today. Not only do we believe in it, we’ve been ahead of the curve for quite some time on this. We totally believe in technology that is Microservices based, API-first, Cloud-native and Headless. As any of you know who follow Divante, we are MACH advocates who always endorse brilliant frontend frameworks and headless builds. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |