Project on Migrating OurSchoolHangout to .NET MAUI

Even an optimally chosen tech stack at the project's start can reveal its limitations over time. In such cases, migrating the product to new frameworks that better meet the solution's needs and scale can be an accessible and convenient way to address the situation.

The migration project of the OurSchoolHangout platform by BuildApps is an excellent example of tackling such challenges. Module and data adaptation, modernization of Back-end and Front-end without disrupting workflows, and much more.

Learn more details in the following parts of the case study!

The OurSchoolHangout platform is the ultimate solution for managing the educational process and organizing school operations. In other words, it is a high-tech digital interface that replaces traditional tools for teachers, parents, and educators, bringing various educational elements to the cloud.

As for the platform’s features, they include:

• A unified dashboard with full functionality.
• Separate user accounts.
• Automated systems for tuition payments.
• Built-in communication solutions.
• Efficient mobile applications.

Primarily, the platform is designed for managing educational institutions, planning educational processes, and interacting with educators and their parents. Despite its long-standing operation, the product owners were not entirely satisfied with the system's performance and efficiency. This prompted them to initiate collaboration with the BuildApps team.

While the initial task was broadly defined as "improve" the platform, an in-depth analysis of the solution helped identify the root causes of the system's unsatisfactory performance and create a clear technical specification with an actionable plan. The plan included the following points:

• Migrating the product to new (alternative) "technological rails."
• Modifying custom components and subsequently integrating them into the solution.
• Standardizing data formats and information exchange protocols.
• Adapting APIs and optimizing mobile applications considering the new tech stack.
• Modernizing the CI/CD process for new product iterations, particularly for mobile versions.

The challenges primarily involved technical issues and the need for a well-grounded rationale for each change and action we considered necessary to improve the product. If you're reading this case study, it means we successfully addressed these challenges and completed the project as a whole.

To say the project went smoothly and without issues would be a lie. While our experience and skills helped to smooth out some rough edges, challenges arose at nearly every stage of the work. Here’s what we implemented during the process:

• Replaced the .NET Xamarin.Forms tech stack with .NET MAUI. And no, Xamarin is not a bad framework; MAUI was simply better suited for achieving the desired results on this platform.
• Adapted some custom solutions to the new tech stack. More precisely, we slightly modified the MAUI framework itself to seamlessly integrate several modules.
• Implemented new libraries and adapted existing ones, particularly those related to the functional components of the platform's modules.
• Slightly modified the portal's GUI. Mostly, we expanded the functionality of the control panels and added the necessary modules to the system.
• Automated CI/CD processes. This accelerated the delivery and deployment of updates for mobile apps on the Play Store and App Store.

Sounds simple? But the platform has thousands of users, and their data also had to be adapted to the new framework. While data migration wasn’t an extraordinary challenge, it demanded significant investments of time and resources. And it was worth it.

The platform is fully operational, including its mobile versions for popular operating systems, Android and iOS. In other words, we completed the task on time, and the product owner was satisfied with the results. No numbers today, but here are the specifics:

• The .NET MAUI-based platform now works significantly faster. Additionally, its operational and computational performance has improved.
• New CI/CD algorithms accelerated the deployment process for new iterations of the product, including updates for its mobile versions.
• The functionality was slightly modified, interoperability for several platform components was added, and module performance was enhanced.

That’s it. Following the audit, we provided the client with a detailed analysis of the issues and opportunities for improvement. We implemented everything that was technically feasible. Currently, the project is in a “creative pause” mode, meaning we might theoretically secure a contract for its further development.

Want to create something similar? Simply contact a BuildApps manager for an initial consultation!