Would I like a file manager on my reader? Yes. I am more comfortable with navigating through file system. I am also more comfortable with storing documents in a file system because I understand what's going on at that level. The file system + database model always leave me wondering if the database is modified accordingly when I move or remove files, how data is stored in relation to other data within the database, and how to make desired modifications to the database itself.

Would I benefit from a file manager on my reader? Probably not. The existing shell allows me to find books based upon a number of criteria, and sometimes does so better than a file manager could. The shell also allows me to do the only file system operation that matters (i.e. deleting a book when I'm done) and it allows me to modify the portions of the database that matter (e.g. marking a book as read and storing annotations). The only drawback is browsing large numbers of books, but I don't keep large numbers of books on my reader anyhow.

Should Kobo implement this feature? It really depends upon who Kobo is targeting. In Canada, it is seen as a mass market product that is used by the general population. For Canada, implementing a file manager would probably be a bad idea because it would make the product more complex and less desirable. (In case technophiles haven't noticed it, the average user of consumer electronics wants a simple product and rarely goes beyond basic customization.) In other markets, I'm thinking that the perception of Kobo is different because it's a niche product that is bought by consumers who do more research before purchasing and may be looking for certain features. I'm guessing that the whole file manager thing can go either way in those markets.