separate app for Legamus and/or Life+70?

[ScottLawton]

I recently released an alternate LibriVox catalog http://aplt1.com/ on the Web, and (separately) an iOS app that I think is a little more user friendly for locating and playing LV books. It's free and currently with no ads. http://appletfab.com/aplt1.html (I'll create an Android version at some point.)

I've been thinking about Legamus, including the old thread about publicizing the great work that's done here. I realize that the 'LibriVox' app from bookdesign.biz includes Legamus books, but Legamus doesn't really stand out there.

I could create one or both of the following:

- A dedicated Legamus app with the 61 (and counting) books
Pro: helps publicize the Legumus name
Con: limited selection

- A Life+70 app that has Legamus books plus the (large) subset of LV that is in Europe's public domain

Of course I can do what I like with public domain works, but I wanted to discuss with the community here what you might like to see (if anything!).

Thoughts? (Here is fine ... or PM or email.)

Cheers,

Scott
(In the USA, but since I wouldn't actually listen to the Legamus works, I think I can navigate the legal issues.)

[J_N]

Thank you for your efforts Much appreciated... the easier the access the more people can benefit

However, I am not entirely sure if either of your suggestions would work well... Legamus is probably not that well known to attract many users to an app specific to it only and I don't know how many people actually know (or are conscious of) the legal status on copyright in their country and would go searching for an app complying with it... a lot of people download music illegally (knowingly!) - I don't think people nowadays are all that bothered about copyright...

Don't know how difficult it would be to just add an option to your current app for limiting search results to 70+ if people want to...

[ScottLawton]

Legamus is probably not that well known to attract many users to an app specific to it only and I don't know how many people actually know (or are conscious of) the legal status on copyright in their country and would go searching for an app complying with it...

Likely true on both points. But, if a potential listener searches the app store for 'audiobooks', would they be attracted to something like:
- Legamus App: 61 free audiobooks for the EU
- Legamus Plus for Europe: 7000+ free audiobooks

Or, to the extent it's better NOT to use the Legamus name for an independent app:
- Aplt1 Europe: 7000+ free audiobooks

I'm just brainstorming; I don't have any firm conclusions.

[Viktor]

Hello Scott,

thank you very much for your kind thoughts, much appreciated! Our books are indeed not very visible in the mobile world, getting them added to catalogues like yours is great. If you feel anything could be made better for importing our data, such as a database dump or an API sending out JSON, just tell me.

I feel that it's our content that needs more visibility, rather than our project name. We are a (much smaller) complement to LibriVox, not a competing project. So I think, for an independent app, an independent name would be best.

I agree with Julia that the best "user experience" would be one big catalogue / app for any one reader that also shows our books where appropriate. Whether that's two apps, one for the US (and similar legislations) and one for the others, or one single app that lets the user make the selection (maybe even through geolocalisation or environment variables) - you're the best for deciding that.

All the best,
Viktor.

[ScottLawton]

If you feel anything could be made better for importing our data, such as a database dump or an API sending out JSON, just tell me.

Well, it's not that much work for me to parse the HTML of http://legamus.eu/blog/?page_id=161 ... but of course a JSON file or csv would be even easier if you get a chance. No rush -- I'm still in the planning stage.

Parsing individual pages is more work for me (especially since I need to go a second level deep to get the individual mp3 links), though also not a big deal.

So I think, for an independent app, an independent name would be best.

That makes sense to me -- especially from the perspective of a listener. (In fact, I think it's unfortunate that LibriVox didn't preserve and enforce their trademark. It's confusing to have an app named LibriVox that is independent.)

At the moment, my app just links directly to archive.org mp3s. Can I do the same here, e.g. to http://listen.legamus.eu/woolf_orlando/ ... _woolf.mp3

Any problems with streaming? From Safari, an archive.org mp3 plays directly, whereas legamus.eu mp3 came as a download. But, not sure if my app will do the same thing...

Scott

[Viktor]

Hello, sorry for the late answer.

Here's something that works right now and that I did for the first mobile app that contacted us. Maybe you find it useful, maybe not. Most audiobook downloads link to http://listen.legamus.eu/<author>_<title>. Even for the oldest downloads, that seem to send the user to other sites, such a page exists. In the HTML of each "listen.legamus.eu" page, you find a big chunk of JSON at the end, in the <script id="LegamusAudioPlayer_json">. This chunk of JSON contains "mobile_url" links for each section. It's MP3 with reduced bit rate, 48 kbps instead of 128.

Yes, you can link directly to files. All URLs on that server are controlled by us, and we'll try to keep them working. But HTTP 301 or 302 redirections might appear one day; it would be good if your app could follow them.

Absolutely no problems with streaming. The fact that browsers try to download, that's certainly due to the HTTP headers (Content-Type and Content-Disposition) - it's up to your app what you do with them. Concerning streaming for the end user, all is done by said listen.legamus.eu HTML pages. They even try to work through Flash or Java plug-ins, if HTML5 <audio> won't do.