Reading in Logos

I am a new heavy user this year and I know others have expressed the same issues I have had with trying to read a subset of my library cover-to-cover in Logos. The forums are full of posts from especially new users confused on why this functionality is not more simple. These users have usually been pointed to a layout or favorite as a potential solution which is what Logos has to offer currently. I think reading in Logos should be easier and created the following suggestion as a way to improve this functionality. Please vote if agree that this simple function could be made more intuitive.

https://feedback.logos.com/boards/logos-desktop-app/posts/reading-vs-reference-on-resources

Find more posts tagged with

Desktop App

Comments

JT (alabama24)

I agree that having effective syncing would be good... but the primary function of Logos is a "research library." In my opinion, the "fix" is to create a feature called "projects." In a "project," resources would always sync across all devices.

The second part of this is that "layouts" would be transformed to mean what it really should mean: Simply a pattern and/or collection of tiles. A "layout" could be populated with a "project."

Antony Brennan

There are already two functions that support this, one is the general sync and the other is the favourite tool. You can set a book mark inside a resource with the favourite tool.

Whereas the sync is hit and miss the favourite tool almost always works, for me at least. I am thinking it would be better if Logos made these functions more robust end to end rather than add a new function. You should not have to add the resource to a list or a project.

It is right that you mention it. This should just work.

I do agree that this feature needs attention, one way or the other.

Chris Heil

https://community.logos.com/discussion/comment/1318518#Comment_1318518

I agree that having effective syncing would be good... but the primary function of Logos is a "research library." In my opinion, the "fix" is to create a feature called "projects." In a "project," resources would always sync across all devices.

The second part of this is that "layouts" would be transformed to mean what it really should mean: Simply a pattern and/or collection of tiles. A "layout" could be populated with a "project."

I have read your suggestion about this on other threads and I agree that Logos sees its primary function as a "research library" and has been optimized for that purpose. I also fully support adding a "project" feature. I would use it all the time to differentiate between different lessons and other, well projects on which I am working.

I do not think all users see Logos as primarily a "research library" especially many new users based on years of questions on the forums about how to simply read a book. For those users, your projects/layouts proposal could be a remedy but I do not feel it would be intuitive up front. Others may look at my suggestion and say the same though. Just my 2 cents.

Chris Heil

https://community.logos.com/discussion/comment/1318519#Comment_1318519

There are already two functions that support this, one is the general sync and the other is the favourite tool. You can set a book mark inside a resource with the favourite tool.

Whereas the sync is hit and miss the favourite tool almost always works, for me at least. I am thinking it would be better if Logos made these functions more robust end to end rather than add a new function. You should not have to add the resource to a list or a project.

It is right that you mention it. This should just work.

I do agree that this feature needs attention, one way or the other.

Thanks for the input Antony.

When simply reading, I do not want to have to remember to add a book mark, set a favorite, or update a layout after each reading session and then load at the start of each new session. Frankly I get interrupted often especially if reading on my iPhone in line at the grocery store. Like you I would also prefer users not have to add a resource to any tool, whether favorite, Reading Queue, or project, but recognize JT's observation of Logos as a research library so there is differentiation between reading and reference look up that cannot be avoided. Maybe the Favorite you suggest could have a "reading setting" that would automatically update the favorite to the latest page read when set. Regardless just asking for improvement on a pretty basic function.

MJ. Smith

https://community.logos.com/discussion/comment/1318518#Comment_1318518

The second part of this is that "layouts" would be transformed to mean what it really should mean: Simply a pattern and/or collection of tiles. A "layout" could be populated with a "project."

No, no, no - a template is simply a pattern of tiles; layouts are instantiated. Speak the PNW dialect please.[;)] You had me confused for so long on what you wanted as a "project" because you didn't make the distinction between template and layout [:P]

Antony Brennan

https://community.logos.com/discussion/comment/1318524#Comment_1318524

Maybe the Favorite you suggest could have a "reading setting" that would automatically update the favorite to the latest page read when set.

I think that is a pretty good idea you've had, that way it serves both functions. Then you can set it manually or you can set it to 'read' mode and it follows your progress

Simon’s Brother

