![]() I have a few Airtables that I basically always have open. However, I don't want to be forced to have each individual Google Document in a separate window like it's Mac OS 9 just because it's a "Web App". I would very much like to have Google Docs as a separate item in my Dock though. I for example often need a couple Google Docs open at once. It seems weird to have to point this out, but there are many apps that have tabs that are not web browsers.Īny sort of document-based app benefits tremendously from tabs, and thus it would be unfortunate to have to lose that feature when making it a Web App. (And for that part, I'll take the further development of alternative browser engines as a net gain tbh. I agree that I'd rather just have a system WebView for things like this, but putting aside that the landscape for those is effectively just Blink/V8 or WebKit/JavaScriptCore at this point, it's still perfectly valid to just want a single engine that behaves consistently across environments - particularly given Safari's history of being slow to adopt Web standards even when they don't fall into the whole argument of capability.Įven Tauri, which currently relies on system WebViews, has started collaborating with the Servo team, at which point you're cycling right back to shipping a browser stack for writing desktop apps in JavaScript. Shipping Node underneath seems to skew more toward the latter, even if it's going to vary by team whether it's a philosophical choice or just a pragmatic one. use Chrome itself without also running server-side JS underneath it? Arguably this is the opposite - Google goes in hard on the idea of expanding the Web's capabilities, after all, where a lot of the Apple camp has historically preferred keeping certain system-level stuff like hardware access away from browsers. I mean, wouldn't the ChromeOS way be to just. If we had those features, we could get back to storing and editing files on disk, using web apps, which would be a huge improvement for local-first apps. Nor is drag-and-drop or LaunchHandler (open a specific file type with the web app). You can open a Web app without opening Safari, you can close Safari without all web apps closing.īuuutt. Separating Safari and Web App allows both to run independently. > Web apps run in the context of a separate process called `Web App.app`. A notable exception are OAuth flow links, which are handled in-app based on a heuristic. > Same-origin (or in-scope if a manifest exists) links are handled in-app, cross-origin (or out-of-scope if a manifest exists) links open in the default browser. No other storage means apart from cookies are copied. > Different from iOS/iPadOS, credentials in cookies are copied over, so if you were logged in when running in the tab, you're logged in when you launch the app. Some of my favorite details from the article: I am unreasonably excited about Safari PWAs on macOS. (It's exactly like the Smart App Banner for native apps, but, for web apps, it only works with the "Open" button, not with the "Install" button.) Note that "Add to Dock" installable web apps already do have a Smart App Banner on the new macOS 14 Sonoma, but only when you already have the web app installed. When the user returns to the webpage, the banner doesn’t reappear. And with a large and prominent Close button, a banner is easy to dismiss. They appreciate unobtrusive banners at the top of a webpage, instead of a full screen that interrupts their experience with the web content. They trust that tapping the banner will take them to the App Store and not a third-party advertisement. In iOS, Smart App Banners provide a consistent look and feel that users come to recognize. > Smart App Banners vastly improve users’ browsing experience compared to other promotional methods. A Smart App Banner for installable web apps would be no worse than what Apple currently offers, a Smart App Banner exclusively for native apps, and I think those banners are just fine. It wouldn't be a "new" way to badger users, because developers can currently badger users to install a native app.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |