This is Zaiko Inventory , A inventory system dedicated to solving a simple problem : Many inventory management tools are difficult to train employees on, lack intuitive designs, fail to provide comprehensive visibility, and have confusing user flows that lead to errors. Zaiko tackles all of these shortcomings to deliver an improved experience.

When researching this project it was important that we focus heavily on competitor audits. Implementing the inventory management system in a creative, innovative, and effecient manner was the main goal of the app. The Zaiko team consists of 6 members split into 2 teams Development Team(Me + 1), Design Team (4 designers)
Together the research methods we used were :

With the results from these research methods we had enough data to start building our solution!

When designing Zaiko our most important goal was to be innovative. We didnt want to create a "List of Items" like so many of our competitors. The system must be simple, easy to use, and visually appealing! We wanted to keep the idea of innovative, but safe. We felt using an orange secondary with primary blue would do just that ; we kept the amount of locations on the screen to a minimum to better adhere to Millers law . Users of our competitors complained significantly of cognative overload, so we decided Zaiko would handle that problem by limiting locations to 6 on the screen at all times. The multi-colored widgets are to make the app more inviting and reduce beginner fear of the app's content. In short, everything has a purpose. Through design we adequately aimed to solve the problem of both user overload, lack of intuitive design in the competitors, and overall confusion when completing tasks.

Implementing Zaiko design into development and an actual web app would take more than a simple CMS system, a full Web app would have to be built. I chose the stak personally based off of web capabilities and hosting limitations. I knew from the start of the project I wanted the app to be hosted and live, so I decided to look into the hosting I already owned which was Cpanel. Since Cpanel uses an Apache server, I decided a M.A.M.P stack was the best solution . MacOS is my home system , Apache server , MySQL , & PHP for the backend. For the front end the dev team Decided React would allow for dynamic DOM manipulation which would make the application lighter when querying all of the objects and data it would take to run the app. Developoing along side the design team created challenges which pushed me beyond my prior knowledge of web application development. Last minute changes, reworked databases , and latenights debating over functionality of the app led to a polished product & MVP boasting the final features and acheived goal of the application.

In the end, the team presented and showcased 2 products ; the Figma design which holds the original file, and the web application hosted and live on ipads specifically. These products simultaneously demonstrate a new way to manage inventory that is intuitive in design, easy to teach , and lacks cognitive overload! The full & final project is below + my Github Repo ! (If you want to try the online version contact me for the password)