Digitransit-ui UX depends on browser JS engine performance. In here, we keep track of some devices that were tested with http://browserbench.org/JetStream/
| Device | Result |
|---|---|
| i7-4810MQ CPU @ 2.80GHz (Chrome) | 211 |
| E3-1505M v5 @ 2.80Ghz (Chromium) | 206 |
| i5-4440 CPU @ 3.10GHz (Edge) | 194 |
| MBP I7-4850HQ @ 2,3GHz i7 (Chrome) | 182 |
| i7-4700MQ @2,40GHz WIN10 (Edge) (Chrome) | 170 |
| iPhone 7 (Chrome) | 169 |
| i7-5500U CPU @ 2.40GHz (Chromium) | 159 |
| i5-4440 CPU @ 3.10GHz (Chrome) | 158 |
| i7-4700MQ @2,40GHz WIN10 (Edge) (Firefox) | 147 |
| i7-2620M CPU @ 2.70GHz (Chromium) | 135 |
| iPhone 6s (Chrome) | 119 |
| MBP i5 (Chrome) | 111 |
| iPhone 6 plus (Safari) | 69 |
| iPad Air 2 (Safari) | 60 |
| iPhone 6 64GB (iOS9, Safari) | 65 |
| Samsung Galaxy S7 (Chrome) | 58 |
| Samsung Galaxy S6 (Chrome) | 49 |
| Xperia Z5C (Chrome) | 47 |
| Xperia Z5P (Chrome) | 47 |
| LG GFlex2 (Chrome) | 35 |
| LG G2 (Chrome) | 31 |
| 1+1 "2014 Flagship killer" (Chrome) | 31 |
| Lumia 950 (Edge) | 31 |
| Nexus 6 (Chrome) | 31 |
| Honor 5 (Chrome) | 30 |
| Nexus 5 (Chrome) | 27 |
| LG G4 (Chrome) | 27 |
| Samsung J5 2016 (Chrome) | 18 |
| Lumia 650 (Edge) | 15 |
| Moto G 4G XT1039 (Cyanogen 12.1) | 12 |
| Lumia 635 (IE) | 11 |
| Jolla 1.1.9.28 (Sailfish Browser) | 11 |
It seems that JetStream benchmark 30 is the threshold where application becomes usable. Below 30, it feels laggy. Results 50 or above seem to give good UX.