Introducing Omnibug v1.0

I'm truly excited to announce the release of Omnibug v1.0, the largest redesign and development in Omnibug's history. A brand-new design, new features, and some old features have been brought back for version 1.0! This version has been in the works for about 6 months, which feels like forever, but moving forward the updates will come regularly, adding new providers and features as the feedback rolls in.

So, what's new in this version? You can check out our change log, but let's cover some of the new features here!

A Fresh New Look

The design has been modernized, and lots of small quality of life changes have been added. You can see below just how different things look now:

The old vs. the new
The old vs. the new

For those that prefer a minimalist style, don't fret. A compact version is on the to-do list!

New Providers

A full list of providers (marketing tools) on our GitHub repo, but few new providers have been added, including OptimizelyX, Segment, Facebook, and more. A few older providers that were very outdated were removed, with the plan to modernize & add them back in shortly after the 1.0 launch.

Filter Out the Crap

You could always completely exclude certain providers in Omnibug, but that was a global change. We've added a way for you to filter on a tab-by-tab basis, either by provider or account ID. If you're doing Google Analytics QA and want to remove the Facebook pixels from showing up? No problem, just filter it out!

Save Your Requests

One of the most requested features of Omnibug. This previously existed in the old Firefox versions, but constantly wrote to a file and you couldn't output a specific session. Now you can export all the requests that you had in a session, as well as adding notes to each request (this is disabled by default, learn more. The output is a CSV with the event type, provider name, account ID, request ID (for identification of redirected requests), the raw URL, any POST data, the request timestamp, and any notes you may have added to the request.

Navigation Requests & Clearing Between Pages

Previously, when you went to a new page, Omnibug had no way to show that you navigated to a new page or clear any of the previous page's requests. Now you have options! You can show or hide any navigation requests, e.g. if you go from /help to /help/settings, this will now show up in the interface.

Example of a navigation entry
You can see here that two pages were seen: / and /help

Additionally, you can now clear the requests as you navigate to different pages. If you don't need to see what happened on the previous page(s), this is a great way to de-clutter the interface.

A Shiny New Website

Finally, the Omnibug website has been completely revamped with a new design & content. Over the next few weeks, more help articles and blog posts will be added to help you navigate the new Omnibug.

I Need YOUR Help!

There's a lot of change in this update and I know all too well that not everybody will like the changes. I'd love to hear your thoughts, good or bad! I've setup a Google Form to collect feedback, so if you have any thoughts, comments, questions, or suggestions, please drop me a note! Additionally, if you're a vendor that wants their marketing tool added, or you're a developer that wants to help out, please check out the contributing page.

Whew! That was a lot to cover, and I'm very excited to finally see version 1.0 make it out to the public. You can learn more about Omnibug, check us out on GitHub, and follow us on Twitter!