P: Ability to sync Lightroom Classic keywords with the Lightroom Ecosystem

@Karl, I'm not trying to divert the attention... I'm trying to find a rational explanation for the many issues LR is suffering from, starting from this one. This topic has been created 11 months ago, is maybe one with the most "me toos" or at least the most dabated one, and is parked as "answered".

I'd love you to prove me wrong, really... but except trying to understand WHY Adobe behaves like this, I have no other idea for being helpfull as reporting bugs and stating my -personal- observations of the evolutions (or lack of, in certain cases).

Maybe other poeple will read this and think the same, mabe not. Maybe Adobe will read this and react, mabe not. At least I do my part: report the bugs and try to give the devs the tools the LR we are -in the end- paying for. Just saying...

@ Karl, 
Ok it is your point of view. 
We (or I) just need keyword. Actually not possible with CC.

Image edition or development is really easy and strong. That what make me stay in the adobe ecosystem. 

The real fact Gilles is
1) we have understand
2)it is not because we understand we are not allowed to complain.

It is unbelievable everything is synching perfectly, I have to admit this is a real performance and can understand how difficult it is to do, really.

It just seems the last step was not achieve for political reasons. By design as previously mentionned.

We too understand hierarchy in keyword add complexity to the complexity. I personally do not use this. My keywords are very specific (technical/legal. I'm not able to sync a full 2 way.
But keyword is just the tip of the iceberg.

It is ok,  Classic and CC are 2 different offer for different users an so on,

The real fact is :

Classic becomes unusable because too fat, too big, too laggy, too slow

CC is just a pre-alpha software with too much limitation to enter in a real production environnement.

Maybe we are not supposed to use both software BUT I've never see on there advert.

And if we use both it is not by nostalgia but because the switch is just not feasible because once again CC weakness.

We can share so much about those points... but let focus about the keyword sync.

In a strict technical terms, I can't understand why it is so complex to sync a keyword which can simply be embedded in the photo??? Everything is embedded and/or sync but the keyword.

What's the point? Adobe is kidding us. That's the real fact.

Adobe have to listen to our customer.

If customer want a real keyword management it is because users need it in CC.
If customer asks a real sync it is because Adobe is not able to provide an real keyword management in CC and we need to use Classic.
If customer ask a non case sensitive or a list of already keyword it is because it is far more efficient and logic.
You can't deny or forget you and adobe earn money thanks to your valued customers.

@9970247 It's funy because the thing that would lock me in more than anything into the Adobe toolchain would be a seamless keyword facility between the cloud and desktop version of their DAM...

The thing is they are so nearly there, they are snatching defeat from the jaws of victory.

The real fact is that Lr Classic and Lr CC are two different work environments, for different users, and you should understand it, as Adobe has always been totally clear with that. You are simply not supposed to use both programs.
Syncing complex keywords hierarchy is difficult, and Lr Classic is not up to that task. Just to understand, look at the many problems when you simply sync collections to the cloud : slow sync, stuck files, etc. I believe that Adobe tried to balance the user needs (and requests) and the technical risks, and this balance was not achievable.

You are totally right.
So strange every time we are asking something we think is legit, somebody comes and tries to explain the inexplicable 

@Antonine, I think it's not helpful if you start diverting the attention away from the issue at hand and instead go to the LR is shit argument... A software never is finished - it only is ever finished when it's development is stopped and it's discontinued!

I don't think it is on purpose, but what's obvious is that cloud/sync integreation on the working LR (aka classic) is still in beta stage and won't evolve anymore. Just the bare minimum to show "no, classic is not discontinued". Even though it seems to be... Buisiness decision. And it is understandable that the integration of new technologies (AI, sync, cloud, ...) in a dynosaure (LR classic...) is quite difficult without rewriting everything...

--> So why not rewrite everything and ensure the users are more trapped whitin the system in order secure recurrent revenues? This all makes sense and is understandable!

However, the new LR is also still in beta, does not respond the photographer's need (it's designed as a mobile app) and is obviously designed to secure the recurrent revenue, BEFORE delivering a decent software.
If the new LR were a great software, integrating all the working concepts of classic, whit additional features of sync, AI, web integration and all this... why not ? But it's not! It has too many flaws and omissions.

Now LR is divided in two, unfinished softwares:
1) Classic, which I belive a lot of people will still be using because it corresponds best to the photographer's need, which is SLOW and on which the sync integration is POOR (/bad/horrible).

2) The newly written LR which is not finished yet, which does not respond to the photographer's need and which first goal seems to be to 'trap' the user's in the 'cloud' ecosystem in order to make it as difficult as possible to switch to another software.

It certainly does feel like Adobe are going out of their way to make the experience of using CC Classic and CC together as bad as possible.