kit created by embracing "differences"

[ishanijerin1]

There were three collaborations we attempted to undertake in order to make this project a success.



The first was collaboration between the company's product engineers and the OMO app development engineers. In order to provide a wide-ranging platform that would solve the problems of app development within the limited time and structure while still running the existing product, it was necessary to get the OMO app development team to cooperate.

However, the development methodology used for their own products was agile, which involves repeating development in short cycles for small functional units, while singapore email address the most commonly used OMO app development method was waterfall, which involves proceeding from top to bottom with the assumption that each step will not be reversed.

Team members who had each been developing in different environments needed to come together, and a wide range of ideas and opinions were exchanged even in the design that forms the core of the development.

This sometimes took time, but we made various efforts, such as using ADR (Architecture Decision Records) to work things out, and eventually came to an agreement.

*ADR: Records the history and rationale for software architecture decisions, as well as their results, and shares them with the entire project team.

Although there were many other challenges, such as establishing an organizational structure in a short period of time and external factors that hindered development progress, we were ultimately able to create a great product through the accumulation and fusion of the ingenuity and efforts of each member.



The second project was a collaboration with Qoil, a group company that provides one-stop services in the field of communication, from strategy planning to the planning, execution, and verification of optimal measures. We asked them to help with the internal branding and naming of a new product.

When changing direction from what was originally proposed as a renewal of an existing product, we approached it strategically, determining what information should be released at what stage and how to get everyone on the same page.

By the way, the name APPBOX, which perfectly embodies the idea of ​​a "development support kit packed with everything you need for the app business," was chosen by employee vote from among the many ideas thought up by project members, including Qoil.



The third is collaboration with other companies' services, which is one of APPBOX's features. This is a bold move that was made possible because it is a product aimed at a new persona.

"Rather than being a self-contained platform, we designed it from the beginning with the aim of being a platform that would be convenient by connecting with various services. We thought that being able to proactively collaborate with services that would be competing if it were a marketing tool and make app development more convenient would give APPBOX a unique strength. It was challenging and fun to come up with this idea.

"The integration and modularization are designed with the assumption that APPBOX itself will continue to grow, so I'm looking forward to seeing how it grows in the future. I want it to be recognized as a platform that supports app development," says CTO Furuki.