There are three certainties in life:

Death, taxes and that every hard drive ever created will fail one day.

The cloud is more trustworthy than your hard drives.

That being said I am keeping a running list of the things I wish it had, with some important mitigants:

– Virtual copies (or preferably Versions) in the Local tab. I know the local tab is new but this feature would be great. I guess it really depends on whether Adobe can embed multiple versions in an XMP or DNG file – I certainly hope so.

– Larger previews in the grid view – it would be nice if I could get the previews much larger in the grid view.

– WAV files – I’m sure I am in the minority here but it would be great if Lr could associate a WAV file with a pic and allow us to listen to the WAV file directly from Lr. I know this is a niche interest, but its important to me and on my list.

– Convert to DNG – I convert everything to DNG (I have had the debates many times with people – I remain all in on DNG). It would be nice if you can do that from within Lr. Right now I use the Adobe DNG Converter to import my pics from the card, which is actually fine, but it would be better within Lr.

– Export presets – I haven’t figured out a way to save customized export presets – this would be very nice and something I used in LrC every day.

– Export to PS in PSD format – this probably doesn’t matter that much because after exporting as a TIF to PS I just save the file as a PSD in the same folder and Lr immediately see it, so this is probably low on my list of priorities and is more about muscle memory from LrC.

– More metadata – and specifically more ways to filter by metadata. The mitigant here, somewhat surprisingly, has been me going back to using Bridge which allows for some very powerful metadata filtering. But it would be better to have this in Lr.

I am comfortable with it; however, I’d change the default order of the Development panels to the order that they are applied by the program. There is an order that adjustments are applied in the program’s code and a rationale supporting that order developed by the programming team. This will help the user understand that previous adjustments are not affected by, successive adjustments. The most recent example of this is DeNoise in the Detail panel. Adobe’s guidance is to apply DeNoise early in the workflow while the Detail panel is positioned in the middle of the default panel stack. Therefore, the Detail panel should be positioned high in the default panel stack to suggest to the user to consider DeNoise and sharpening early in the workflow.

Checking Adobe’s helpx file tells me that neither smart collections nor folder hierarchy will be retained.

Also, I have plenty of disk space and two different online backups.

2. The “Classic” version should be called ‘Lightroom’, and the Cloud version should be called: “Lightroom Cloud”. That’s the only naming that makes any sense.

3. If I would change anything about Lightroom Classic it would be the Book module, I would add direct access to print with Shutterfly, and the Web Module to work together with Adobe Portfolio or other websites.

So to answer your question as to “what Adobe could do to make you you LR Cloud” is: Absolutely nothing. There is nothing they can do to make me want to use / switch to that version.