Note - Web App Notes and Highlighting Don't Sync

In what appears to be a reactionary move to recent criticism of the lack of progress on the web app in a recent forum thread and highlighting'code out the door but they are not what they seem.

We have added the ability to take, edit, and remove notes and highlights in the web app. These are entirely new and separate from your desktop notes/highlights.

and

They are different from desktop notes in several key ways:

First and foremost, they are not broken into different "documents".

We have not added support for specific highlight styles and indicators.

Contents of notes are plain text (do not support formatting, links, etc.).

These differences are subject to change as we continue fleshing out the web app but we wanted to provide this basic level of functionality as early as possible.

In simple terms what that first difference means was only clarified after a couple of users questioned what this was really about:

Just so I understand correctly; when you say "new and separate from your desktop notes/highlights" you mean that notes/highlights done in the web app do not sync to desktop/mobile and vise versa?

That is correct. The notes and highlights in the web app are stored in the same system as the rest of them, but we made a deliberate decision to keep them separated so that we could get something out the door without having to implement full rich text support.

At some point in the future (no schedule guarantees!) we intend to make notes that you take in the web app available on your other devices.

So right now if you take notes / make highlights in the web app they will not sync to your desktop or to mobile apps. Hence you will not be able to work seamlessly across platforms / devices with notes / highlights created in the web app as it stands.

If you do decide to use notes / highlights in the web app please ensure you understand this difference. The web app is in beta this feature has clearly underdeveloped and will change - when a developer says "so that we could get something out the door" that always rings alarm bells for me. And ensure you do read the web app forums to be fully informed of the lastest status of this feature and what impact changes to it might have to any notes / highlights you have created in the web app - personally I would say if its critical work stick to creating the notes / highlights or any other user created content for that matter in the desktop or mobile app.

Find more posts tagged with

Comments

JT (alabama24)

when a developer says "so that we could get something out the door" that always rings alarm bells for me.

I agree. This decision is perplexing to me. It seems quite short sighted and potentially a huge headache for some users. It is better not to ship than to ship the wrong thing.

Out of curiosity, where was the original post?

Graham Criddle

https://community.logos.com/discussion/comment/891631#Comment_891631

Out of curiosity, where was the original post?

https://community.logos.com/forums/t/139394.aspx

JT (alabama24)

https://community.logos.com/discussion/comment/891633#Comment_891633

Thanks Graham!

Mark Barnes

https://community.logos.com/discussion/comment/891631#Comment_891631

when a developer says "so that we could get something out the door" that always rings alarm bells for me.

I agree. This decision is perplexing to me. It seems quite short sighted and potentially a huge headache for some users. It is better not to ship than to ship the wrong thing.

This is a very sensible decision from the developers point of view, and perfectly acceptable for a product in beta (which the web app is).

Adding notes/highlighting will no doubt be very complex. Any coder will want to split that task up into various sub-tasks. As an example:

Displaying simple highlights
Adding/removing highlights
Displaying more complex highlights (e.g. inductive study)
Handling custom highlighting schemes
Syncing highlights

During a beta phase, it's perfectly sensible to break that process down into discrete milestones, and release and debug each milestone separately. It's called incremental development, and it's increasingly common.

The alternative to this is to not release until all the steps have been developed. Then people complain that nothing's happening. You can't please all the people all the time.

JT (alabama24)

https://community.logos.com/discussion/comment/891658#Comment_891658

During a beta phase, it's perfectly sensible to break that process down into discrete milestones, and release and debug each milestone separately. It's called incremental development, and it's increasingly common.

I agree in principle, but not in this case. When the developers add a feature which can cause harm to the end user, that is inexcusable!

Mark Barnes

https://community.logos.com/discussion/comment/891660#Comment_891660

I agree in principle, but not in this case. When the developers add a feature which can cause harm to the end user, that is inexcusable!

You're overstating it.

If they released a version which messed up your existing highlighting, then that would cause harm. Releasing a version which doesn't (yet) sync back to the desktop hardly causes harm. They may even add functionality later to convert these basic notes to full notes that sync. But either way, no-one is harmed.

PetahChristian

https://community.logos.com/discussion/comment/891658#Comment_891658

The alternative to this is to not release until all the steps have been developed. Then people complain that nothing's happening.

So true.

The fact that the product is a beta should be all the warning anyone needs. We're getting early access to a work in progress.

Please feel free to test it and report bugs, but let's please not be unreasonable about expecting x.0 features in an 0.x beta. It's not finished yet.

JT (alabama24)

https://community.logos.com/discussion/comment/891662#Comment_891662

You're overstating it.

I have misunderstood. I was under the impression that this system was not a part of the current system, nor would it be. Alan wrote:

These are entirely new and separate from your desktop notes/highlights.

