Wanting contact management in your app is loser thinking actually (jk)
The speed at which Proton is vibe-coding their services means you should expect feature regressions on the regular. Shipping MVP is on the table so long as impossible roadmaps are met.
I don't know why they are doing this. I do know, that contact-management always worked fine — until for whatever reasons, they removed it. I usually assume a motive for such things. In this case, I can't come up with much, not seeing how they'd benefit from nudging users to use the web UI.
In my experience, feature regressions like these are due to some kind of service migration, data pipeline refactor, or etc, all in service of some future end-state that has more features but constrained by the MBA-brained roadmapping requirements that sees MVP releases with major regressions first.
Wanting contact management in your app is loser thinking actually (jk)
The speed at which Proton is vibe-coding their services means you should expect feature regressions on the regular. Shipping MVP is on the table so long as impossible roadmaps are met.
I don't know why they are doing this. I do know, that contact-management always worked fine — until for whatever reasons, they removed it. I usually assume a motive for such things. In this case, I can't come up with much, not seeing how they'd benefit from nudging users to use the web UI.
Apparently, if it works, break it.
Enshittification is Lord. Amen
In my experience, feature regressions like these are due to some kind of service migration, data pipeline refactor, or etc, all in service of some future end-state that has more features but constrained by the MBA-brained roadmapping requirements that sees MVP releases with major regressions first.