PWA vs Native Android

Hardware access includes

Native PWA

Geolocation Y Y

Camera and microphone Y Y

Device vibration Y Y

Screen orientation Y Y

Battery status Y Y
 Features

Native PWA

Push notifications Y Y

Working offline Y Y

Adding an icon to the home screen Y Y

Being installed into Android (i.e. in the

Y Y
apps drawer and in Settings)
 Features

Native PWA

Receiving intents Y Y

Launching in full screen Y Y

Clipboard access Y Y

Persistent auto-login using the

Y Y
Credential Manager API
 Features

Native PWA

Hardware-accelerated 2D/3D graphics

Y Y
using CSS3, HTML5 Canvas or WebGL

Accessing the filesystem (Chrome and

Opera) and reading user-selected files Y Y
in any browser

Really slick, smooth UIs with 60fps

Y Y
animations
Upcoming Hardware Access

Bluetooth via Web Bluetooth API Magnetometer

NFC Gyroscope sensor access

Ambient light sensor (works in Firefox 48+) Hardware powered shape detected API

Proximity sensor (works in Firefox 48+)

Accelerometer
If you target the Next Billion Users, PWAs are the way to go. Android users are
the majority, and data is expensive.
If you have desktop users, build a PWA.