These differences are subject to change as we continue fleshing out the web app but we wanted to provide this basic level of functionality as early as possible.

This made it sound like they hobbled something together which they had no intentions of supporting in the future, just so that beta** users could have some "functionality" now. David clarified a bit:

The notes and highlights in the web app are stored in the same system as the rest of them, but we made a deliberate decision to keep them separated so that we could get something out the door without having to implement full rich text support.

At some point in the future (no schedule guarantees!) we intend to make notes that you take in the web app available on your other devices.

As long as this means that the notes & highlights WILL (eventually) be integrated into the rest of the system, I fully agree with you. If this is not what is intended, but rather they mean "the note system now WILL NOT be plugged in, but eventually we will create a system WHICH WILL," then you are wrong and harm indeed will be done to users.

I <think> Phil clarified this just now, but I am not sure:

I hope you take advantage of this opportunity to "migrate" the desktop notes to a more flexible and powerful "centralized" note repository, where things like "note documents" become just one more type of tagging that the note has, with the added benefits to speed, searching, flexibility, etc. that a system like this could bring.

That's exactly where we plan to go.

Lastly, re:beta testing... There are two different kinds of beta testing. Any number of times I have made posts about beta testing, reminding users that it is designed to help work out bugs and should not be used on "production" machines, etc. Things can and do go wrong.

There is another kind of beta testing, and this clearly falls in that category. Faithlife is MARKETING this as a selling point feature of Logos Now. The word "beta" here should NOT mean "helping the developers work out the bugs" but rather "this feature is in development and not quite ready for prime time." If FL doesn't intend to support these notes for these users, it is shameful. Hopefully I have misunderstood (as it seems I might have done).

Alan Palmer (Logos)

https://community.logos.com/discussion/comment/891694#Comment_891694

I'm sorry that my announcement wasn't more clear. It sounds like there are a lot of assumptions being discussed in this thread. I'm always happy to address any specific questions and concerns people have in this thread.

... was not a part of the current system, nor would it be.

"They are new and separate from the desktop notes". By this I was referring to the fact that they don't sync. I wasn't trying to imply anything about the future. Our current plan to eventually merge these web notes with existing notes into a new system (I think Fr Devin Roza must have a bug planted in our conference rooms) [;)]. This is likely still a ways out though, and I always hesitate to promise things too early. I have a fear that even as I say this, different people will make varied assumptions and it might even spawn more speculation. [:S]

Again, I want to add clarity (and, hopefully, not more confusion) so please let me know if there are questions I missed.

[8-|]

JT (alabama24)

https://community.logos.com/discussion/comment/891714#Comment_891714

please let me know if there are questions I missed.

My concern isn't that the notes don't sync now, but only that you won't abandon support for the notes that the users create now. It sounds like that is your intent. [Y]

David Mitchell

https://community.logos.com/discussion/comment/891694#Comment_891694

As long as this means that the notes & highlights WILL (eventually) be integrated into the rest of the system, I fully agree with you. If this is not what is intended, but rather they mean "the note system now WILL NOT be plugged in, but eventually we will create a system WHICH WILL," then you are wrong and harm indeed will be done to users.

I <think> Phil clarified this just now, but I am not sure:

I hope you take advantage of this opportunity to "migrate" the desktop notes to a more flexible and powerful "centralized" note repository, where things like "note documents" become just one more type of tagging that the note has, with the added benefits to speed, searching, flexibility, etc. that a system like this could bring.

That's exactly where we plan to go.

In terms of implementation details, we've hedged our bets. Our intention is (eventually) to migrate all apps to a new, more powerful model for Notes. However, the initial implementation of Web App Notes is built on top of the old system, so that we can (basically) flip a switch and make Web App Notes appear in Desktop/Mobile notes if we have to abandon the current strategy for any reason. (customers hate the new UI, unforeseen technical challenges, whatever)

If FL doesn't intend to support these notes for these users, it is shameful.

Prior to leading the team working on the web app, I led the "Documents Team" for about two years, whose sole concern was safely preserving our customers' Notes/Highlights/Visual Filters/Reading Plans/Prayer Lists/etc. while scaling those web services up. I know how important your data is to your livelihoods, and I would not release a feature in Logos Bible Software that allows the creation of new data without a firm commitment to preserve and support it.

JT (alabama24)

https://community.logos.com/discussion/comment/891719#Comment_891719

Thanks David. [:)]

David Mitchell

https://community.logos.com/discussion/comment/891719#Comment_891719

However, the initial implementation of Web App Notes is built on top of the old system, so that we can (basically) flip a switch and make Web App Notes appear in Desktop/Mobile notes if we have to abandon the current strategy for any reason. (customers hate the new UI, unforeseen technical challenges, whatever)

