SUGGESTION: Informational Post Permanently 'Stickied' at the Top of the Mobile App Subforum
I suggest the following post be made as an official, permanent notice, stuck to the top of the Mobile App subforum:
Subject: "These Two Functions Will Never Be Implemented"
Post: "Personal Book resource synchronization and Read Aloud ('native', or built-in, text-to-speech) will never be implemented in the various Logos Mobile Apps."
This will be a much-needed point of clarification for new users (or new forum readers), who have the completely natural and reasonable expectation that these features from the desktop app might have some analogous, if only rudimentary, functionality on the mobile apps.
The post should be locked, so that ugly kludges, all of them well-meant, won't be suggested.
macOS (Logos Pro - Beta) | Android 13 (Logos Stable)
Find more posts tagged with
Comments
Read Aloud ('native', or built-in, text-to-speech) will never be implemented in the various Logos Mobile Apps."
“The trouble is that everyone talks about reforming others and no one thinks about reforming himself.” St. Peter of Alcántara
perhaps you should be petitioning Samsung rather than FL?
Hi David:
My post might not have been clear (and maybe you're replying to Sine), but I'm not petitioning for these changes to the mobile apps, as I have given up on those long ago. (Although, I do appreciate the quixotic Feedback post on Read Aloud.) What I would like is for Faithlife to let new users know this right up front. I'm sure you've seen the weekly posts asking about these. Rather than having the inquirers Google the forums for the dozens of related posts and try to aggregate a concise outlook (and even getting conflicting reasons: https://community.logos.com/forums/p/126859/862178.aspx#862178 ), a naked statement of reality at the top of the subforum would be more efficient.
macOS (Logos Pro - Beta) | Android 13 (Logos Stable)
That's fine, and it's a fair ask. But aside from FL's "will they or won't they", perhaps it may bear fruit to provide the Android OS manufacturers a request that they add the same kind of functionality (read aloud) that iOS users enjoy. It's worth a shot, I imagine, since there is a competitive angle undergirding their service. Contacting Google and making the request could help attain your ultimate objective.
ASUS ProArt x570s Creator, AMD R9 5950x, HyperX 64gb 3600 RAM, ASUS Strix RTX 2080 ti
"The Unbelievable Work...believe it or not." Little children...Biblical prophecy is not Christianity's friend.
You may have noticed the big green "In Progress" status on that request.
No, actually I didn't. A perfect storm of retinitis pigmentosa, advancing color-blindness, and the Chrome dark mode extension caused me to miss both its greenness and its existence. Thanks, and happy tilting!
Fearing that 'In Progress' is the ugly cousin of 'Gathering Interest', I looked for a legend or glossary (I'm sure it's there, but couldn't find it). However, since I didn't see that many of them, I'll conclude it's not estimate inflation or ad puffery. I'm not spiking the football yet, but am now cautiously hopeful.
My pessimism on mobile Read Aloud was conditioned by years of either 'unh-unh-unh' posts like this one: https://community.logos.com/forums/p/41565/528418.aspx#528418 , or just plain silence.
macOS (Logos Pro - Beta) | Android 13 (Logos Stable)
Fearing that 'In Progress' is the ugly cousin of 'Gathering Interest', I looked for a legend or glossary (I'm sure it's there, but couldn't find it). However, since I didn't see that many of them, I'll conclude it's not estimate inflation or ad puffery. I'm not spiking the football yet, but am now cautiously hopeful.
"In Progress" means "Faithlife is doing this." [:)]
“The trouble is that everyone talks about reforming others and no one thinks about reforming himself.” St. Peter of Alcántara