trotzke
I think this is a big step in the right direction for Stripe (unclear pricing aside). We’ve been thinking about usage based billing for a long time now. We built a bunch of apps using Stripe and found there was a lot missing if you wanted to track activity and bill for it, as well as with reporting and revenue optimization. Having not dug into the platform too far, this definitely looks like it could fill some gaps.
I will say I’m not a fan of taking a percentage for billing on top of taking a percentage on payments, though. There is risk involved for payments (chargebacks, fraud, etc), but billing is transactional. A percent there feels like a money grab to me.
The only other problem I see with this is that it all seems a bit convoluted. I get that it has to be tacked on to their existing platform. But we’ve found that the secret to an awesome usage based billing system was to track activity in real time, then apply automated billing to that tracked activity. It’s a different approach and we’re working on polishing that up and bringing it to market over the next few months.
Would love to hear more about how folks are thinking about consumption and usage based billing and pricing. I think it’s the next big wave in Internet monetization, so it’s important to get right.
Subscription Billing in 5 Minutes
New Pricing and PayPal X for CheddarGetter
We also use Facebook, twitter and linkedIn extensively for research. If we're interested in an app we immediately look up entrepreneur's profiles. If we know them it reminds us how. If we don't, we find common connections and get some context aout what they are about.
I don't think we could do what we do, at the scale that we do, if social media didn't exist.
BTW... we're missing you out at Big Omaha this year.
1. The ads were too much for sure. When each ad was made it didn't seem too bad, but once all the dancing was on the page at once we knew it wasn't going to work. Unfortunately it was one of the last things we put in before launch (3 days ago). Given all the traffic, we've been focused on making sure everything stayed up an running. Today we put some temporary static ads up while we're redesign them.
2. Not a bad suggestion, but I like being able to bookmark the app. Long term we'd like to be more a competitor to desktop text editors. A bookmark directly to the app that isn't tied to only one share made sense to us, particularly in like a Fluid or Chrome OS type use case.
3. We definitely want to tie in with version control. The challenge is in doing it elegantly without forcing a particular VCS on someone. We've got some ideas on this we want to implement in the future.
Thanks for the feedback.
The next direction for Squad is better project handling via a tree file browser, SFTP, version control hooks, etc. not adding formating buttons or making shares embedable. I think Squad and EtherPad were diverging like say Dreamweaver and Word. That's not to say we wouldn't like to capitalize on both the Dreamweaver and Word markets. :)
Here is my suggestion, I say you (or someone else passionate about this) go over to http://sproutbox.com/apply and fill out an app for recreating something like EtherPad. If you're selected, you'd be working with the same team that built Squad. We'd donate a big chunk of real-time editing code and you'd have something up around the time EtherPad shuts down. Win Win.
But hurry, apps close tomorrow at 11:59pm.
Squad serves a great purpose for developers working together on code, but it isn't embedable, and doesn't do wysiwyg text formating. It's focused on syntax highlighting and opening and saving local files. So for some it may be an alternative, but not for everybody.
The goggle wave everyone type at once stuff is like reverb in the 80's if you ask me. Too much.
Particularly when you are dealing with multiple tabs. What I want to do when I'm asking a buddy to take a look at or help me with code is see what he or she is doing.
The tool really wasn't designed to compete with/replace Etherpad. It was designed to make our lives as developers a little easier. I think Etherpad is awesome. I've used a ton for google docs type stuff, but never really thought of it as code editor.
All that could maybe be done in an interface outside of a standard Wave client. But not being able to follow where someone is editing makes it hard to use for instruction or code review.
We ended up just creating a different kind of interaction that we think works a lot better for working with code.
I'd love some non softball comments/feedback. So fire away.
Oh..and Thanks. Lot more to come soon.
Startups: Hold on for one more day
Linda sounds like the problem not basecamp. If Linda was doing a good job she would have researched problem and turned up Harvest-- at least as an option to try.
Instead she fell into the 'this is the way it's been done before mindset', that doesn't recognize the benefits of collaboration or web services.
In my experience, Linda's approach may make her feel like every penny is accounted for, but that will only be true in her books. Everyone else will be left with a print out of a week old, outdated gantt chart, and less certainty about what to do.
Nearby shelf: The Design of Everyday Things, Maverick, Founders at work, A Brief History of Time, A Pattern Language, Peopleware, Made to stick, Web Standards Solutions, Designing Interactions, The Pragmatic Programmer, The Mythical Man-Month, Oh, the Places You'll Go!
Other good reads: Blink, Tipping Point, Long Tail, Freakonomics