I feel that I should add that I see no reason to expect that we'll have to abandon this strategy—I included this note to highlight the extent to which we have "backup plans for backup plans" when it comes to preserving the data that you entrust us with.

Simon’s Brother

https://community.logos.com/discussion/comment/891723#Comment_891723

Thanks for adding some further clarity David but I still stand by my initial concerns that you are breaking user workflows surrounding user created content and you need to be very clear about this to anyone using the web app. The web app is promoted heavily as a part of Logos Now - I have seen FL employees stating the web app is close to the desktop experience, which it is not, it is a beta app. FL is sending conflicting and mixed messages about this web app and what it is and is not capable of doing - if I log into web app now there is no way I can telling the notes and highlights I create there will not be part of my desktop or mobile workflow.

FL has caused users problems in the past with user created content being put in jeopardy and if you understand the history of this software notes and highlighting have been a contentious issue on many ocassions. I believe FL had a responsibility to communicate clearly the full implications of when you make fundamental changes to the way the software works / behaves, particularly when that affects user created content. The Web App is promoted as a major benefit of signing up to Logos Now so saying the web app is in beta is not an excuse for communicating this change in the wishy washy way it was communicated.

Mark Barnes

https://community.logos.com/discussion/comment/891751#Comment_891751

I have seen FL employees stating the web app is close to the desktop experience,

He actually said that in comparison with biblia.com, "it's as close to getting the full desktop experience in your browser as possible" (emphasis added). Obviously, app.logos.com is significantly closer to the desktop experience than biblia.com, and as a comparative statement, it's not inaccurate (though it would have been better to say "as currently possible"). Anyway, my point is that he didn't say that it's close to the desktop experience, but the closest you can get it a web app.

if I log into web app now there is no way I can telling the notes and highlights I create there will not be part of my desktop or mobile workflow.

I agree that there should be a 'warning' when first using this feature.

The Web App is promoted as a major benefit of signing up to Logos Now so saying the web app is in beta is not an excuse for communicating this change in the wishy washy way it was communicated.

As far as I can see, the only promotional description of the web app is this:

These doesn't seem to oversell the current functionality — if anything, it undersells it.

Preston Davis

OK, so I just subscribed to Logos Now for the express purpose of using app.logos.com more effectively. ...only to discover that my notes dont sync. With notes sync, app.logos.com is truly a "Killer App" without notes sync, it's extremely frustrating & negative experience (for me)! ...so I just got my refund. ...to bad. I really wanted/needed that functionality as I now work primarily on Linux.

...please get this added. Surely, you hear the cries of your people!

Preston

JT (alabama24)

https://community.logos.com/discussion/comment/954019#Comment_954019

OK, so I just subscribed to Logos Now for the express purpose of using app.logos.com more effectively. ...only to discover that my notes dont sync. With notes sync, app.logos.com is truly a "Killer App" without notes sync, it's extremely frustrating & negative experience (for me)! ...so I just got my refund. ...to bad. I really wanted/needed that functionality as I now work primarily on Linux.

...please get this added. Surely, you hear the cries of your people!

Preston

For clarification: FL is in the process of upgrading the notes engine. Currently the web app uses it, but the desktop and mobile will convert at a later date. I have no idea when that might be. In all likelihood, Now subscribers will have early access.

Adam Borries (Logos)

https://community.logos.com/discussion/comment/954024#Comment_954024

OK, so I just subscribed to Logos Now for the express purpose of using app.logos.com more effectively. ...only to discover that my notes dont sync. With notes sync, app.logos.com is truly a "Killer App" without notes sync, it's extremely frustrating & negative experience (for me)! ...so I just got my refund. ...to bad. I really wanted/needed that functionality as I now work primarily on Linux.

...please get this added. Surely, you hear the cries of your people!

Preston

For clarification: FL is in the process of upgrading the notes engine. Currently the web app uses it, but the desktop and mobile will convert at a later date. I have no idea when that might be. In all likelihood, Now subscribers will have early access.

Early-access announcement: New: Beta test the new Notes tool on desktop

Please note:

Now membership is no longer a requirement for the web app. It is open to anyone with a Logos 7 package, including the free Logos Basic.
This early-access for the Notes tool on desktop does not sync your previously-existing notes documents from Logos desktop and mobile applications. Note documents and notes in the new tool are two separate systems at this time. It will be possible to import your existing notes to the new system "soon"*.

*Rev 22:20

Preston Davis

https://community.logos.com/discussion/comment/954024#Comment_954024

That's great news! I will "occupy" till then [O]

Preston Davis

https://community.logos.com/discussion/comment/954096#Comment_954096

Early-access announcement: New: Beta test the new Notes tool on desktop

Yay! [Y]

Now membership is no longer a requirement for the web app. It is open to anyone with a Logos 7 package, including the free Logos Basic.

