586 karma · joined April 25, 2010
www.BoardGameTables.com
@RoyalsUmp (and every other MLB Team Ump) - Did an MLB umpire make a bad ball/strike call? Tweets when umpires make bad calls.
You need to explain what problem you are fixing and how your product fixes it if you want to get any traction. People aren't going to signup if they don't know what they are signing up for.
The real kicker was when you asked for my credit card right away. I am a big fan of credit card up front on subscription services with a free trail. But I just wanted to see the product. There ins't anything for me to be excited about yet. Luckily I noticed that I could just click something in the menu to skip this step. I would put of asking for the card until you they go to make a purchase. You have my email address so you can already follow up if I abort at the CC step later.
There is a move history, but you have to expand it.
https://twitter.com/MajorLeagueUmp
https://twitter.com/YankeesUmp
https://twitter.com/DiamondbacksUmp
https://twitter.com/OriolesUmp
https://twitter.com/WhiteSoxUmp
https://twitter.com/IndiansUmp
https://twitter.com/RockiesUmp
https://twitter.com/MarlinsUmp
https://twitter.com/DodgersUmp
https://twitter.com/BrewersUmp
https://twitter.com/AthleticsUmp
https://twitter.com/PhilliesUmp
https://twitter.com/PiratesUmp
https://twitter.com/MarinersUmp
https://twitter.com/CardinalsUmp
https://twitter.com/RangersUmp
Most sites use iframe for embeded widgets for this reason.
I think Stripe's checkout doesn't use iframe. They just define every single style with very specific rules. From what I remember.
That is a positive sign, but they aren't customers. It seems like 2,00 people logged in and then found out the product wasn't what they were expecting.
I know this was the case for me. I signed up hoping for a really nice online IDE. I found a bunch of ssh stuff that made no sense to me.
It might be worth talking to the 2000 people and finding out why they signed up and what type of product they were hoping to find.
Email me at chad@brombone.com if you want to talk details.
Steve Pavlina was the first place I heard of this method. http://www.stevepavlina.com/blog/2005/05/how-to-become-an-ea...
Actually, my first thought was that Melancholia might have been 450 minutes long. Because it felt that long when I watched it.
It's a service that solves SEO for javascript driven websites.
For the most part, Google can't crawl sites that manipulate the DOM using javascript (AngularJS, Backbone.js, Ember.js, etc). The solution is to use a headless browser to make html snapshots for all your pages and serve those to Google instead of the page that requires javascript.
This turns out to be a bit of a pain in practice. So, BromBone does it for you. It generates, hosts, and updates the html snapshots. When Googlebot visits your site, you proxy the snapshot from BromBone and serve it to Google. Now Google can see the same thing your users see.
You can get it faster than 15 seconds, but you can't really get it fast enough. We precache everything. I would strongly recommend against trying to process the pages in realtime.
However, from working with customers of BromBone, I know this. People have javascript powered webpages that were not getting indexed by Google. Google would crawl the page, and see no content. The pages were not in Google. After creating prerendered snapshots and serving them when the _escaped_fragment_ parameter was present, the pages showed up in Google.
You are right about one thing, it is a pain to setup. Much harder than it sounds at first. After doing it a few times, I finally got sick of it and built http://www.BromBone.com. It's a service that takes generates the html snapshots for site owners and keeps them up to date. I hope it will let site owner keep all the positives and eliminate most of the new negatives.
I've never seen an example where Google crawled a page and included content that was loaded via ajax or an external javascript file. I have seen Google index content that is loaded from a script tag included in the html page.
Google has documented this method here: https://developers.google.com/webmasters/ajax-crawling/
I have made a service that takes care of this for javascript sites that don't want to mess with maintaining this system themself. http://www.BromBone.com
Heroku, Firebase, NodeJS, javascript
Create a Heroku add-on created for our SaaS.
BromBone (http://www.brombone.com) is a service that makes client-side javascript driven websites (AngularJS, Ember.js, Backbone.js, etc) crawlable by Google. We process all the websites pages with PhantomJS and save the result. When Google crawls the page, the website just has to proxy the snapshot from our server and send the file to Google-bot.
We need to create a Heroku add-on so that people can signup for BromBone form within Heroku. This process is well documented by Heroku.
Currently BromBone does have any login/auth system for users. The project would also involve creating that system. Probably using Firebase's Auth system, although this is still up for discussion.
Willing to work with someone working nights and weekends, or with someone who wants to knock it out quicker working full days. Would prefer to per project or milestone payments rather than hourly.
The ideal candidate is someone who has previously created a Heroku add-on and/or used Firebase's Auth system. However, that is not a requirement.
If you're interested, please email chad@brombone.com
I agree. The learning curve can be steep, but I've really enjoyed using Angular.
We've done Twitter and not Facebook because we are marketing to developers and IT/Eng Managers. I think they are more like to follow accounts about the tech they use on Twitter rather than Facebook.
To give you an idea, for http://www.BromBone.com we target the followers of just one account. The people who follow this account are very likely to find our service useful. Overtime we will expand to other accounts. We spend just $5 per day, and that will bring us about 20-25 visitors per day, plus a new follower or a retweet every once and a while. Our ads started running within 24 hours of setting up our account.
This probably won't scale well enough to get all the customer you need, but it can give you a starting point. It can allow you to collect some potential customers email addresses so that you can talk to them and figure out what they need. Or maybe no one signs up at all. In that case you need to make some bigger changes.