Go Back

Modernization of the SAVY Platform

Classic registration is an anachronism. Users want to log in within seconds, so we provide them with such options. Learn more…

Blog post

Modernizing Savy: A Little Convenience for the Platform’s Users

As part of the SAVY development team, we know its specifics. As expected, we rejoined the project, completing new tasks once again. This time, the BuildApps team worked on integrating optional authorization methods into the mobile and web versions of the platform. Sounds simple? Perhaps, but it’s still interesting work worth learning more about.

It’s not just login – it’s a new interface with APIs and advanced user data protection algorithms. Authorization modules via popular platforms with a somewhat non-standard implementation.

Interested in the details? Check out the full version of the article!

From SAVY’s Origins to Its Scaling

We worked on SAVY in the past, and now we’ve returned to add a few important touches.

Today, classic registration on web resources takes about 5 minutes. From the moment of clicking the corresponding button to filling out all the fields, confirming contact details, and logging in with subsequent authorization in the system. But what if you skip most of these steps and authorize immediately using existing profiles? Yes, yes, this is not new to the industry, but it’s still an optional solution. And it’s primarily important for improving UX, which means increasing the audience, conversion, and so on.

So, the task is simple – to develop and integrate modern authorization tools into the platform. Heard, accepted, done.

When There’s a Need for Alternative Options

How can you make a user immediately feel “at home” on the platform and start interacting with it literally from the very first seconds after launch? Easily – just give them the opportunity to skip the lengthy registration and identity verification process. Or at least simplify the login while leaving the KYC policy unchanged.

The solution is simple – integrating Google Authentication and Facebook Authentication into the system. The benefits of these solutions are obvious:

  • The providers maintain high standards of personal data protection, encrypt connections, and so on.
  • The service providers have their own verification policies, so it’s practically impossible to bypass the system.
  • There is still the option to conduct post-verification through the platform’s internal algorithms.
  • Clear APIs that can be partially adapted to the standards of the target project.
  • Instant registration with the transfer of basic data (if the profile is properly filled out).

Therefore, choosing these authorization providers was an obvious decision. As was the technological part of the project, namely:

  • Library for Google auth: google.com/gsi/client to load.
  • SDK for Facebook auth: accounts.google.com/gsi/client.

Was the integration a challenge? No. However, there were additional tasks that were not as easy to implement as the core parts of the project.

Security Above All

The reliability of authorization is the Achilles’ heel even of the most secure systems. The problem is that almost all protocols have certain vulnerabilities. And our secondary task was precisely to eliminate them. So, within the project, we:

  • Integrated APIs for authorization via Google and Facebook (through Meta accounts).
  • Edited algorithms for the correct processing of data entered and received from servers.
  • Encrypted communication channels so that information packets could not be intercepted or read.

The result was entirely expected – two new authorization methods that positively influenced the platform’s activity.

Interim Project Outcome, Background for Further Cooperation

Authorization via Google and Meta improved the user experience and provided both existing and new clients with options for logging into the platform. As analytics showed, the registration system through Google works better since almost the entire audience has accounts with the search engine. Facebook performed worse, so this authorization option is currently disabled.

As a result, the client tested the concept, provided users with options for registering in the system, thereby simplifying onboarding operations and slightly increasing brand loyalty. However, this is just one of the stages, another step toward further modernization of SAVY.

Do you want to implement a similar project? Need help from professionals? Entrust it to the experts at BuildApps. Contact a manager to start cooperation!

Ready to get started?

Contact Us