A developer browser

I was doing some reading the other day and one of the articles was about browsers that were based on the Chromium project. I was kind of pleased that I knew about most of them and have, in fact, many installed on this computer. I rotate through them to test out new features, etc. I’m always impressed with how each browser adds value to time spent online and how they push each other to add new features. Those of us who were online a long time ago know that our choices were very limited.

I ran into this new-to-me browser – Blisk.

Blisk is the first developer-oriented browser. It provides businesses with a development workspace for the teams and freelancers to develop and test modern web applications twice faster.

I was intrigued with the overview. It’s designed to assist those who are website developers. I don’t do a lot independently these days from scratch but spend time in Google Sites or WordPress. And yet…

From the description, it reminded me of the golden age of development with Adobe Dreamweaver. You could work with and inspect code and then see it immediately all in a single program. But, times have changed and working for the desktop browser isn’t the only game in town.

Imagine working on a project and seeing what it looks like immediately in another completely different device.

Once you get past the initial screen with every iPhone model I could think of, I found the Samsung collection and my S7.

With Blisk, I was able to see my desktop version and a mobile version at the same time. I could rotate it to landscape mode to check out the looks there. Staying in the main window, I could scroll there and the phone would show it’s equivalent at the same time. It just followed me along.

The inspector lets me observe the elements that go into producing the content. If you apply for a Blisk account, you’re able to take and save screen captures with a number of options.

Since I do spend most of my time in a CMS, this isn’t a tool that I would use regularly but I found it really interesting to explore and learn about the “how” the content gets to the screen. For people that do a lot of big graphics or those annoying widgets, I suspect that seeing how they monopolize screen space on a smaller device would be helpful.

Since Blisk is based on Chromium, there’s very little learning that needs to be done to get up and browsing. The other tools unique to Blisk and developing content are fascinating and having them all on the same screen is very engaging.

Author: dougpete

The content of this blog is generated by whatever strikes my fancy at any given point. It might be computers, weather, political, or something else in nature. I experiment and comment a lot on things so don't take anything here too seriously; I might change my mind a day later but what you read is my thought and opinion at the time I wrote it! My personal website is at: http://www.dougpeterson.ca Follow me on Twitter: http://www.twitter.com/dougpete I'm bookmarking things at: http://www.diigo.com/user/dougpete

2 thoughts on “A developer browser”

Comments are closed.