Skip to main content

Having an organized Browsing Experience

Are you the kind of person who inevitably has to work on multiple tabs due to the complexity of your work?
We have all been there. You are researching about something, or building something, or doing any other task on your browser, and you end up opening at least 4 tabs if the task is simple, 10/12 tabs if the task is tough, or sometimes tabs you're too afraid to even count!
You know what opening so many tabs creates?
Yes, after a certain point, you don't even remember exactly on which tab is the information you looked at recently. You know everything that's going to help you is right in front of you, but you don't know where exactly.
And if a time comes when you have to disconnect from the work in progress, and maybe call the day or start working on some other thing, you are too much afraid to close these tabs.
Eventually, you start doing all the tasks on the same window, and mixing everything, or you open a new window and never really close anything.
One of these things is bad for your productivity while the other is bad for your memory.
A solution to get rid of this problem is saving Browser Workspaces.

There are many browser extensions, both in Chrome and Firefox that allow you to save a group of tabs as 'Workspaces'.

If you're a Chrome user, I suggest you use the following extension:
Workspace Launcher

During my time as a Chrome user, this extension greatly helped me to remain organized while doing multiple tasks.
Then I moved to Firefox, and (I guess) due to my poor searching skills, I couldn't find this kind of extension for Firefox. This gave me an opportunity to build my own extension! I could customize how it looked and overcome all the shortcomings I felt as a user in the Chrome extension that I used!
A week of learning and coding, and I was ready with my own Jarvis Workspace Manager!

The Jarvis-like Interface

Now, if you have read my previous blogs, you might know that I'm a huge fan of Iron Man.

Yeah, that's my home screen
By the way, here's how to do this if you're wondering: Jarvis, we love you 3000

Anyway, so it was only fitting that I come up with an extension which makes it look like a JARVIS Interface is managing my Workspaces too!
So what do I need to achieve this? Simply, just a dark interface with a bluish green hue for the text and elements.
So that's what I did.
My current Workspaces in Firefox
So this is how it looks. Feel free to stalk your way in to what I do with my life. It'll also give you a better idea to know what kind of tab groups you should save as Workspaces.

Save tabs with just one click

In the Chrome extension that I used before, I had to manually enter all URLs that I wanted to be saved as a Workspace. That was a real pain if I had more than 5 tabs open!
So I made an enhancement:
Official Demo of the extension, don't miss this!
All your open tabs are saved and you can carry on with your work seamlessly.
Of course, you can still add all the tabs manually too (the hard way), but I don't use that feature even though I had a good time coding it!

Having a map of your best links

If you save Workspaces for all your important tasks, you have an organized list of all your best important links in the new tab page automatically.
It's not necessary to open the entire set of all the tabs every time. Sometimes we just need to go to one of the links. 
All such possible links will be right in front of you the whole time. 
So you won't be just replacing your Mozilla default startup page with an extension's, it would rather be an improvement over the existing one.

Developer Support

Another good reason for its usage is that you know the developer who can solve the bugs for you and bring out new features on your informal request!

So all the best and I hope you use a Workspace Manager extension to organize your work, because believe it or not, you need it!


Post a Comment

Popular posts from this blog

Namaste JavaScript Quick Notes

Note:  Akshay Saini's Namaste JavaScript is probably the best course for JavaScript developers out there. These are my personal notes that I made while watching the course; they serve more of as an online quick reference for my understanding and revision, and I hope it benefits anyone reading it too! Everything in JS happens inside an Execution Context. Before a JS code is run, memory is allocated and variables are set as undefined   , and functions are set as their exact code in the scope within the Execution Context. The global execution context hosts all the global variables and function definitions. An Execution Context has 2 components: Memory, that stores variables and functions; and Code, that reads and executes the code. Call Stack maintains the order of execution contexts. Since JS is single threaded and asynchronous, at one point of time, only one function is executed which is at the top of the call stack. For each function, an execution context is created before executi

An introduction to APIs

API is an acronym for Application Programming Interface. Let's start with first defining some basic terms: Browser: These are browsers. To visit any website on the internet, you need a browser. Server: Hmm, this is tough. In simple words, server is a computer. Yes, just like the laptop, or PC at your home. The only difference is that it does not have a screen. Of course, there are other differences in technical specifications, but at its core, the server is just, simply, a computer. That's it. So why is it called a server? Because it serves . When you go to a website like , your computer connects to the internet and gets you your search result. But your computer's internet connection has to get that result from somewhere, right? If the google search result is giving you some answers, the answers have to come from somewhere. What is that place? The answer to that some place is: a server. When you click on the search button on google, or hit enter after typing, &q

Review: Nestjs - Finally a scalable way to build APIs

I have been thinking about this for a long time. There HAS to be a defined way to build APIs in a scalable way.  If you have used Node, Express, etc in your side projects, you might have felt that after a point in development, debugging truly becomes a pain. Sure, enterprise-level API codes are great. But a lot of times, these configurations are too much, and probably not even needed in other projects. To be honest, I haven't seen a lot of Open-Source API codes either to make a judgement on how experienced developers build their APIs. Anyway, I came across an amazing framework recently, and I think if you are coding a complex API, this should be your way to go. Nest.js Nest.js is a framework for building efficient, reliable and scalable server-side applications.  You essentially break your APIs into controllers, services, and modules, which allow you to modularize the smallest of functionalities in your endpoints or the API as a whole. Why is modularizing important? As I have talk