Why webcompat.com should do better + a proposal

I really like the webcompat project‘s idea: to allow all users to be able to report bugs on all websites and in all browsers. Let’s take a step back: What are the 3 main problems with bug-reporting in general?

Most of the users are not-so-tech savvy.

It’s true. They know something is wrong, because the website is not working for them, but they don’t know why is that or how to report it. Imagine if they could use the tools they are familiar with to report bugs and to give the developers the data they need without even realizing it. Cool huh?

“It’s working for me”

Thanks to different browsers, standards and different developers a website that one user sees can be completely different for another user. Agreed?

You can imagine the questions the user must answer:: “On which page are you?”, “What are you doing exactly?”, “Did you select something wrong?”, “Did you write a number in your street address as requested?”, “Are you logged in?”, etc.

It’s an option too: the developer (or a QA) will say to the user “It’s working for me”, meaning to the end user - you are doing something wrong, John or Jane, it’s not the website. it’s you.

The end user doesn’t know how to fill-in bugs into bug tracking systems

Majority of the people that can find a bug don’t know how to report it or why to report it.  Most of the companies or projects have 1-2 page howto’s attached to the bug reporting form, but the result is still questionable.

 

The WebCompat way: Now

Webcompat will give all users a brand new way to report bugs. It will also provide for a community which will be able to easily find fixes for the bugs or alternatively, contact the website owners and report them.

There is still one problem with that. The users are still missing the tools which they are familiar with to report bugs. The developers (community of fixers) are still missing the vital information about fixing the bug.

 

The WebCompat way: Upgraded

We can fix that!  Being part of Usersnap’s mission to make this process easier, I can propose a solution and being a Mozillian for almost a decade I believe this will help millions of users to report bugs and to make the web a better place – this is why Usersnap has been created for.

The ideal set of information to fix a bug from the developer’s perspective:

usersnap_ui

  • Obviously, a report of what exactly is not working
  • Information about the plug-ins installed in the browser
  • OS and browser version, at a minimum
  • JavaScript error log and the XMLHttpRequest Log  in case there are problems (we still don’t know that). The worst thing about client-side JavaScript errors is that they happen on the client side, which is a cruel place far away from the developer trying to fix this error.
  • It would also be great to know what the user did BEFORE the error (yes we can do that)

Wouldn’t it be awesome if we could have this information to every bug report, collected automatically.

 

Push to gitHub

And what is the best part of this? All data goes directly to your bug tracking solutions – in this case gitHub and everybody is happy.

10 things every startuper must know about e-mail marketing and will not find anywhere else.

This mini-book has been staying for at least 2 months in my backlog waiting to be pushed online. It’s time has finally come. I know there are millions of mini-books like that, but this one is different, because it shows things that I’ve learned from my experience working in startups and with communities from 20 to 1.4M e-mail holders.

Let’s get started!

 Email marketing is not dead

Admit it, it feels really good when you open your mailbox and you find some good news or nice offers waiting for you. You can even find them within the rest of your e-mail messages full of winning the lottery notifications to offers to enlarge some things or mail from … the FBI. Oops!

It’s not dead at all! It is getting worse but it’s still kicking.

 

The rest 9 things with a lot of links, examples and free updates are available in my mini-book that can be purchased from Amazon by clicking here.

  • Spam checking: Content
  • Spam checking: Your Servers
  • Spam check: Filters
  • Ask to be whitelisted
  • Don’t care about open rates, do care about CTR
  • CTR are useless if you don’t track conversions
  • Segmentation
  • Buying e-mail lists
  • Searching e-mail lists online

How to simplify the WordPress development processes which involve clients

I had a period in my life when I was working for different employers like a freelancer developing wordpress plugins, themes enhancements and some integrations.

Back then I didn’t realize how much time I was spending in communication with the clients or the middle man (project manager), because, let’s be honest – time is money, right. I didn’t mind to spend 3-4 hours talking to a client about how to make the red button, even more red or why the image is not aligned with the little horse. They would pay me anyway. You know what I mean.

After I started expanding my business portfolio I realized that “spending time” from the previous paragraph is actually losing time. Instead of working for many clients and getting more opportunities (more money) I was working just for a few.

This was one of the reasons for which I decided to move to another segment of my professional life. True story!

Continue…