1. Why do I have to use Listen API?
Well, you don’t have to. You have two choices:
2. How hard it could be to build a podcast database?
Building a decent podcast database is an ongoing effort.
It's not hard. But it takes time (and money) to build and maintain.
Just like owning a car or a house, the initial expense to buy is way less than the ongoing cost to maintain (e.g., tax, insurance, unexpected costs...).
As a grownup, we all know that.
There are new podcasts & new episodes being produced every second. Actually, there will be more and more podcasts
being produced at a faster and faster speed — we clearly see this trend from our database. To keep your database
up-to-date, you have to run crawlers 24/7.
Of course, you need to pay for servers that run 24/7. You need to run crawlers, host your podcast database, and run
a search engine like Elasticsearch on those servers. Do your own math by looking at AWS
You need to deal with edge cases to make sure your podcast database is high-quality. Let me give you some ideas: 1)
A lot of podcast RSS feeds are malformed. 2) Podcasts change their RSS feeds from time to time. 3) A lot of podcasts are
junk (e.g., machine-generated contents) that you don’t want them to be in your database. 4) Podcasts may change audio urls, which actually happens a lot.
5) You need to deal with duplicate podcasts and episodes.
At first glance, these edge cases seem trivial if you don't have much previous experience working in the internet industry. Oftentimes, you'll learn lessons in a hard way.
Don't worry. We all need to start from somewhere or nowhere :)
What's worse, server outages may happen.
Even Amazon or Google has large scale outage from time to time.
It takes time, energy, money, and expertise to deal with those outages.
Actually, I haven’t mentioned the most expensive part of building your own podcast database: opportunity cost. You
need to decide where to spend your money and your developers’ time: building your own podcast database, or building
your apps. Using Listen API allows you to jumpstart the most exciting part of your project immediately.
3. Are you actively supporting the API? Do you expect to continue to do so?
Yes. Listen API powers our user-facing website ListenNotes.com. Listen API benefits from most backend improvements of ListenNotes.com.
4. If we use Listen API and it goes away in the future…
Your concern is valid. We all know that NOT ANY online services or companies can last forever.
If we decide to shut down Listen API, we’ll give you (at least) 12 weeks’ notice and you’ll be able to buy the latest database dump (all podcasts + all episodes) at a reasonably low price.
It's very likely that Listen Notes will outlive many well-funded startups or even public companies.
I am able to run Listen Notes lean. Unlike other bigger companies, we don't employ tons of people,
so we don't need to pay tons of salaries and it's unlikely that our company will shut down due to internal power struggle.
I'm able to architect the software infrastructure to be robust enough while not wasting tons of money on server bills.
If you've ever worked in any modern internet companies, you know that it's very easy to burn money on servers.
5. Do you provide any support?
Yes. If you have any questions about Listen API, just email [email protected]
Unlike talking to an average customer service guy in other lame companies,
you talk to me directly. I'm the founder and CEO of Listen Notes, Inc.
and I'm the person who built this whole thing by hand & by heart.
For API users, I reply emails almost instantly when I'm awake. "We are not a large House, we are a proud one"