How can I see Reading Plan on my iOS device?
In January, I created a reading plan using the “Generate a Reading Plan” on the desktop version of Logos. I was then able to do something within my iOS app to see that reading plan on my iOS devices. I have just created another reading plan on my desktop, but I can't find the steps to add it to my iOS devices. (My app version is 6.2.4.0099 and the reading plan is for the ESV.) Any suggestions? Thanks.
Comments
-
I have just created another reading plan on my desktop, but I can't find the steps to add it to my iOS devices.
Any suggestions?
I believe that it is supposed to automatically appear, but I could be wrong. I agree that you should have a means to turn it on & off on a particular device... and maybe you can. Some questions:
- When is the "start date" for the reading plan?
- Does the reading plan document appear on the mobile device (under documents)?
- If so, is the reading plan turned on within the resource (ESV) itself?
0 -
I believe Faithlife expects that the normal way of following a reading plan in its mobile apps is via the "home" screen in those apps.
In previous versions of the mobile apps (before the tabbed interface enhancement), I never worked my reading plan from the home screen. I'd have the reading plan document open, and it would stay with my most recently-read date. I'd tap on the reference for the date, and it would navigate to the correct location.
In the new, tabbed interface version of the mobile apps, that approach is very unwieldy. So I don't use it any longer. I go to the home screen and allow it to take me to the correct location. It works 80% of the time, but there are times when it loses its place and isn't correct with where I've read. Since I only ever read from one device, I'm not sure why that's the case. But it's a pain when that does happen.
Donnie
0 -
-
now it can be open but out of sight
How do you make it "out of sight"? I'm in the "select tab" view all the time, and I'd always have to see it as I scroll right/left to the resource I want to get to.
I think the more general point is that for the majority of scenarios, the new UI is far preferable. I really like it. However, in the scenario of opening any kind of "document" (e.g. a note or a reading plan), it's worse. If they had a "Send all documents here" tab feature, then I'd be more inclined to open documents in the new version. If I'm in an open document, I can't even open a new document in the same tab. I don't want to manage a proliferation of tabs whose content is documents. So at present I pretty much never open any document in the new version, including reading plans.
Donnie
0 -
Hi JT,
The "start date" was May 2 and it is a four month plan.
I can see the reading plan document under the mobile device's document menu for Reading Plans.
I can see the reading plan prompts within the ESV.
I just can't figure out how I successfully got a reading plan to the home page in January.
Thanks for getting back to me.
David
0 -
How do you make it "out of sight"? I'm in the "select tab" view all the time, and I'd always have to see it as I scroll right/left to the resource I want to get to.
It is "out of sight" because it IS in the "select tab" view. In the old system, you would have to have a split screen, right?
0 -
The "start date" was May 2 and it is a four month plan.
I can see the reading plan document under the mobile device's document menu for Reading Plans.
I can see the reading plan prompts within the ESV.
If the "start date" is in the past (and yours is), and if the document is showing on the device (it is), and if you can see the reading plan prompts (meaning that it is "turned on"... and it is), then I am perplexed. FL will have to chime in.
0 -
It is "out of sight" because it IS in the "select tab" view. In the old system, you would have to have a split screen, right?
No. It took no time to open the reading plan document (no more than going to the home screen), and when I touched the link for the day's reading, it opened the resource in the document's place.
Donnie
0 -
I reached out to FL. The problem was solved by reinstalling the app.
0
