owen-chapman

I was asked to sit on a panel for discussion about industry topics and how to start up a successful games business.

I love talking about my job, I love talking about my company – in fact – I just like talking in general; but do remember that all of the things I’m writing about, I’m still learning too! Secondly, I’ve tried to make this presentation as generic to business as possible, but it is adapted from a talk I did about getting into games, merged with this previous blog post about starting up a games company, so forgive me if I drop the ball now and then and start waffling about games and techy stuff… I am in fact, deeply nerdy.

What we at Static Games failed to grasp when starting up was that running a business and a development team is not a small part time job for one of the developers. It’s a lot of work. Seriously. A lot. In fact, I’m now the managing director and that’s what I do full time. I have contributed to the coding and development on occasion, but developing games isn’t actually a part of my regular day job and probably isn’t ever going to be.

Games and religion are rarely seen as compatible sections of society. On the surface, there seems to be very little overlap between the two, and often when we hear about religion and games in the same article, it is because the two are in conflict. Whether it is the use of Manchester Cathedral in a shooter or the use of a Hindu god in a fighting game, the general opinion is that religion in games simply causes offence and outcry. But perhaps this doesn’t have to be the case.

Games and religion are rarely seen as compatible sections of society. On the surface, there seems to be very little overlap between the two, and often when we hear about religion and games in the same article, it is because the two are in conflict. Whether it is the use of Manchester Cathedral in a shooter or the use of a Hindu god in a fighting game, the general opinion is that religion in games simply causes offence and outcry. But perhaps this doesn’t have to be the case.

We’ll explore how the WebComponent specification describes a new way for browsers to implement this architecture without needing framework support, and then ways in which existing frameworks can leverage this support to provide an enhanced experience for developers. Along the way we’ll take a detailed look at the actual specification as well as current support by some actual frameworks.