And if it fails, it's at least worth it to learn why it failed. Was the UI bad? Did it not promote the service in the right way? Did users not understand the purpose of the tool?
I think the juice is worth the squeeze.
And if it fails, it's at least worth it to learn why it failed. Was the UI bad? Did it not promote the service in the right way? Did users not understand the purpose of the tool?
I think the juice is worth the squeeze.
2. Get it working well with UI, UX, etc....
3. Then integrate it into the browser.
Seems like a totally logical flow to me.
When Firefox warns you that you're (possibly) pwned when you browse to a website or try to log in, then you can't get around combining step 2 and 3.
Or when Firefox compares your password database with HIBP, you can't get around combining step 2 and 3.
Firefox Monitor is just a page on the official Mozilla website.
>The site will offer recommendations
Now, the screenshot doesn't have a URL in the address bar, suggesting it might be a built-in special page. But it also has a generic "Page title" in the tab title, so it looks like a modified stock image rather than an actual UI screenshot.
The screenshot on Troy Hunt's blog does show "https://www.mozilla.org/firefoxmonitor", but it's otherwise the same screenshot with the same generic "Page title", so it's probably equally fake.
(I tried to look for the actual bugzilla bug for this for more info, but didn't find anything.)
(Disclosure: Although I work at Mozilla, I have not worked on Firefox Monitor)