Published on Monday, Dec 14, 2015
Author: Blisk team

Becoming Blisk browser

The story of how we came to the idea to create Blisk, the browser for web developers

Becoming Blisk browser

As we wrote in the previous post, our team relocated from Ukraine to Estonia and took part in acceleration program.

During the program, we finally understood that product is not fully solving the problem of a customer. Moreover, that it was not so easy for our users to integrate the tool inside their infrastructure.

We expected SaaS approach to be the cure-all for our customer and even defined our competitive advantages (below are some of them):

  • Enabling testing on real devices not emulators. QA-engineers and developers can be confident about supplying their customers with working products.
  • No coding, no installation, device independence. Start using within 3 minutes. The installation process is as easy as installing Google Analytics.

However, making interviews gave us the understanding that our users are not always willing to work with the cloud and to test on real devices. For example, one of our users, one of the Estonian banks, could use our tool with landing page only because of security issues. Moreover, small and medium outsourcing companies could not provide their developers with devices to test.

Blisk browser
Blisk browser

This is how we understood that testing with emulators inside of desktop application was the best fit for our customers. And we came to the idea of creating Blisk, the browser for web developers. Thus, our SaaS tool became a part of the new browser.

Learn the basics of using Blisk:

Learn more about Developer Mode, Development Domain, and Device Manager on Blisk Documentation.

Article tags:

Need to run a mobile test or responsive test of your website on the latest iPhones, Android devices, tablets, and desktops?