Check out some kickass WebExtensions by Nodetics: https://nodetics.com
60 karma · joined October 23, 2017
1. How extensively do those 5 people test the software? Do they test all features or just part of the software?
2. What is the background of those 5 people testing the software? Do they understand UX/good UI design and how well?
3. Are these 5 people just random users or professional test engineers?
4. How passionate are these 5 people about the product/service they are testing? How meaningful is it for them that the product actually works _really well_?
5. What is the quality level of feedback these 5 people can provide? Is it like "meh, this is ugly" or is it detailed, concrete and contains practical improvement ideas that can be easily implemented?
The primary driver for this extension was the fact that especially when searching with Google and using "sort by date" there are A LOT of spam domain hits which lead to potentially malicious sites. It turns out that a simple regexp will catch most of them: \.php\?\w{6,9}=
So I first implemented functionality to be able to block these spam domains (and to easily report them to Google as well).
Then I found myself clicking many times different menus when I wanted to search by date (try it on Google for example). Those clicks add up so I wanted to make it faster and simpler. So I implemented the popup based search and made the UI as simple as possible but still powerful (sort by, search category). I later added support for multiple search engines to unify the experience.
Then I found myself often searching for certain types of things which are provided by a handful of websites. So I figured that having "search profiles" would be good so I don't always have to write a long line of (site:foobar.com OR site:yeehaw.com OR ...) type things in the search box.
Then I got REALLY annoyed by the very small navigation buttons (next page mainly) in Google search. So I wanted to make them BIGGER so that I won't have to point and aim like in CS every time. After I implemented that, I thought that just scrolling with a mouse down should load new results (infinite scrolling) but it should be opt-in feature only. I want to find information fast and don't want to spend time aiming for UI elements.
Then during evenings the bright colors blind me so I implemented built-in dark mode for Google and Bing and created an option to use any custom CSS for search engines.
And the story goes on. So the features that are there were something I personally needed. And since most people need search every day, I figured that why not share the extension with others as well.
Currently there's no business intention and the code is not obfuscated in any way.
"permissions": [ "tabs", "https://www.googleapis.com/", "identity", "notifications" ]
"tabs" is just needed to check if Kanbanly is already open in another tab. If yes, activate that tab instead of opening a new tab.
The side effect of this permission is that Chrome claims the extensions has access to browsing history (which is incorrect since that would require "history" permission). So it's really a Chrome bug and the WebExtension does not access your history or any content in tabs whatsoever.
So given two tasks: Task A with 5 hrs of effort and value of 100, and Task B with 5 hrs of effort and value of 20, you should first do Task A since it produces more value. Value figures should be relative so when you estimate how valuable some task is, compare it to at least two other tasks.