theonna, you're making the assumption that a file browser is a default technology. It's not. If a pre-existing plugin, it must be integrated. If a new piece of software it must be designed, developed and integrated.
All of which adds up to time, and in sixteen years of life in high tech I have never heard of a dev team with enough time to do everything.
So, given that Kobo has adopted database as their file location method... why waste the time on a file browser? The more logical course is to spend the time improving the database experience... or implementing other features they feel will drive people towards purchasing their product.
Sufficient demand will get a company to implement just about anything. Given that even Amazon, the undisputed worldwide leader in e-reader tech, hasn't seen sufficient need to implement a file browser system with directories/folders... why in the world would anyone else see it?
|