Remote Development Reinforcement for the Fitness Game-Changer, MyFitnessPal

Challenges and Solutions

• Working with legacy code, migration to Swift and switching to MVVM

  Despite the existing app being initially created with Objective-C, the requirement was to use Swift when implementing new features. Resolving incompatibilities and refactoring legacy code sections, our developers have done a tremendous job to keep on schedule. The keys to succeeding with migration were the ability to handle ever-shifting objectives and high responsiveness from both sides

• Implement a new tool to simplify and speed up the old way of modifying public ads files

  The MFP team was unsatisfied with the long and expensive procedure, which required the input of both managers and developers. Sometimes what should be a simple and quick update took R several days to be applied. We introduced an admin panel for the ad specialists who don’t work with code. This allows the specialists to instantly modify public ad files without having to involve the developers

• Slow interaction between graphic designers and developers

  By integrating with Storybook, we solved the issue of re-developing frequently used items for the web GUI. Later on, MyFitnessPal Storybook expanded and became relevant for other products, which were of the same brand

• Remote teams and time-zone difference

  We used the “Game Plan” concept, which included an in-depth discussion and evaluation of the current and planned features before embarking on the implementation stage. It allowed us to achieve mutual understanding with the MFP team and actively resolve problems in the early development stage. Our “Context- message-options” request composition approach made it much easier to avoid the frustrating “ping-pong” communication model and reduced time delays