Transforming Patent Analysis: From MVP to Enterprise-Grade Solution For Mobile

• Stage 1

  To kickstart the project and plan the implementation of the first version of the platform, Binary Studio conducted a discovery phase with SnapCare executives and created a roadmap for web-based applications. We selected React, Node.js, and JavaScript as our main technology stack and Heroku as our hosting platform.

  The MVP was released in three months and was built as a booking system between hospitals and nurses. The platform also included time management and payment systems.

  SnapCare launched to an early adoption audience of 1,500 nurses and a dozen hospitals. In the first year, they saw a whopping 77,000% growth, becoming the fastest-growing tech-enabled nurse staffing company in the United States.

  • Vendor and asset management
  • Bid management with automatic cost and margin calculations for various construction project types
  • Automatic contract generation based on bid information and predefined contract templates
  • Generation of project information reports for truck drivers and construction workers

  After this significant update, the first external beta users were invited to test it. Based on their feedback, we fine-tuned the system and released it to the public.

• Stage 2

  To meet the evolving user needs, our team developed a set of features that enable operators to manage and monitor their charging station networks in real-time, including:

  • Receiving malfunction alerts
  • Managing charging stations – their locations, firmware updates, and access restrictions

  Additionally, we integrated with several third-party systems via API to incorporate key functionalities:

  • Authentication systems for secure access
  • Billing and parking systems for payment processing

  After its public release, MassageBook quickly started attracting a community of massage therapists. Based on their feedback, we've been continuously adding new features to the platform, ensuring it not only meets the needs of our customers but also brings additional value.

  To ensure the platform's reliability and scalability, we selected the most advanced and suitable frameworks available. For the MassageBook 2.0 update, we used Marionette and Backbone, brand-new for that moment. This update brought several new features, like an enhanced search, integration with Facebook business pages, better SOAP notes, and more customizable email campaigns.

  During this phase, we also introduced the first mobile app for MassageBook users. We started with native apps built with Apache Cordova. These apps were just the beginning, and they set the stage for later cross-platform versions made with Flutter. For more details about the mobile app's evolution and special payment features, check out this dedicated case study.

• Stage 3

  After successfully launching the dating functionality, we focused on expanding Lynk's features and target audience. The goal was to transform the dating app into a social media platform that catered to various user needs, including social interactions and business networking.

  Lynk has evolved into a video streaming mobile app that consists of three modules:

  1. The Dating module that offers:

  • Virtual speed dating events based on interests and topics
  • Timed video interactions to assess compatibility
  • Chat-based conversations after mutual interest is expressed

  2. The Community module that includes:

  • Interest and topic-based virtual events for fostering friendships
  • Ability to make new friends with similar interests

  3. The Business module, which provides:

  • Exclusive internal events for organizations
  • 1-on-1 interactions among guests

  Throughout this expansion, the Binary Studio team ensured seamless integration of these new features while maintaining optimal app performance. A Binary Studio project manager was introduced to the team, implementing Scrum methodology to streamline the development process and boost efficiency.

  In addition to the app's enhancements, the Binary Studio team developed a React-based admin panel to simplify app store releases and centralize the application's management.

• Stage 4

  Lynk's expanding user base required us to optimize the app's performance for heavy load. The app's video streaming nature meant that a large number of users could simultaneously join an event, putting significant strain on the system.

  To emulate high loads, Binary Studio team applied the Nitro framework using Node.js to generate bots that simulated real user behavior. This approach allowed the team to identify and address potential performance bottlenecks.

  One of the critical aspects of handling high loads was database management. Throughout the development lifecycle, we worked with various databases, including MS SQL, PostgreSQL, and MongoDB to handle different data storage requirements. Our team also implemented Redis for caching to optimize performance and moved logs to CosmoDB to manage high loads effectively.

  To further enhance the app's scalability, we experimented with ready-to-use solutions like PlanetScale, which offered built-in scaling capabilities.

  The microservices architecture implemented in the previous stages proved beneficial in supporting high loads. The modular design allowed for easy scaling of individual components, ensuring the app could handle increased traffic and usage.

  As a result, we ensured Lynk to support over 100,000 concurrent users during events, maintain high-quality video streaming, and provide a seamless user experience.

The new platform follows a modular monolith architecture built with .NET 7. Given its broad functionality, the system comprises several components. To ensure high performance, reliability, and scalability, a message broker is used for distributed communication between application modules, along with CQRS and rigorous unit, integration, and architecture testing practices.

To ensure stable, real-time performance, we also configured AWS S3 for storing static images, employed SignalR for real-time notifications, and utilized Automatonymous to implement the saga pattern for maintaining data consistency.