We're currently implementing invoice payments with the new Stripe button over at Paydirt (https://paydirtapp.com).
One little issue: in Chromium 20.0.1132.47, the button renders with a line break and overflows the iframe like this: http://imgur.com/88st1
The same page renders the button fine in Firefox and other Chrome browsers I checked. Adding `white-space: nowrap;` via the Chrome inspector fixes the problem.
I'm tristan[ at ]paydirtapp.com if you need it replicated.
The magnifier was built for us by the super talented @taybenlor. You should tweet him to tell him you like it :)
That SO post is pretty thorough!
Yep, it's a canvas element with rounded corners moving around on top of a fairly stock-standard slideshow. It uses a css transform to scale and this stackblur library (http://www.quasimondo.com/StackBlurForCanvas/StackBlurDemo.h...) to make it look like it lifts as it moves from place to place.
Exactly. There are many ways to alienate potential users (missing languages, missing features, etc). In the early stages we've learned the importance of focussing on the biggest bottlenecks first.
That's good point. Taken on board, and we'll improve the page to encourage IE users to let us know. It's very true that things might change which would require us to change our tack, but as a bootstrapped startup with a hundred things requiring attention, IE support has taken a back seat.
You're right. My recent encounters with IE9 have been pleasantly surprising (and I bet IE10 will be quite competitive), but for us the numbers are so low that, at least for now, a broad sweep feels OK.
True, it's really just a spin. It's a benefit for most of our users because we can use the time more productively to improve the product and support in other ways. In the zero sum game of the 24 hour day, an hour saved is an hour earned.
Thanks for such a candid telling of the Adioso story. Certain parts ring so familiar it's uncanny. Just as you got a boost from hearing that Airbnb had some tough times before the tide came in, we find it encouraging to hear how you've had to battle the odds. Staying tuned for part 2...
Very wise. This post is by no means a prescription for everybody. We're lucky that our demographic tend to use stronger browsers. Actually, when I exclude blog traffic the IE percentage drops further. :)
It's a good thought, and an area that's ripe for all sorts of standardisation. My passwords follow a system which is secure, but doesn't conform to all the password requirements of all sites, so I get caught out with this problem all the time.
Hey cool! We're a team of two so I'll be trying this out for sure. Your landing page lured me in perfectly. By the way, your <article> tags are rendering with a white background-color, but I assume they're meant to be transparent/#202020. I'm using FF 7.0.1.
Great site, but I found the interface very confusing. It took me ages to figure out what to do next at every step. The resizing text is an ok idea, but currently it's more distracting than guiding. Hope that's helpful. :)
It's funny how when you're working on something every day you can miss such gaping oversights. Yes - foreign currencies (including Bitcoin) are supported, and you can create multiple customized taxes which are automatically calculated and totaled for the invoice - but there's no indication of that on the home page. An important point.
Regarding price, you may well be right. I'd be lying if I said we weren't testing the waters on price, so it's good to hear some explicit thoughts on the matter.
Which is tougher: pricing higher now for the future features or starting low and having to raise prices (which nobody likes) later?
Top work!