Ever wondered how software developers use document comparison in their apps and web services? We spoke with Mobile Helix – developers of software solutions that make it easy for lawyers to be productive using smartphones and tablets – to learn more about the comparison feature available in their secure container app. Missed Part 1? Catch up here.
When we last heard from Mobile Helix, the President and COO, Maureen Blando, was explaining why the company needed to replace the document comparison technology in its app.
The app in question – LINK – is relied on by lawyers and legal professionals who depend on accuracy every day. The old technology was like Microsoft Word’s in-built comparison tool, which is known for missing small but important details.
“If you’re going to offer comparison,” Maureen explained, “it must be high quality or lawyers won’t trust it or use it.”
In this post, Maureen gives insight into the process of choosing a replacement software development kit (SDK) to compare two documents programmatically in the LINK App.
The list of requirements for a comparison SDK
The first and most important requirement for Mobile Helix was that documents weren’t sent to the cloud for comparison.
“When looking for an SDK, we knew we needed to be able to provide server-side comparison,” said Maureen.
Rather than processing happening in the cloud, Maureen explained that comparison technology needed to be coded into LINK through a native .NET API so that it wouldn’t “create any ripples in what LINK offers since we deploy our solution on virtual machines behind the user's firewall.”
Secondly, Mobile Helix wanted to partner with a technology vendor that was the right fit for LINK users.
“Since our app users are lawyers, we knew we wanted to partner with a technology vendor that had an established reputation in the legal tech industry,” said Maureen. “So, we thought about who we knew from big industry events and went from there.”
Considering all options
“Next, we evaluated our top contenders from publicly available information, and spoke with our law firm clients that were already using comparison products,” continued Maureen.
“We ruled out any products that didn’t meet our business requirements and ended up with just one SDK product left.”
Trialing the last SDK standing
Before rolling out any SDK into the LINK App, Mobile Helix knew it wanted its senior in-house developer to review the integration and feel confident everything would go to plan.
“Our development team reviewed the product and began work on the integration,” said Maureen. “For the next few weeks, we evaluated how it performed for LINK users.”
Only then was Mobile Helix fully confident it had found the right SDK solution for its app.
The end result
Mobile Helix has been able to offer highly accurate document comparison in its LINK App after finding the right SDK.
“The SDK works as it’s supposed to, and it’s fast and accurate,” said Maureen. “After our experience, we’d encourage any other software developers to really consider what their business requirements are and see how this corresponds to comparison SDK products on the market.”
This is only part of the Mobile Helix story. Learn more about their comparison SDK experience by reading the Mobile Helix case study.