The Gamepad Reloaded
Revision of Gamepad API support in Samsung Internet Beta 5.4
A while ago Ada Rose Edwards and myself reported on the state of the Gamepad API in Samsung Internet 4.0, and given that time flies when you’re having fun, a prompt update is due. We have recently released an open beta for the next version of Samsung Internet (5.4) which, amongst other changes, enhanced our support for gamepads. We are going to retest all the controls from the original tests and add the joy of a special surprise!
We are testing in Samsung Internet version 5.4.00–15 BETA, running on a Galaxy S7 Edge with Android 7.0. In a similar manner to last time, we are using the HTML5 Gamepad Tester.
In order to use the controllers, first you need to pair them with your phone. In order to do so, turn on Bluetooth in your device and scan for nearby devices. Make sure your controller is turned on and discoverable.
Each controller has its own way of pairing. The 8Bitdo requires the “start” button to be pressed, while the Stratus and the Xbox controller have dedicated pairing buttons on the back/top respectively. Once the controller is paired, you should see it in your Bluetooth list of connected devices and listed as an input device.
Once the devices are connected, you will see icons that will represent them on the notifications bar. From here you can jump into their settings and disconnect them as well.
Here we give our thoughts on each controller. At the bottom of the article is a diagram for the complete mappings of these controllers in Samsung Internet Beta.
SteelSeries Stratus XL
Ada: The controller which was initially promoted with the Samsung Galaxy GearVR. Great to see it now has all major buttons mapped! I was impressed it could even handle pressure sensitivity on the triggers. A little big and heavy for my taste but a great feeling controller.
Diego: One of the better options when using a Bluetooth controller on your device, this gamepad now accurately maps buttons, triggers, analogs and bumpers. This is a great comeback since last review, where inconsistent mappings made it a good yet incomplete option. It now sits at the top alongside other controllers!
- Amazing button mapping.
- Feels comfortable
8Bitdo SFC30 — Ada’s Fave
Ada: My personal favourite. Light & small fits in a pocket or purse. Buttons feel great and I love the retro Famicon look. Has multiple modes so it works in a variety of apps and buttons are fully mapped. I like how the D-Pad matches to the Axis-0 and Axis-1 so it can be used for where other gamepads would use an Analogue stick.
Diego: Still attractive not only due to nostalgia and form factor, this portable controller can brag that it has all its buttons mapped. Nonetheless, with the excellent mappings now present in the SteelSeries and Xbox One Controller, I can’t seem to justify why the D-Pad is not being mapped accordingly and is instead being mapped to a ‘digital’ thumb stick. The way these buttons are mapped to an axis is inconsistent and behaves in a different manner than expected.
- Small form factor
- Can be recharged
Microsoft Xbox One Controller — Diego’s Fave
Diego: There’s something about this controller… maybe it’s the fact that many people consider it the best controller in existence, but being able to use it to play on your mobile device is cool. It is not something new though. We already saw that in our past review of the Gamepad API, but the fact that all of the issues with button mappings have been resolved is something to be excited about. Buttons, triggers, bumpers, analogs and d-pad are all accessible from the browser, with only the “View” button [B8] used to navigate back.
Ada: It’s a classic controller design. Like the Stratus XL it is too large for my tastes but a great high quality controller. Fantastic to see that the button mappings in Samsung Internet have improved significantly since our last reviews.
- All buttons mapped.
- Provides trigger and bumper control.
- Many users might already have one.
Nintendo Switch Joy-Con
Ada: A brand new controller, working in the web straight away! A few buttons don’t work and it is a little laggy but it is impressive none-the-less!!
The controllers are mapped so that when held with the joystick on the left, you have the analogue stick, 3 of the buttons, trigger and SL mapped the same. Home, screenshot, start and select are mapped to different buttons.
Diego: Enter Nintendo. Some days ago we saw the release of the Nintendo Switch, and when a few days later we read that the Joy-Cons were being connected to Windows and Macs it immediately brought up the question if they would be picked up by the Gamepad API. And *voila*, they are. This being said, the fact that it is one controller being broken to work as two makes for some inconsistencies while trying to use each separate controller as equals. Also, analog sticks mapped to buttons is not exactly what we would like, but hey, it’s a start! And a pretty good one for that matter!
- One Switch controller gives you two separate Joy-Con controllers. If coded specifically for these type of controllers we can take advantage of two inputs instead of one.
- Since it separates it can have innovative applications for an experience with controls in each hand.
- Few buttons mapped that match any other controller.
- More complex to use the pair as a single controller with two joysticks.
The following image summarizes all the available button mappings present in Samsung Internet version 5.4.00–15 BETA.
First of all it’s quite remarkable how much the gamepad situation has improved from our last revision! From different button mappings, supporting 21 mappings (up from 14 last time), to [B1] causing our apps to navigate away from the page, we’ve come a long way! ([B8] seems to be the default way now to navigate back).
It’s quite exciting to see great support for gamepads like the SteelSeries Stratus XL and the Xbox One Controller, which behave in a similar fashion. This is great news because we are getting consistent trigger, bumper and analog stick support to use in our web applications/games. It is also promising to see how very new devices like the Joy-Con controllers are being picked up by the browser through the Gamepad API, which albeit having a lacklustre mapping configuration, will improve surely for our next revision!
What does this mean for developers?
Gamepad support is good, use it. Mappings are getting more consistent but some controllers may have unexpected layouts. By default you can use an expected layout that will mostly work for most controllers but it is important to provide the ability to remap buttons and axes for the comfort of your users.
Feel free to send us any reports on how your gamepad of choice is behaving in the Samsung Internet browser or BETA.