|
|
|
|
|
by LanternLight83
1580 days ago
|
|
I agree, but would add that nailing these features doesn't excuse a reader without sufficient support for customization of the UI (especially content). I might be able to excuse a reader with a polished, clean, and opinionated design (like Apple & Google's eBook readers), but would prefer to have as much freedom as possible, to the point of user-stylesheet support or some such low-level measure. Bonus points for features easing the manipulation of such 'profiles', such as a simple theme selector for easy swapping between an arbitrary number of custom styles and support for per-feed defaults. Not to mention accessibility features, which readers are well positioned to support. Not to be too picky, these are my ideals and I wouldn't so blutly demand such feature coverage from a developer. Y'all do what you think is best and I'll find what works best for me, thx to amyone who's contributed to a reader c: |
|