Hacker News new | ask | show | jobs
by spacemanspiff01 870 days ago
It seems to me that there are 3 independent issues.

1 scanning the books to text.

2 reading text to the user.

3 having a good interface.

Number 1 seems to be where you put the most effort, along with 3.

I guess at least for me, there are often digital copies of books, either in epub or Kindle. When that's available those should be used.

And if it is not available, wouldn't it make more sense to have document scanner to epub?

I guess I'm just thinking that it is relatively rare that you really need to document scanning in order to get an audio book. Since most of the cost seems to be from document scanner side, it seems worthwhile to split them up.

And also seems like it would make sense to think of these as 2 separate products. Specialized document scanning, and audio generation. I can definitely see uses for one without the other.

1 comments

Yes this is a very valid point, on a technical level it's definitely a 2-step thing. From a product perspective I'm framing it as a "this app reads books out loud to you" but if I start hearing about people using it to grab the text out (which is possible right now) I'll definitely consider paying more attention to that use case.