Show HN: Monitorbook – Easily track anything on the web
monitorbook.com
Show HN: Monitorbook – Easily track anything on the web
1–10 of 56 posts
Re: Show HN: Monitorbook – Easily track anything on the web
#2Re: Show HN: Monitorbook – Easily track anything on the web
#3Re: Show HN: Monitorbook – Easily track anything on the web
#4So... what does it do? I don't wanna sign up to figure out, in more specific language, what exactly it tracks. Users? News? API calls?
Re: Show HN: Monitorbook – Easily track anything on the web
#5So... what does it do? I don't wanna sign up to figure out, in more specific language, what exactly it tracks. Users? News? API calls?
it's a bookmarklet that identifies some portion of the screen to scrape (a numerical value in the example), and tracks it over time, allowing you to set alerts at thresholds (presumably so you can buy at a favourable price)
Re: Show HN: Monitorbook – Easily track anything on the web
#6So... what does it do? I don't wanna sign up to figure out, in more specific language, what exactly it tracks. Users? News? API calls?
Re: Show HN: Monitorbook – Easily track anything on the web
#7Overall, I think it looks pretty clean. But I would probably add just a bit more information on the main page. I see it's mostly in the video, but it would be nice to get pricing details, description of exactly what things you can track, etc..
Good job though :)
Re: Show HN: Monitorbook – Easily track anything on the web
#8I operate a string of ~60 local businesses that have physical storefronts.
On average each store has 5 local competitors.
Our customers are VERY price sensitive - they will almost always call the "lowest price" guy in the area first.
As a result we currently have a duct-tape system to monitor competitor pricing and tweak ours as fast as possible.
MonitorBook would be a potentially much simpler mechanism to orchestrate this.
If the MB team is reading this drop me a line and we'd be a potentially great case study / early adopter.
Things that would have to work to make this usable long-term:
a) API so we could pull this data into our pricing algo.
b) Clear error-checking confidence - if a site we're monitoring changes their code / display and we miss it, we'd have to go back to duct-tape which is sloppy and labor intensive, but reliable.