For the most part things already work for me and I'd rather see Logos improve what already exists and sure it works consistently across application rather than leave existing functionality where it is and introduce another thread of new functionality that will servce a purpose up to a point until in the future we say, hey Mr & Mrs Logos, this really isn't doing the job for me anymore, my needs and/or my expectations have changed again so can you add another new funtion to the software and don't worry about improving what you have already done even though it's what should be doing what I want / need it to do.

I am not convinced a project/template combined with a layout is the solution to this particular problem. It sounds like overkill to a simple problem and one in which if the ability to set up templates and layouts can not be equally and easily done in the Desktop App, Web App and Mobile app then is just introducing anthoer complicaitn of disjoint between apppication platform when what we want for a task of keeping track of where we are up to in a book to have continuity in how we go about it and how the software keeps track of it.

In other contexts a project/template and layout solution has merit so I'm not discarding it all together, just think it overcomplicates things. I get what a template is, what a layout is, but should I assume every person who is going to use Logos understands them and how to make them work to keep track of readng a book cover to cover? Should the have to learn this way of looking a things and how to implement it on mulitple platorms or know they have to set it up on one platform to use it on other platforms when all they want to do is open a book and read it from start to finish. There will be people coming to the software and using it primariy for ebooks - whether they be popular chrisitan living titles, amish romance titles, children's books or whatever else is offered on the e-book platform. They may only be using a faithlife ebook mobile app on their phone and not even know what Logos Bible Software Desktop app is and certainly won't want to download and install it simply so they can create a template and layout to read there latest mystery fiction purchase. We need to step outsid outside of where we are coming form and think about users wanting to achieve he same thing - keeping track of their reading progress - but these complicated solutions - for thats' what they would be to them are not going to cut it with them.

If syncing needs improving then let's see that improved, if users need to be better informed about how place location of books between platforms is synced and can be explained better how to use that to acheive there goals then let's see that better explained. But lets keep how we keep track of reading simple and in line with what people know from life experience of how to keep track of reading progress - Overcomplicate the back end as much as need be but the front end should be as simple as possible, as familiar as possible to what people already know and where it is smarter and offers finer control than a phycial bookmark - then demonstrate it well and explain it well and make it easy to find where to find that demonstration and explanation.

DMB

https://community.logos.com/discussion/comment/1318527#Comment_1318527

The second part of this is that "layouts" would be transformed to mean what it really should mean: Simply a pattern and/or collection of tiles. A "layout" could be populated with a "project."

No, no, no - a template is simply a pattern of tiles; layouts are instantiated. Speak the PNW dialect please. You had me confused for so long on what you wanted as a "project" because you didn't make the distinction between template and layout

Yes!

I felt JT was eternally angry with me, because I didn't understand.

Matt Hamrick

https://community.logos.com/discussion/comment/1318524#Comment_1318524

There are already two functions that support this, one is the general sync and the other is the favourite tool. You can set a book mark inside a resource with the favourite tool.

Whereas the sync is hit and miss the favourite tool almost always works, for me at least. I am thinking it would be better if Logos made these functions more robust end to end rather than add a new function. You should not have to add the resource to a list or a project.

It is right that you mention it. This should just work.

I do agree that this feature needs attention, one way or the other.

Thanks for the input Antony.

When simply reading, I do not want to have to remember to add a book mark, set a favorite, or update a layout after each reading session and then load at the start of each new session. Frankly I get interrupted often especially if reading on my iPhone in line at the grocery store. Like you I would also prefer users not have to add a resource to any tool, whether favorite, Reading Queue, or project, but recognize JT's observation of Logos as a research library so there is differentiation between reading and reference look up that cannot be avoided. Maybe the Favorite you suggest could have a "reading setting" that would automatically update the favorite to the latest page read when set. Regardless just asking for improvement on a pretty basic function.

So don't set a book mark or favorite. Simple you say? Open book and read then close book. Tomorrow open book to read again and where you closed the book is where it will open. This is easier than reading a print book.

scooter

https://community.logos.com/discussion/comment/1318536#Comment_1318536

Overcomplicate the back end as much as need be but the front end should be as simple as possible, as familiar as possible to what people already know and where it is smarter and offers finer control than a phycial bookmark - then demonstrate it well and explain it well and make it easy to find where to find that demonstration and explanation.

