4 ms·
> An API for lists. I've written a few microservices for listing-lists, getting list-members, which generally just serve the contents of a JSON/YAML file. I'v
by stevekemp 10y ago
> An API for lists.
I've written a few microservices for listing-lists, getting list-members, which generally just serve the contents of a JSON/YAML file.
I've done it often enough that I can see the value in a list-server, but equally it's something I'd struggle to see monetizing well, or even at all. How do you plan to handle that?
(Because in the worst case you can just be lazy and embed your list-data in your application itself as a lazy-loaded YAML file which is parsed on each request.)
- callmeed 10y agoYeah, I often use the YAML or PList approach myself. My initial pricing experiment will be something like: 1. Buy any single list one-time for $9 (as a JSON/YAML/PLIST download) 2. Pay $49 per year for API access to all lists
- stevekemp 10y agoThat's an interesting pricing model, thanks for sharing. I guess the key to drive subscriptions would be to ensure that your data-sources were updated constantly (where appropriate). I know in the past I've struggled to handle updates to things like UK postal-codes, where additions are frequent and omissions lead to errors being presented to clients.
- callmeed 10y agoYeah, good updates are important but something I think can be mostly automated. BTW, if you're interested in teaming up on it at all, by all means get in touch. I'm never opposed to a capable partner.
- stevekemp 10y agoI think the programming side is trivial enough that you'd probably not benefit from my help/involvement. The harder part is gathering accurate data, working out what lists users even want, and the promotion of the service/site. These last parts are the ones I'd struggle to be useful at.