The article explicitly called for native networked apps (Java-based, or activex based, e.g.) to bury the browser, because browsers can't be offline-first and can't be dynamic enough.
In the end, the opposite happened: After a brief profusion of native network UIs experimenting with new kinds of dynamism, browsers just absorbed their features until all other network UIs were dead.
In the end, the opposite happened: After a brief profusion of native network UIs experimenting with new kinds of dynamism, browsers just absorbed their features until all other network UIs were dead.