Skip to content

Commit

Permalink
add server info
Browse files Browse the repository at this point in the history
  • Loading branch information
friadev authored Nov 21, 2024
1 parent f34a71c commit 33953d6
Showing 1 changed file with 3 additions and 1 deletion.
4 changes: 3 additions & 1 deletion blog/posts/pwa-vs-iwa.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,4 +14,6 @@ license: BY-SA

The concept of a Progressive Web App is enticing: an app using web technologies that’s inherently cross platform (since it runs in a browser) and acts like a native app, even working offline. Support in traditionally locked-down platforms like iOS means that PWAs can give users the freedom to install apps without having to go through Apple’s App Store.

Attempts at similar things have been made before, notably the infamous Electron allows developers to easily create cross-platform apps by essentially bundling the browser in with the app. This has its drawbacks, though. Browsers have huge attack surface so it's important to keep them updated, but many Electron apps ship outdated versions, leaving those apps vulnerable.
Attempts at similar things have been made before, notably the infamous Electron allows developers to easily create cross-platform apps by essentially bundling the browser in with the app. This has its drawbacks, though. Browsers have huge attack surface so it's important to keep them updated, but many Electron apps ship outdated versions, leaving those apps vulnerable.

So why isn't every app shipping as a PWA? The answer is an old problem with web content: the fact that you have to trust the server every time you use it.

0 comments on commit 33953d6

Please sign in to comment.