Do tell! My budget thanks you for this timely info! So "7" users get full access to all features (currently available)?

This early-access for the Notes tool on desktop does not sync your previously-existing notes documents from Logos desktop and mobile applications. Note documents and notes in the new tool are two separate systems at this time. It will be possible to import your existing notes to the new system "soon"*.

*Rev 22:20

...understood. and amen, Brother!

JT (alabama24)

https://community.logos.com/discussion/comment/954112#Comment_954112

Do tell! My budget thanks you for this timely info! So "7" users get full access to all features (currently available)?

You must have a base package... but that includes "Logos Basic" (which is "free"). https://www.logos.com/product/136022/basic

Kevin A. Purcell

https://community.logos.com/discussion/comment/954115#Comment_954115

The problem with the current system is not Logos' fault. The term "beta" has changed in tech over the last 20 years. It used to mean in development and likely to not work so only the very brave should use it. But when Google got very popular and kept Gmail in "beta" forever and average people used it, other companies began to start using the term beta the way Google did with Gmail.

"This is a beta, but don't expect any help because we just don't do that. However, it's the only product we've got and the only one you'll get and it's free so shut up and just use it."

I"m not saying Logos is doing this. I'm saying they're using it int he more traditional term stated at the outset. However, a lot of users saw the announcement for something they've been wanting FOREVER and couldn't resist signing up for it not understanding what Logos meant by beta assuming they meant the same thing Google did with Gmail et. al.

Don't use this unless you're willing to use something that's not yet production quality. It's frustrating that the web app is still in this state this long after it first came out. Seem to be taking forever to develop in this give me instant satisfaction society we live in.

Rant over.

Preston Davis

https://community.logos.com/discussion/comment/954945#Comment_954945

Well,

Thank you for that completely unnecessary "rant". No one said anything about having an expectation of a completed app. What was said was that when I found this feature was NOT available, that it did not work FOR MY PURPOSES. Others may be fine with the current implementation, but as I stated ...for me... with Notes Sync it would be a "killer app" without ...for me... it's a frustrating experience. For others? Maybe not so much. Also, I know what Beta means as I am software developer with more than 20 years programming experience in multiple languages. ...so yes, I know what beta means. Don't assume! Because "assuming" makes an ...well ...you know. I will not be responding to your possible response as I have found your "rant" to be a needless waste of kilobytes.

Peace Be Unto You.

Yiteng

https://community.logos.com/discussion/comment/954111#Comment_954111

It's been a year, and the problem still hasn't been resolved.[:$]

Andrew Batishko

https://community.logos.com/discussion/comment/955159#Comment_955159

It's been a year, and the problem still hasn't been resolved.

It's in progress, and currently in beta:

https://community.logos.com/forums/t/159247.aspx

Kevin A. Purcell

https://community.logos.com/discussion/comment/954961#Comment_954961

Well,

Thank you for that completely unnecessary "rant". No one said anything about having an expectation of a completed app. What was said was that when I found this feature was NOT available, that it did not work FOR MY PURPOSES. Others may be fine with the current implementation, but as I stated ...for me... with Notes Sync it would be a "killer app" without ...for me... it's a frustrating experience. For others? Maybe not so much. Also, I know what Beta means as I am software developer with more than 20 years programming experience in multiple languages. ...so yes, I know what beta means. Don't assume! Because "assuming" makes an ...well ...you know. I will not be responding to your possible response as I have found your "rant" to be a needless waste of kilobytes.

Peace Be Unto You.

Wow you have totally misinterpreted my tone. I'm equally frustrated with the state of the web app and want it to improve much faster than it is. Sorry for making you so angry. Never intended that. Never intended to say anyone thought it would be completed. I'm not sure why my words caused you such frustrated that you feel the need to respond as you did, but if it caused this kind of response, then I am VERY sorry.

Shikai Ronnie Poon

https://community.logos.com/discussion/comment/955169#Comment_955169

It's been another 6 months. Any news?

MJ. Smith

https://community.logos.com/discussion/comment/993647#Comment_993647

It is in beta - still with features missing. I suspect the needing to import notes from BibleWorks may have caused a slight delay but it is generally progressing at a reasonable rate. https://community.logos.com/forums/t/171239.aspx

Thomas W Haynes

https://community.logos.com/discussion/comment/891631#Comment_891631

Disciple of Christ (doc):

when a developer says "so that we could get something out the door" that always rings alarm bells for me.

Having been a developer for 25 years, That phrase ring bells for me too. It usually means a kludge (look it up lol). It usually means some arbitrary timeline cannot be met if the "planned" functionality is included. So just cut something out to make a schedule.

Unfortunately, this happens and for sure Faithlife is not the first one to do it.

Best regards