1. Automate deployments
What is it?
The process of downloading code, building, and pushing it live to a URL or app store. Automating this repetitive task not only saves time, but reduces errors, frees up developers and ensures everybody has access to the latest build.
Also known as continuous deployment (CD)
Technologies we ❤️:
Time saved
4-12 hours per week
2. Use pre-built UI component libraries
What is it?
A set of user interface componenets for common UI/UX scenarios.
Whilst developers think it be might be flex to build everything from scratch, there’s actually a lot that goes in to a UI component.
For example, take a date picker. On a desktop it might display as an overlay. On mobile, it could be a full screen modal. On screen readers we’ll need to accomodate text-to-voice, and so forth.
Component libraries we ❤️
Time saved
8-20 hours per screen, depending on complexity
3. Re-use a project starter template
What is it?
A re-usable group of files, containing code, artwork, documentation and designs that are common across most software projects. They’re highly specific to their domain, for example, a 3D game starter template will differ greatly to an MVP starter template.
At LLUME we have the unique advantage of acquiring code and best practices from building MVPs all day long - it’s all we do! Other teams may not have that luxury, and are intead pulled in various directions, affecting their ability to compound knowledge and development expertise.
What does LLUME use?
Our own internal project starter templates. (Hint: they’re built around our tech stack of Vite, React, ExpressJS, Supabase and Google Cloud)
Time saved
8-16 hours per project
4. Automate testing
What is it?
Code that runs to check the integrity of your existing code base, preventing new changes from breaking current functionality.
An excellent use case is it check the integrity of the build before code is merged in to the main production branch - preventing innocuous bugs from causing catastrophic failures. This is known as continuous integration (CI).
Long-term payoff is even higher as the project grows.
Time saved
1-4 hours per new feature
5. Make use of hot reload and live preview
What is it?
A mechanism for developers to see code changes immediately, rather than wait minutes or hours for a build.
Technologies we ❤️
Time saved
2-3 hours per day
6. Automate error tracking and logging
What is it?
When you’re a startup, everyone is QA (even Founders should be testing!). But what happens if you come across a bug, long waiting time or a crash?
Rather than spend hours digging through the device logs, those errors can be automatically captured and saved, and then fixed in accordance with the project roadmap and priority.
Technologies we ❤️
Time saved
1-2 hours per day