Originally created by @p18dh28ejfi on GitHub (Sep 7, 2025).
Describe the Feature/Enhancement
Description:
The in-app reader in the Audiobookshelf Android app suffers from significant usability issues that degrade the reading experience:
Unintuitive and Cramped Menu Navigation:
Buttons and menu items are too small and tightly packed, making them difficult to tap accurately. This leads to frustration, especially on smaller mobile screens, and increases the risk of accidental taps.
Missing Basic Customization Features:
No Font Customization: Unlike the web interface, the Android app does not allow users to change the font type or size. This limits accessibility, particularly for users with visual impairments or reading preferences.
No Text Alignment Options: There is no way to adjust text alignment (e.g., left, center, justified). This restricts readability and forces users into a one-size-fits-all layout.
Impact:
The current design makes the app feel unpolished and less functional compared to the web version.
Users who rely on customization for readability or accessibility are forced to use the web app instead, defeating the purpose of a dedicated Android app.
Why would this be helpful?
These changes would align the Android app with the web version’s functionality and significantly improve usability, accessibility, and user satisfaction. A more intuitive and customizable reader would make the app more competitive and user-friendly.
Future Implementation (Screenshot)
To address these issues, the following improvements are needed:
Redesign Menu Navigation:
Increase the size of buttons and menu items.
Improve spacing to reduce accidental taps and make interactions smoother.
Add Font Customization:
Allow users to select from a variety of fonts (e.g., Serif, Sans-Serif, Dyslexia-friendly).
Include a font size slider or dropdown to adjust text size dynamically.
Add Text Alignment Options:
Provide options to align text (left, center, right, justified) to match user preferences.
Audiobookshelf App Version
Android App - 0.10.1
Current Implementation (Screenshot)
No response
Originally created by @p18dh28ejfi on GitHub (Sep 7, 2025).
### Describe the Feature/Enhancement
**Description:**
The in-app reader in the **Audiobookshelf Android app** suffers from significant usability issues that degrade the reading experience:
1. **Unintuitive and Cramped Menu Navigation:**
- Buttons and menu items are **too small and tightly packed**, making them difficult to tap accurately. This leads to frustration, especially on smaller mobile screens, and increases the risk of accidental taps.
2. **Missing Basic Customization Features:**
- **No Font Customization:** Unlike the web interface, the Android app does not allow users to change the font type or size. This limits accessibility, particularly for users with visual impairments or reading preferences.
- **No Text Alignment Options:** There is no way to adjust text alignment (e.g., left, center, justified). This restricts readability and forces users into a one-size-fits-all layout.
**Impact:**
- The current design makes the app feel **unpolished and less functional** compared to the web version.
- Users who rely on customization for readability or accessibility are **forced to use the web app** instead, defeating the purpose of a dedicated Android app.
### Why would this be helpful?
These changes would align the Android app with the web version’s functionality and significantly improve usability, accessibility, and user satisfaction. A more intuitive and customizable reader would make the app more competitive and user-friendly.
### Future Implementation (Screenshot)
To address these issues, the following improvements are needed:
1. **Redesign Menu Navigation:**
- Increase the size of buttons and menu items.
- Improve spacing to reduce accidental taps and make interactions smoother.
2. **Add Font Customization:**
- Allow users to select from a variety of fonts (e.g., Serif, Sans-Serif, Dyslexia-friendly).
- Include a font size slider or dropdown to adjust text size dynamically.
3. **Add Text Alignment Options:**
- Provide options to align text (left, center, right, justified) to match user preferences.
### Audiobookshelf App Version
Android App - 0.10.1
### Current Implementation (Screenshot)
_No response_
As a possible alternative allowing opening books in external apps by default would open up the possibility for users to decide which app has the best feature set for their needs.
@Oxika95 commented on GitHub (Sep 9, 2025):
As a possible alternative allowing opening books in external apps by default would open up the possibility for users to decide which app has the best feature set for their needs.
@Oxika95 That's a nice feature, but I bet the reading progress won't be tracked by ADS (for external reading apps).
Currently I only see only one client app for ADS which supports ebooks (litlyric).
@p18dh28ejfi commented on GitHub (Sep 9, 2025):
@Oxika95 That's a nice feature, but I bet the reading progress won't be tracked by ADS (for external reading apps).
Currently I only see only one client app for ADS which supports ebooks ([litlyric](https://github.com/shane9b3/LitLyric---Beta)).
More of a recommendation for a stop gap solution. I completely agree with you on the desire for a much more robust reader. I use ABS as a file downloader rather than a reader because of how feature poor the reader is.
@Oxika95 commented on GitHub (Sep 9, 2025):
More of a recommendation for a stop gap solution. I completely agree with you on the desire for a much more robust reader. I use ABS as a file downloader rather than a reader because of how feature poor the reader is.
If ADS doesn't offer significant added value, what is its purpose? I could just as well install Syncthing and synchronize all my podcasts, audiobooks, and ebooks with my server (assuming I have enough storage space, which I have with a SD card slot).
The main argument for ADS is the shared and stored reading or listening progress (for me at least).
@p18dh28ejfi commented on GitHub (Sep 11, 2025):
If ADS doesn't offer significant added value, what is its purpose? I could just as well install Syncthing and synchronize all my podcasts, audiobooks, and ebooks with my server (assuming I have enough storage space, which I have with a SD card slot).
The main argument for ADS is the shared and stored reading or listening progress (for me at least).
Well Audio Book Shelf is primarily focused on Audio books. Most of its features and development are focused there. The Community has been asking for better ebook features for a while now but development doesn't seem focused there at all. Most recommendations for ebooks get filed away for future review.
I think it is far more likely that a third party app will be developed with the features we want using the API before the devs get to it. Short term you may be right, syncthing or another sync solution might be a better for your use case. Right now the features are just not there.
@Oxika95 commented on GitHub (Sep 11, 2025):
Well Audio Book Shelf is primarily focused on Audio books. Most of its features and development are focused there. The Community has been asking for better ebook features for a while now but development doesn't seem focused there at all. Most recommendations for ebooks get filed away for future review.
I think it is far more likely that a third party app will be developed with the features we want using the API before the devs get to it. Short term you may be right, syncthing or another sync solution might be a better for your use case. Right now the features are just not there.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @p18dh28ejfi on GitHub (Sep 7, 2025).
Describe the Feature/Enhancement
Description:
The in-app reader in the Audiobookshelf Android app suffers from significant usability issues that degrade the reading experience:
Unintuitive and Cramped Menu Navigation:
Missing Basic Customization Features:
Impact:
Why would this be helpful?
These changes would align the Android app with the web version’s functionality and significantly improve usability, accessibility, and user satisfaction. A more intuitive and customizable reader would make the app more competitive and user-friendly.
Future Implementation (Screenshot)
To address these issues, the following improvements are needed:
Redesign Menu Navigation:
Add Font Customization:
Add Text Alignment Options:
Audiobookshelf App Version
Android App - 0.10.1
Current Implementation (Screenshot)
No response
@Oxika95 commented on GitHub (Sep 9, 2025):
As a possible alternative allowing opening books in external apps by default would open up the possibility for users to decide which app has the best feature set for their needs.
@p18dh28ejfi commented on GitHub (Sep 9, 2025):
@Oxika95 That's a nice feature, but I bet the reading progress won't be tracked by ADS (for external reading apps).
Currently I only see only one client app for ADS which supports ebooks (litlyric).
@Oxika95 commented on GitHub (Sep 9, 2025):
More of a recommendation for a stop gap solution. I completely agree with you on the desire for a much more robust reader. I use ABS as a file downloader rather than a reader because of how feature poor the reader is.
@p18dh28ejfi commented on GitHub (Sep 11, 2025):
If ADS doesn't offer significant added value, what is its purpose? I could just as well install Syncthing and synchronize all my podcasts, audiobooks, and ebooks with my server (assuming I have enough storage space, which I have with a SD card slot).
The main argument for ADS is the shared and stored reading or listening progress (for me at least).
@Oxika95 commented on GitHub (Sep 11, 2025):
Well Audio Book Shelf is primarily focused on Audio books. Most of its features and development are focused there. The Community has been asking for better ebook features for a while now but development doesn't seem focused there at all. Most recommendations for ebooks get filed away for future review.
I think it is far more likely that a third party app will be developed with the features we want using the API before the devs get to it. Short term you may be right, syncthing or another sync solution might be a better for your use case. Right now the features are just not there.