Just adopt the new services, and if they disappear, use something else.
What do we exist to persist these days and how long for?
Google have broken that trust on countless occasions, and as a consequence for half a decade they have been deprived of the opportunity to waste any more of my time. You should consider doing the same
If only I could easily use something like notmuch/isync on my phone...
Gmail doesn't have the automated bundling features that Inbox does, and like you, losing Inbox will be a pretty significant blow to my ability to manage email.
I've been slowly migrating away from Google's services for a long time now because they keep pulling stunts like this - it's like they're completely unable to keep their engineers focused on maintaining any kind of product consistency or long-term support.
Android Pie's awful UI/UX changes and discontinuing Inbox are very nearly the last straw for me. I can't avoid Gmail entirely as I'm too attached to the address, but worst case I can always just forward to a new one.
I don't think it's intentional, but it's a side-effect of Google's bonus structure[1]. There's more money to be made (by employees) if their team successfully launches a new product. Maintaining existing products isn't as profitable, in fact, launching and deprecating popular products as frequently as possible is the optimal scenario for maximizing bonuses.
1. From the information I've encountered. I'm not a Googler.
Google is an R&D company really, not a consumer one.
Off the top of my head, I've observed:
- Resume Driven Development: wherein enterprise contractors and developers inject as many fad frameworks, architectures, and uncalled for features unnecessarily.
- Vendor Driven Development: wherein the application architecture is tie to a cloud solutions billing model as much as possible.
- Search Engine Driven Development: wherein the code is just a bunch of copy/pasted code that isn't really understood, and doesn't really work together coherently.
- Ignorance Driven Development: wherein a perfectly serviceable solution which is better in every way was not used, simply because the developer saw a problem and immediately went to code, without looking at how everyone else in the world solves the problem.
- Delusion Driven Development: wherein a completely useless application is beautifully crafted based on the obvious delusions of a manager or founder, which have successfully spread to the development team without any critical push-back or data to back the deluded assertions of the authority that has deemed the software necessary.