Rebuilding a .Net Audio Recorder in Flutter

THE PROBLEM

Document Direct records audio for lawyers and doctors and transcribes the meetings and sends them back to their customers. Document Direct is ISO accredited and works with some of the largest law firms in the UK.

They had three apps on the UK app stores, that were built using .Net code. Apple had removed one and was threatening to remove the other two because of the outdated systems.

Document Direct approached external agencies to build the new app, using modern technology. Over the course of 6 years, they worked with 3 agencies and none were able to build the application.

The app had to meet the following criteria:
‍
1. Start recording the instant someone pressed record. If someone said “Don’t give medicine” and the recorder picked up “Give medicine”, it could be lethal.
‍
2. Record for 4 hours+, to be suitable in court proceedings, for example.
‍
3. Insert and overwrite audio limitlessly
‍
4. Save the audio if the phone died or someone got a phone call

After unsuccessful builds with other agencies, the Document Direct Team approached us to develop this project.

HOW WE DEVELOPED THE SOLUTION

Scoping + Design

The new app would be a like-for-like recreation of an existing app, just using modern technology.

So, during the scoping and design phase of this project, we detailed the features of what already existed, detailed any potential upgrades to the application and modernised the design.

AT A GLANCE

PROBLEM

Document Direct had 3 apps on the app stores that were outdated, and that Apple was threatening to remove
The apps needed a high level of precision and durability
The client had spent 6 years working with 3 agencies trying to rebuild the apps

SOLUTION + IMPLEMENTATION

We modernised the design using Material 3 design principles
We built an initial prototype that solved the precision and durability issue
We built and deployed 6 apps for the client using one code base, for them and their core clients

BENEFITS

Saved millions of pounds of potential lost revenue
Built with excellent quality, saving time to improve the app
Built with one codebase, so can be updated and improved easily

Development

Phase 1 - Core Development: Building the Main Feature

Initial Challenge: The main feature that other agencies had failed to build was recording and playback. This was the most critical aspect of the application and the starting point for our development team.

Quality Focus: We placed significant emphasis on the quality, modularity, and architecture of our code. Our approach and methodology were crucial to why we succeeded in building this feature where others had failed.

Iterative Development and Testing: Our engineering team created a stopwatch mechanism for precise control. They tested and iterated on the build and functions until the application met all the requirements stated in the problem set.

Development

Phase 2 - Extending the Application:

Client Presentation: Once the core of the application was developed, we presented it to the client, ensuring alignment with their needs, and proceeded to the next phase of development.

‍Connecting to Client's Custom API: Integration with the client's custom API was critical for ensuring that the application could interact with the existing infrastructure.

File Management: We worked on how files were saved after completion, implementing iterative improvements to the process to ensure efficiency and reliability.

Backup Services: A significant addition was the creation of backup services if the app failed to send the files. This safeguarded against data loss and added an additional layer of security and reliability.