davidsawyer

They still have Behind the Lyrics for some songs on the mobile app, which shows a mix of lyrics and info about the song and artist.

Wow, I hadn't thought of that before! That really is genius.

Did you finish that project yet? If so, would you mind sharing it?

> building the right product trumps building a flawless product.

Y Combinator has been saying this for years, and I couldn't agree more. Niantic will iterate and fix problems, but Pokemon Go would have been doomed from the start if it wasn't what people wanted.

Hey, love the website! Nice, clean, and straightforward.

Just a heads up, I noticed a typo on the membership page: "No need to even look at the gas gauage anymore"

I feel like it would be worth the trade-off.

Stripe's documentation and API design are both the gold standards in my mind. Braintree is good as well, but they fall just a little short of Stripe in almost all categories.

The most notable shortcoming for me has been Braintree's testing/sandbox environment. They require different dollar values in order to trigger certain payment processor errors, and a payment won't fail in their sandbox environment if you use a bogus nonce. This behavior alone caused me to mistakenly ship a placeholder nonce to production, and it took us a while to figure out what was going wrong in production since all purchases worked perfectly in the sandbox.

tl;dr Braintree has burned me, and Stripe has not.

Really cool concept! It would be awesome to put a little gif in the readme of what the interaction is like. Maybe you could use something like https://asciinema.org to record your terminal session?

Just FYI, the "Bro" in the logo looks a lot more like "Bra" to me.

How was your experience using firebase to build the app?

I'd caution not to use commenting as a crutch, though. Code really ought to be readable and easy to follow all on its own. I don't think code should be littered with comments just narrating what's going on, since those can get out of sync easily when code is modified. The code itself ought to be descriptive enough to "tell its own story", so to speak. Comments ought to explain why something is happening if the author feels the code may be unclear.

I think you're right in that a lot of established and independent podcasts will tend to stick to the main channels of podcast distribution, but if it becomes too financially tempting to go through a custom app, they'd probably choose to do that.

There definitely doesn't seem to be a ton of money in podcasting right now. Many of the heavy hitters in that world regularly ask for donations from listeners.