Blazing Chrome Android

[Saran Bascas]

MilitantAI-fueled computers rule the Earth while humans are expendable, lacking power, prestige or status among their machine overlords. Choose to play as Mavra, a super badass human resistance soldier, or Doyle, the equally groovy and deadly insurgent robot.

When a small group of rebels decides to overthrow their oppressors, it results in heavy casualties and a ton of lock-and-load fast-paced action where scrapping robots and blazing chrome with your powerful weapons is the only thing standing between you and your freedom.

Blazing Chrome is currently under development. If you just want to check our updates, Danilo and JoyMasher twitter are the most frequently updated channels. Our Youtube and Facebook cary more curated posts, mostly once every a couple of weeks. If you are press and want to receive early builds, please request access on our Do.Distribute.

In Blazing Chrome, militant AI-fueled computers rule the Earth while humans are expendable, lacking power, prestige or status among their machine overlords. Choose to play as Mavra, a super badass human resistance soldier, or Doyle, the equally groovy and deadly insurgent robot. When a small group of rebels decide to overthrow their oppressors, it results in heavy casualties and a ton of lock-and-load fast-paced action where scrapping robots and blazing chrome with your powerful weapons is the only thing standing between you and your freedom.

This page contains co-op info for Blazing Chrome on the PlayStation 4. All information about Blazing Chrome was correct at the time of posting. Information is subject to change. If you see any errors please email us.

LinkedIn and 3rd parties use essential and non-essential cookies to provide, secure, analyze and improve our Services, and to show you relevant ads (including professional and job ads) on and off LinkedIn. Learn more in our Cookie Policy.

The traditional argument for web apps goes something like this: since a web-app runs in a browser, and all phones have browsers, and the browser on your phone is largely independent of the operating system, a web-app can run on all platforms with broader backwards compatibility. That translates into fewer developers, fewer designs, with less cost and in less time. A web app can be deployed to all users simultaneously without any input from them, so nearly all your users are using the latest version of your app nearly all the time. And when your users try to view your web site from a mobile device for the first time, they aren't confronted with that annoying pane that asks them to go download the app from a store.

Using a web app as your mobile app can be a really attractive option, especially from a cost/benefit standpoint. It used to be that the case against web apps on mobile was the conclusion Facebook came to in 2012: A web-app just couldn't compete with a native app when it comes to performance and user experience. But with processors in phones starting to approach -- and exceed -- processors in laptops, that argument starts to take on water. With that kind of power, it becomes more difficult to argue that web apps can't compete when it comes to snappy scrolling and image loading. And for a lots of apps, that's really the core of what they need to do. The back and forth of user interaction and network operations is, for a lot of apps, the whole enchilada. And with web apps starting to get support for gestures and complex touch interactions, they can do a lot more than they used to. Web apps on your mobile device can even do things like access your files and camera. With that kind of functionality, there isn't much left to set a native app apart from a web app, right?

First, let's start with the mobile processor issue. Yes, it's true that mobile processors are evolving, and that, one day, we'll all bask in the glory of omnipotent smart devices that can plunge through content at blazing speeds. But, sadly, that day is not today. Even though your brand new iPhone might churn through a webpage as fast as a native app, that's not the case for lots and lots (the vast majority) of devices out there. So, before you go all in on web, you should probably do an expansive feasibility test.

Next, let's talk about user experience. Specifically, the idea that you can approximate the UX of a native app in a web app. While that may be true in certain specific circumstances, overall, I'm just not buying it. While you do have access to things like device notifications from a web app, they don't entirely emulate the native app experience. Notably, on Android, a website's notifications from chrome are clearly identifiable, and are missing some of the more advanced features of native notifications. While they might become more attractive and functional someday, that day is not today. In addition, those notifications are supported specifically by Chrome, not the Android system itself. So if your users prefer Firefox, you might be out of luck. Furthermore, when you click on a notification sent by a web app (or that convincing home screen icon) that click is going to send you into a browser. Whenever you view that web app, you're going to see the browser bar at the top of the screen with the web address visible. When you compare that to the seamless splash of a native app's startup, it's hard to defend.

I don't think anyone can really have a purely objective take on this issue, and mine is biased by my occupation. Objectively, it seems like a mobile web-app is certainly a more viable solution now that it was in the past, and certain apps could definitely be more-or-less approximated by a web app, and there are potential cost and time savings to be had. But when you look at the breadth of options for what a native app can do versus a web app given the hardware landscape of the mobile industry right now, the reign of web apps still seems a ways off.

3a8082e126