DRM being tied to the software is effectively still the same end result. Software maker for any number of reasons stops publishing new versions of the app and they become unlisted from appstores eventually for failing to use recent SDKs or patching security flaws and users still cannot read their books.
So you depend on a company paying someone to run a DRM server or you depend on them paying someone to maintain an app and a CI/CD system. Sooner or later when the DRM content supplier stops paying for the infrastructure, your book stops working one way or the other.
Microsoft is a noteworthy example of a major ebook seller shutting down ebook accs: https://www.vice.com/en/article/3k3wkk/microsoft-ebooks-will...
DRM being tied to the software is effectively still the same end result. Software maker for any number of reasons stops publishing new versions of the app and they become unlisted from appstores eventually for failing to use recent SDKs or patching security flaws and users still cannot read their books.
So you depend on a company paying someone to run a DRM server or you depend on them paying someone to maintain an app and a CI/CD system. Sooner or later when the DRM content supplier stops paying for the infrastructure, your book stops working one way or the other.