Yesterday I caught my PC trying to upgrade to Windows 10, and I quickly put a stop to it. Windows has been threatening this for a while, and I saw Helen’s laptop take several hours to upgrade, on a day she needed to do work.
Many people at the time of writing seem obsessed with the AR game Pokémon Go – where you have to walk around the real world to find monsters to catch.
My facebook and Twitter feed this week has been full of people telling me what creatures they’d caught, and I thought it’d be fun to invent my own silly Pokémon names, and post responses saying things like “Oh but have you caught a Spruedongle yet? I have!” and see if people wonder where I’m finding these super rare Pokemon that don’t exist in any guide.
Then I thought of creating a game using Textadventures.co.uk, which I’ve dabbled with before, to make something resembling the actual game – where the player ambles about and collects creatures. I know it’s pointless, but if you think about it, so is the real thing.
So Fakémon was born! Gotta collect them all, for no reason.
My game BotSumo that I made for Android has been on the Android Play store since January, and has been downloaded now over 12,000 times. Most of those people downloading were from the US, which was to be expected, but weirdly it found secondary audiences in Russia and Brazil, despite not being translated into their native languages.
I use Browserstack a lot for testing website in devices, and It’s especially useful as I don’t have a lot of popular devices that I need to test on. iPhone 5, iPhone 6, iPad, iPad air etc.
I noticed a problem a few times now, and it’s mostly the way these iOS devices handle vendor prefixes – or more specifically that they *require* vendor prefixes for things like transform: rotate();
Sometimes, a page might look totally different on Browserstack (which shows the design messing up disastrously) to on iPhones and iPads that I’ve tested on.
It seemed a bit odd to me that the most favoured devices in the world still required vendor prefixes, when Chrome mostly doesn’t need them. I assumed they must have been updated recently surely, and that Browserstack is only showing me the devices at their factory settings. So I asked them to find out.
So there’s proof. Devices on Browserstack are at their factory settings, which means any updates to the browser (and there might have been loads by now, surely?) won’t show.
This is good and bad, I can see why you’d want to see what your website looks like on a brand new out-of-the-box iPhone, but also, with the amount of browser updates there’s been, that might display totally different to the majority of iPhones.
But, just something to bear in mind.
Update – Browserstack got back to me saying they do provide the latest version of Safari on iPhone 6S and 6S Plus, which is what I’d expect.
Although still it looks like you can’t test on an older phone that’s upgraded to Safari 9 (assuming that does happen of course?!).