Yessir. 100%.

JT (alabama24)

https://community.logos.com/discussion/comment/1318547#Comment_1318547

Yes!

I felt JT was eternally angry with me, because I didn't understand.

How could I ever be angry at you? [:)]

JT (alabama24)

https://community.logos.com/discussion/comment/1318555#Comment_1318555

For those who think that “projects” would be too confusing, here is my argument:

Those users would simply have ONE project, turned on by default. Let’s even give it a name: “READING.” Everything would just sync, all the time, no matter the device or how the resource tiles were “LAID OUT” on any device.

Other users might want slightly more flexibility, so they could have a second project named “STUDY.”

More advanced users could have projects for each academic course they teach, each sermon they preach, or wedding they officiate.

If I were going to use the term “TEMPLATE,” it would be starting points for any given project type. For example: I am currently getting ready to take a couple through premarital counseling. I have created a “layout“ (using logos currently AWFUL nomenclature) that automatically opens up the books and bibles I use. I never update the “layout” unless I want to add something. When I do, I make sure to reopen the “layout” from scratch so that everything is back to default before adding anything. I WOULD NOT want any of those resources to sync… unless I created a “project.“ then I would!

Lew Worthington

https://community.logos.com/discussion/comment/1318559#Comment_1318559

I see some merit to that concept.

As it works now, the way I use Logos sort of forces me to study different topics when on my various devices. I might be a bit of an outlier, but I have about 50 books open on my phone broadly addressing about 6 different topics. I'm always reading parts of all those topics. When I go to my tablet, I would love to have those same things open without having to open them individually. But that's way too much trouble, so I just resign and read different things.

And that doesn't even touch the vast differences in the way the desktop app works for me. Functional parity is almost completely irrelevant if the visual universes these platforms foists upon us are so foreign to one another.

Hmm. I cannot imagine trying to look productively at maps or any graphic or any chart on the mobile app, so perhaps it's best just to keep them completely separate.

Simon’s Brother

https://community.logos.com/discussion/comment/1318559#Comment_1318559

For those who think that “projects” would be too confusing, here is my argument:

It's not that projects are too confusing. It's that they have no relevance to someone who may only use a mobile app. A project is useless to them. They want a robust easy to use bookmarking system. Or should these users needs be ingnored because they are different to ours ?

JT (alabama24)

https://community.logos.com/discussion/comment/1319520#Comment_1319520

A project is useless to them.

Or should these users needs be ingnored because they are different to ours ?

But it isn't useless to them. In your scenario, they would have the ONE default project and everything would always sync. All of the time. Logos would function very differently for them than it does now.

The issue is that Logos is designed to be a research library. These users want it to be more like a reader app. There are other users who want to have both (a research library and a reader app). My suggestion solves that problem for everyone.

Dave Hooton

https://community.logos.com/discussion/comment/1318536#Comment_1318536

If syncing needs improving then let's see that improved, if users need to be better informed about how place location of books between platforms is synced and can be explained better how to use that to acheive there goals then let's see that better explained. But lets keep how we keep track of reading simple and in line with what people know from life experience of how to keep track of reading progress

Desktop to mobile (Android) sync needs improving as I found it to be unpredictable. Mobile to Desktop (Windows) sync was predictable after it was opened on desktop (if already open and then read the mobile sync will be ignored). So it would be better to close the book when finished reading on a device. Then one has to remember to be online in the Mobile app.

Overcomplicate the back end as much as need be but the front end should be as simple as possible, as familiar as possible to what people already know

I thought I knew about sync to desktop (above), but that has failed!....

Hanson

https://community.logos.com/discussion/comment/1319601#Comment_1319601

I just want to be able to read a book on my iPad, bookmark it and be able to go to my computer or phone and pick up where I left off. Exactly same way I do on Kindle. Yes, Logos, is used for research. However: 1. a lot of the books Logos sells are books meant to be read from beginning to end, i.e., a normal books. 2. Research entails reading. In my research I've read numerous books starting at page one to the last page without jumping around. I still read the bible this way as part of my daily bible reading routine. It doesn't negate the research aspect it supplements it.

Also, for our mobile heavy users chech this out: Mobile Bookmarks