Dead Mojo

About Us

Our History

In 2022, I started building an app for an IBOS logistics team. The first version was developed in Excel using VBA and macros, allowing the team to print a single page with information and a QR code. The team used this for about a year, but as change requests became more frequent, maintaining a consistent version across all users became challenging. Every update required redistributing the sheet, which led to issues since many team members were using different versions.

To solve this problem, I set out to build a fully functional program with an updater—this is where version 2 comes in. I started by choosing a programming language for the project. Initially, I liked the simplicity and ease of use of C#, but as I developed the application, I wanted something more lightweight and faster to provide a smoother user experience. So, I switched to VB.NET.

After releasing version 2 to the team, I received many compliments, and everyone was happy with how it functioned—except me. I felt it looked unprofessional, like something you’d find in a doctor’s office or a mechanic shop. That’s when I decided to start working on version 3.

Development began in late 2023, and I initially expected it to be a quick process since I planned to reuse the core code from version 2. However, everything changed. As I was working on version 3, the client we were working for modified the way we could access their internal pages, which in turn locked my program out of the system.

With a few patches, I was able to keep the core functionality of version 2 running, but I wanted to do more. My goal was to simplify the team’s day-to-day paperwork and provide a better, more efficient tool. That’s when I decided to rewrite the entire program. I had many conversations with the team about their daily tasks and what tools could improve their workflow. From these discussions, I compiled a list of features that would enhance efficiency.

Once I completed version 3, I set up a test group within the team and had them use the program for a few months, identifying and resolving any bugs. When I felt it was ready and all major issues had been fixed, I officially released it to the entire team on November 18, 2024.

Now, a few months into full release, our client has once again changed the way documents are printed, making things more difficult for the team. On top of that, some of the laptops provided by the client are unable to run the program. Additionally, the client has become aware of the software and has requested changes, including a version that will run on all platforms.

And that brings us to today. I have launched this website to once again provide this service—not only for our IBOS team but for every IBOS site operated by our client.