Ask HN: Launching an MVP vs Browser Compatibility

I've been building out our MVP for a social fitness game (social, questing, loot, rewards etc) and am very close to going live with it. However, we have a number of browser specific bugs that make using our site less than the entertaining and interactive experience we're targeting. We're pretty much good in Chrome, and mostly good in Safari, however mobile Safari and IE 9+ have some usability/functionality issues.

I could spend weeks getting all browsers perfect before launch, but I'm very excited about releasing to the wild and am flip-flopping on releasing our MVP vs getting it 100% working in all major browsers.

Where do you stand on MVP vs Browser Compatibility? Is it good enough to display a nice "Hey, we're working on your browser, but try Chrome if you want it to work" while working like mad to release updates that fix other browsers? What have you done in the past for your MVP? Where did you draw the line?

Our product is NeuFit, www.neufit.com and we're hoping to start inviting people that have signed up on Tuesday while we're at TechCrunch Disrupt. If you're planning on attending, come say hi!