Modern Jago recently welcomed some of the UK’s greatest indie game developers for beer, pizza and a healthy amount of geekery. Let’s take a look at some of the awesome new games that were previewed.

Icycle: On Thin Ice

Reece Millidge, developer of Icycle and the upcoming sequel Icycle: On Thin Ice, talked us through how he developed the games using Action Script 2 (not 3). Interestingly, neither uses a physics engine – not that you’d be able to tell.

Originally inspired by BBC Micro classic Dare Devil Dennis, the Icycle series sees the last human on earth running for his life through a post-apocalyptic city . As you do. With the backing of publisher Chillingo, it’s due out by August this year and looks set to be a hit.

Lumino City

This game is a beautiful work of art – literally. Every backdrop was built from wood, cardboard and metal, and then filmed to create a gorgeous game setting.

Lumino City creator Luke Whittaker described how the game began as a series of sketches many years ago. When he saw a piece of art that looked startlingly similar to his prototype sketches (by freakish coincidence only) he got in touch with the artist and collaborated with her to design the set.

Lumino City is a stunning game, as you can see in the video above. Luke assures us it will be out ‘soon’. We can’t wait.

Imp Paired

Imp Paired, developer Nicholas Lister’s fun, addictive offering  challenges the user to match shapes and patterns.

Nicholas’ story is incredibly interesting and inspiring to anyone who aspires to become a game developer but is stuck in another career path. Nicholas was in the sixth year of his architecture studies when he decided to follow his dream of creating a game.

The development of the game, he explained, also helped him develop as a person and discover what he truly wanted to do in life.

Letter to ourselves

And now for something completely different…

Our letter to a young us, featuring sound advice from @nicollhunt, @nicholaslister, @gurumatt, @runefrog & @boidster utopianworldofsandwiches.com/a-letter-to-a-…

— UtopianSandwich (@UtopianSandwich) May 21, 2013

Utopian World of Sandwich, aka Sarah and Woody, took to the stage to share a letter they had written to themselves while at college.

The letter included advice on their dreams and wishes they used to have and encouraged their younger selves to just do it – create the game they had dreamed of and not be embarrassed by their designs.

It was an inspiring talk and got everyone thinking about what advice they would give their younger selves.

Fist of Awesome

Nicoll Hunt, developer of the hit game Hard Lines, talked us through his new game – an Ouya exclusive – Fist of Awesome, which started off as a way to impress his girlfriend on Valentine’s Day, before he realised it had even greater potential.

In the game a lumberjack wanders through a forest and city taking on wild beasts that seem to be controlled by some sort of evil… Of course, our protagonist has fists of awesome that can punch the little critter’s lights out.

Funded through a Kickstarter campaign, the game is a brilliant example of how new technologies and funding platforms can support indie game developers.

Do you have an idea for your own game? Why not share it on Twitter!

Originally posted on ModernJago.co.uk

If you spend any time amongst people in the London tech startup scene, it won’t be long before you pick up on the influence that Eric Reis’ 2008 book The Lean Startup has had on many people in fledgling businesses.

The book describes a methodology for running a new (tech) venture that draws on both the lean manufacturing movement pioneered by the Japanese car industry in the 1980s, but also from agile software development methodologies.

Overall, Lean Startup argues that if you want to build a business you need to change your product or service to reflect what your customers need, rather than building the “perfect product” and releasing it to market.

There are a few core concepts at the heart of Lean Startup:

Minimum Viable Product (MVP) encourages releasing a new product or service as early as possible, rather than waiting for the whole to be developed. This feels quite similar to time boxing and working releases in agile methods.

Continuous deployment encourages all software written to be released into production immediately.

Split testing (also know as A/B testing) is an experimental method of testing multiple versions of an application to see which is most preferred by users. It’s been a very common technique in commercial web development for many years.

Actionable metrics are measures that allow for meaningful business decisions to be made, as opposed to vanity metricswhich tend to just paint a rosy picture of a business’s position.

Pivot, which is when a business changes it’s fundamental business proposition on realising that it’s original hypothesis isn’t necessarily a great idea. Nokia, for example, started as a rubber products business, moved into producing cables as part of that product set, then into electronic components and from there into mobile phones and networking equipment.

Lean Startup came about in the world of the Web, and there are (it seems to me) a few challenges that need to be thought about when it comes to building a business that is focused on apps rather than a browser:

You need to think a bit harder about what you want to measure
The world of Web applications, and Web analytics is such that there is a lot of data about people’s use of your application generated at the server side which can be analysed using off-the-shelf tools (Google Analytics, for example). Those analytical tools provide so much information that you will probably have data that can provide actionable metrics.

If you are delivering an App, that changes: you can find out information automatically about the demographics of people downloading your app, and maybe some very limited usage data (time of use, for example), but that will be about it. Help is at hand though from services like Flurry.comwhich enable you to build flags to report on specific sorts of activity within your app.

A/B testing becomes more challenging
Within a browser environment you can deliver different versions of the same service to different people at the same time – having two entirely different versions of your site being tested concurrently is perfectly possible without the end user being much aware of their experimental subject status. Building that kind of testing model into an app becomes more challenging unless you have a level of complexity built into your app (or potentially can find a way to deliver two different versions of basically the same thing to your customer base).

Alternatives might include testing versions in a lab, but that can be costly or runs the risk of strange results from using small samples of experimental users and the impact of lab testing in the first place (this, in fact, is kind of what led to the New Coke debacle in the 1980s).

Continuous deployment versus app store submission processes
The idea of releasing multiple versions of code in quick succession works well in the Web world – code is released to a server, and can be rolled back quickly as well. In an app environment where there are submission processes and quality control on behalf of the app store owners, it’s slightly more challenging: if it takes a day (or a week, or whatever) to deliver an update to an app, then releasing every hour into the live environment is just impractical. Larger releases on a weekly or longer basis potentially bridge the divide (a week or even a month is a short time in comparison to application release schedules of old…)

There’s a lot of sensible advice in Ries’ book, but some of the concepts might need a bit of flex in a world where Apps become an increasingly important facet of a tech startup’s business.

jQuery UK was one of my favourite conferences of 2012. It had a great line up of speakers, talks about things I was interested in and was in an awesome venue. This year the venue had changed (to a bigger one) and the line up looked great.

After collecting my badge I made my way through the foyer with the other conference goers, collected my obligatory conference T-Shirt and made my way around the room. Some would have noticed the sweet retro game set up in one corner, others probably headed for coffee and pastries, me? Giant Red Bull can-shaped-fridges holding the various new flavours was my breakfast of choice, although by 11am it was obvious that 4 cans of varying flavours of ‘Awesome Juice’ might have been on a bit on the extreme side.

The morning was going to be kicked off by Brendan Eich – you might have heard of him – and as I filled through to the nice large auditorium, I went to find my seat…well, a seat not necessarily my seat. I’m a front a center kind of dude usually, just because I like to really absorb the speakers and not be put of by the glow of a screen in front of me, but as usual at these things, the front and center row is reserved for speakers, so i was front and to the right. Not a problem though, the set up was excellent with two large screen either side of the stage for the presenters slides.

Brendan Eich

As a developer who spends most of their time in JavaScript world, getting the chance to see Eich speak is certainly a tick on the old bucket list. Talking about the upcoming ES6 and ongoing to ES7 features, Eichs talk was certainly in a league of its own, but a great talk to start the day. Finishing up with a demo of Unreal Game Engine running in the browser to just blow minds, it certainly looks like JavaScript isn’t going to fade away any time soon and is only going to be even more important.

Richard D Worth

Speaking about jQuery 1.9, 2.0 and the future, Richard D Worth came onstage to address what had only really happened the night before – the release of jQuery 2.0. A massive milestone in the libraries journey which has been met with some hostility due to dropping support for legacy browser. He clears up a lot of messiness in the understanding of how well the legacy version of jQuery will be supported though and gives a rundown of the current state of the project.

Remy Sharp

I learnt jQuery because of Remy and here he was talking about not using it. Of course, I had come to this same conclusion a while back and started using un-jqueried JavaScript where I can, not to be some sort of Front End hipster who likes his code vanilla flavoured, but because it helps you both be a better developer in other libraries you might like to use and also gives you a better understanding of what jQuery actually does under the hood.

Remy’s slides, humour and excellent explanations make him one of the best speakers at almost any conference. Sure, he’s at a jQuery conf talking about not using jQuery, but it’s informative and a well-argued position. He admits that he won’t re-invent the wheel if he doesn’t have to and use jQuery where it make sense, but using it by default is not his preferred option.

Adam Sontag

Kudos goes to the organisers planning for lining up Adam’s talk right after Remy’s, it’s the same thing we saw at last years Full Frontal with two talks delivering two sides of an argument. Adam was talking about why it’s OK to use jQuery. A fantastic talk delivered with expertise and a great sense of humour, Adam owns the stage and no doubt drew the audience in, one of the highlights of the day.

Doug Neiner

Talking about state machines, Neiner’s talk might have seemed intimidating on paper, but due to his nature and natural ability to explain complex things, he manages to make the idea of Finite State Machines understandable even for the newest of developers.

Garann Means

Garann wrote the first Node book I actually read and understood, and here she talks about the full stack and how it works together. Maybe a little too much for some of the attendee’s, but I certainly got something from it.

Iiya Grigorik

I’ve seen this talk before, but the great thing was that some of the tips changed and it’s still a great talk to watch – actually, if you spend any amount of time developing in a browser, do yourself a favour and watch this talk. You need to know the dev tools and what they are really capable of and there is no place better to start.

John Bender

Every conference has one – the mind melter. John talked about Category Theory, a way of formalising mathematics and it’s concepts as a series of morphisms (objects and arrows). He used Category Theory as a way of seperating concerns within jQuery which allowed for faster DOM interactions. It was a good talk, a lot of it in the beginning went over my head way too fast, but in the end I caught up and managed to get on-page with some of the things he was talking about. From his experience of applying category theory to his work with jQuery, he built Wield, an object wrapper for abstracting away the DOM interaction with jQuery.

Joe Pettersson

Joe’s talk was great. Funny, witty and full to the brim of helpful hints. The pains, trials and tests that he and his team had to go through in setting up testing grounds for their web apps all boiled down in a 30 minute talk. He spoke about so many things that I want to use and now have somewhere to start. A great story teller too.

Jason Scott

Probably my least favourite talk of the day. I can’t tell if it was the content or the delivery though. Everyone I spoke to at the after party seemed to agree that it was hard to understand WHY that talk was in there. It started out being about building an experience and not a framework and sort of drifted into how to make a jQuery mobile theme for Blackberry.

The day ended with Food Trucks and Locally brewed beers. I’m not a drinker but was told that it was good. I hung around for a bit, speaking to a few of the speakers and attendees about the day, and then made my way back to Oxford station. All-in-all it was a good day, one of the better UK developer conferences, and no doubt I shall return next year.

I caught up with Lorraine Starr from Yippee! Entertainment, creators of the hugely popular Windows 8, Windows Phone and iOS game Chimpact, and got her to share some secrets on how they marketed the app.

“We didn’t get support initially from Apple when we launched Chimpact (although they have since featured us), so like most other app developers we had to do our own PR and Marketing. Most apps don’t get picked up by the app platforms and have to do what they can to get their apps in front of customers. There are three key key elements to marketing that we’ve found really successful.

1. Social Media

The key thing we did was build links into the app itself encouraging users to like our Facebook page and follow us on Twitter.

We brought the main character in the game, Chuck the Chimp to life by giving him his own Facebook page and Twitter account.

The key thing is not to bore your audience with endless posts, people will drop out if what you’re saying just fills up their news feed. Only post interesting/news worthy content that resonates with users of your app. We ran a competition to design a Chimp that was promoted on Facebook, offering one person in the UK and one in the US a chance to design a member of Chuck’s Chimpact family and have their design turned into a character in the Windows 8 & Windows Phone 8 versions of the game. The UK winner got the chance to go to our studio in Manchester and see their creation turned into a video game character.

You can also connect your Windows Store app to an online identity provider that uses internet authentication and authorization protocols like OpenID or OAuth– so you can get access to Facebook’s open graph API in Windows 8, allowing users to sign into your app using their Facebook credentials.

Social media also gives people a way of asking you for help if they get stuck or give you feedback. We get fantastic comments and feedback just because we’re approachable and users can come and talk to the team.

The best way to manage social media is to track the conversations around your app constantly, I do a daily search for ‘Chimpact’ and hijack people’s conversations to engage them and join in the conversation. It’s hard work but necessary.

2. PR

PR has been the most valuable thing but not easy to do, usually its about who you know and the connections you can make. For example, we serendipitously got some great publicity from the Celtic supporters who happened to mention Chimpact. I jumped on the conversation as Chuck and Chuck ended up engaging the Celtric team mascot, “Hoopy The Hound Dug” and had a picture tweeted round of the two “furry friends”. We even put a Celtic scarf on Chuck which really resonated with the supporters.

We also saw a direct boost from links we had already with a premiership footballer who tweeted about Chimpact for us just from the fact we had a personal link with him. Whoever you know, make sure you let them know about the app you’ve created and pull in some favours! The value of celebrity involvement or endorsement is amazing. The effects are short-lived, they only last for a day or so – as long as the Tweet is in their stream – but they’re very impactful. If you can afford to hire a PR agency then do it, it’s so important to target the wider market. We were lucky enough to get support from Microsoft and saw excellent results from an article in The Sun and publicity from Jonathan Ross, but usually you have to invest in that PR coverage unless you’re well connected!

In the early days I managed to get us a mention in The Times – the journalist Stuart Dredge used to run an iOS news magazine so I knew him from there. He picked up on Chimpact and he put a piece in The Times. It’s important to get your app some coverage in the general mainstream press as well as your local newspaper/s, both online and offline.

3. Partnerships

Look at who you know and what networks they have that you can hook into. For example, we have the advantage of being based in Media City so they’ve supported us by promoting Chimpact via their social media and The Brand Detective also gave us a feature through links we had with them. It’s important to look at cross partnerships – who do you work near or is in your extended community that might be interested in your app?

People are much more willing to collaborate and help each other than they used to be. If you’re not cash rich then hook up with other devs to do some joint marketing and PR to cut costs. Tell everyone you know – friends, colleagues, family and people you know who work at the platforms you’re working with. Before we started working with Microsoft we saw them as a big, faceless corporation. We’ve been bowled over by everyone at Microsoft we’ve dealt with, they’re very down to earth and willing to help which was a huge revelation. No-one else does that. It’s really important for the developer community.

‘Take advantage of the screen real estate’. That’s a common saying that was bandied around when working on the web in the early days. As screen resolutions increased we (collective we – designers, developers – the makers of the internet) chose not to celebrate that space and allow the content to breathe, instead we looked to see what we could add that would give us extra ‘stuff’ and more buttons and separator lines and tiled backgrounds even animated GIFs and information and screens became busier, busier, busier. “Look, we have a 100×100 pixel space. Add a button to do something, drop a weather widget in. Fill the space!”. It was a cacophony of visual noise and at the time, we thought it was great. I was there.

That mentality of filling space with confusion I partly blame on science fiction. I’ve often said in public that technologists look to science fiction for inspiration. Who wouldn’t want to have all the buttons and flashing lights that Uhura had in the original Star Trek? Those sets were designed to look complicated – after all, this being the future would surely mean that we would have invented many new technologies and devices and each of those would require at least one button, one light and an accompanying beep. That’s what made those visions of the future so exciting – the level of complexity and the thought that we’d need to be super clever and aware in order to operate these gigantic space engines. Did anyone think that we might also make sweeping advances in UI design so that it could all actually be controlled by a joystick with one button? Maybe, but I doubt that version of Star Trek would have been given the funding from the TV studios, this looks much more exciting:

When I look at games like World of Warcraft, the menus and the stats that you see are bonkers. The first time I played that game it was confusing, more then confusing, it was incomprehensible. Check this:

When I started playing, I wondered how I could ever be able to understand what any of that meant. But after a short amount of time, with a little investment, it became second nature and although there are options to turn parts of that UI off, I didn’t. It would have meant that my game play would be slower and I wouldn’t be as quick to respond. Part of being a player, a good player, was being able to read that interface. If this WoW talk is all gobbledygook to you then at least take a moment to enjoy Leroy Jenkins, one of my favourite examples of video that justifies the whole of the internet (WARNING: colourful language alert):

We have complicated UI on desktop programs – but they need to be complicated because they’re doing complicated things. For instance, Visual Studio – there’s even more detail required there than in WoW and complicated applications like that are not going to go away, here’s my current Visual Studio screen:

With Windows 8 we now have a new style of application – Windows Store applications. These applications seek to remove as much of the UI from the screen as possible – the concept behind this being that if there’s no UI on the screen then the user’s focus is on the content. Here’s a screenshot of a photo of mine in the Photo application:

There’s no UI on the screen – there doesn’t need to be and it means that the content gets my full visual focus. The content then becomes the UI, the inherent nature of that particular piece of content within the context of that application means I know if I touch and swipe I can then cycle through the other photos on my machine. We don’t need a button to indicate that that is the method of interaction, we’ve removed the chrome. However, if wanted to do something more than swipe through my photos, our approach is to employ on-demand UI.

On-demand UI

With Windows 8, if the content on the screen isn’t, or can’t be the interaction then we look to the edge. To the right for the Charms Bar for searching, sharing and settings, and if I want to find commands to interact with the screen, I swipe from the top or the bottom to pull up a control that we refer to as the Application Bar. Here’s the same photo after I’ve swiped in from the top:

You can see that I now have a back button on the top right (which takes me to a folder view of my images) or on the bottom application bar I can now perform some editing functions but I call on those functions only when I need them.

With the Modern UI, I celebrate the content and embrace the space available in the application. In the photo example above, that application is all about me enjoying my photos and not having to be distracted by buttons around the photos that could distract me from the task at hand. The Photos app is a very visual example, but how about an audible example, with Xbox Music. When I have that open, I’m enjoying the music that I’m listening to, I can glance at the screen and see exactly what track is playing without figuring out the UI first.

I can see what song is playing, where abouts in that track I am and if i’m not interacting with the app then I enjoy the additional imagery that’s pulled in from the cloud and that augments the experience. It’s like when the radio in my car would not just say ‘Radio 2′ but would say Radio 2, Chris Evans, and even tell me the name of the track. A small bit of information that doesn’t distract from the experience, but adds to the experience.

The same is true of Windows Store apps. That’s the beauty of the Modern UI. It’s all about the content. I don’t need to know the biography of the artist, I don’t need to know who the bass player is but at the time when I do, then by using the edges of the screen I can use the on-demand ui get to that information. That’s the key. 95% of the time it’s just visual noise, but if I need it I can get it.

Reduce distractions

If I’m reading a book, all I want to see is the words that the writer has written. I like the Kindle for this, there’s not even a clock on it – I’m sure there was a conscious decision made by the designers at Amazon at some point when it would have been so easy to incorporate a clock into the top corner of the screen. Maybe that’s their homage to the authenticity of a book. Maybe, they recognised that when you’re reading it’s about the story. It’s a feature that I find both annoying but also amazingly satisfying about reading on my Kindle. Any additional info that’s placed on the screen is only a distraction. ‘How long have I been reading?’ ‘How long do I have before I should go to bed?’ That’s why I love my Kindle, because it makes me just read and read and not care about the time and I’ll read till the early hours of the morning because the story is brilliant and there’s not a clock to remind me that it’s only 5 hours till daybreak. I don’t care. I want to know how Ender will finish his game.

Ho Designers

The same is true of Windows Store applications. When you decide what it is that your app is meant to be doing, don’t worry about the extra space that is available that you could fill with info, let the the user enjoy the content of the app, let the user revel in the content that you’ve worked so hard on and when they need to interact with your content, they know to look to the edge to find that interaction. Celebrate space.

This can be a difficult concept to grasp, especially when you’re coming from a different platform, be that a traditional Windows desktop applications or an application on another platform. But once you get it, you realise that it allows your user to enjoy and immerse themselves in the product they’re investigating, the article they’re reading, the image they’re viewing.

I spent some time with a chap at one of our workshops who had the most incredibly complicated desktop application. He had been tasked by his boss to turn it into a touch screen app. After reviewing the functionality, it was clear that this was never going to happen, however, when we talked through how his desktop app was used, it became clear that 10% of the time it required the complicated desktop application experience, 90% of the time it could be a touch screen app. So his desktop app did not and never will disappear, but it became apparent that there could be a touch app used 90% of the time to keep the day to day running of the app in place. That made me really happy. For 2 reasons.

1. Desktop apps will never disappear – some apps will always have a level of complexity that cannot be translated to a touch screen be that because of the complexity of the app itself or maybe the requirement for precise input of a lot of data (our fingers are not very precise when matched aginst a mouse) eg, Visual Studio, Visio or Photoshop
2. There are aspects of these programs that can become touch enabled and separated out to this new style of application, and as such become more accessible to a wider audience on a number of different devices

The lesson we learn there is – user context – recognise when your app is going to be used and customise for those user scenarios. Don’t try and convert an app to a tablet because that’s what you carry around in your pocket. Customise for touch, where touch is appropriate.

Celebrate the content

Allow the user to immerse themselves and only when they need to interact should they have to bring up the commands that allow them to do so. The application bar is your friend. For Windows 8 users it quickly becomes second nature. You digest the content on the screen and at the point where you need to change it, share it, move it, interact with it, you look to that first pixel and the on-demand UI gracefully glides in.

We are creatures of habit and we don’t like change. However, we are also brilliant at recognising and adapting to more efficient and beautiful ways of working.

Find out more: http://design.windows.com/.

It’s time for the most important post we’ll publish around this year’s Critters. The awards? A mere sideshow. The incredible entertainment? An afterthought. Now we know (and based on Twitter we really do know) that you’ve all been most perplexed by what to wear. Well, help is at hand, we’ve put together a guide to ‘what to wear for The Critters’  which means you’ll avoid any fashion faux pas on the night.

Dress Code – Black Tie

For those of you who are committing 100% to the theme, we applaud you. All of the Ubelly team will be rocking the full on Black Tie look and we’ve been drawing inspiration from this handy guide. That means dress shirt, tuxedo, bow tie and (polished) black shoes. A handkerchief tucked into your jacket pocket is optional, but highly recommended.

Also acceptable: Hollywood Black Tie or to 99.9% of the population – a suit and black tie.

The playing it cool alternative to full on black-tie, just pair your favourite shirt with a black tie and a matching jacket and trousers and you’ll be flying.

And if you need any more persuading as to why you should suit up:

We know for some of you suiting up is a deal breaker, so we’re willing to compromise. Penguins look an awful lot like they’re wearing a suit already, so if you come wearing a Penguin Onesie and some form of bow tie we’ll accept that as embracing the spirit of the dress code.

And for the ladies – We’re confident you don’t need our help to look amazing, but if you need  a starting point, we’d recommend your favourite cocktail dress and your best dancing shoes.

Of course if you want to don Onesies as well, we won’t hold it against you.

As for what not to wear. Well, if you could make sure your clothes are clean and you’re not wearing Pyjamas that would be a start. Basically if you’d wear it while lounging around your bedroom hungover on a weekend, it’s probably not going to be suitable for wearing to The Critters (Penguin Onesies excepted)

Still not got your ticket? Don’t miss out, grab one today!

A few weeks ago we headed north for Gavin Elliot‘s inaugural Industry Conference. Gavin was one of the forces behind Newcastle’s other web conference DIBI, which we’ve been to the last few years and loved, and Industry Conf is the product of his time after Codeworks. Taking place in the rather astonishing Turbine Hall, where Newcastle’s tram system used to be run from, Industry Conf saw 8 speakers from the UK and abroad share their views on the web design and development industry, via product design, cross cultural UX, education and, probably the strangest, insurance. The entire day was a great mix of speakers, and we’ve highlighted a few of our favourites from the day. I also managed to sketchnote a couple of the talks, which you can find at the bottom of the post.

Rachel Andrew and Perch

To begin the day, Rachel Andrew, co-founder of the tiny CMS Perch, took a non-design and non-development route to her talk by focussing on customer support. However, what came out of her talk was a great insight into how to build a successful product, how to use customer feedback and a few lessons and tips for anyone thinking of going into the realm of product. One aspect that Rachel talked a lot about was how much customer feedback affects Perch’s features and roadmap. She made the comment that “In business, you get what you want by giving people what you want.” However, she also went on to talk about how even though the more you talk to your customers, the clearer your roadmap gets, that you always need to protect the core use case of your product. If you only build in features that benefit the vocal minority, you’ll usually end up alienating and losing your majority.

There were two really interesting insights into how Drew and Rachel are trying to design support out of Perch. First, building in useful user feedback and writing solid documentation is one of the key ways of designing support out of your product. However, there will always be support requests. One of the ways that they’re looking at effective ways to scale is via their Registered Developers programme. Basically, they can advertise the skills of their passionate, skilled users to help the rest of their users when building or designing a Perch site. It’s a really good example of using your community to make your product better.

Christopher Murphy and Education

Christopher Murphy is one half of The Standardistas, the tweed-clad duo from Belfast, who as well as putting out various internet musings and writing great books on web design, also double as educators at University of Ulster. It was on this subject that Christopher was focussing on at Industry, and how we can make education in the web industry better. There were three key things that I took away from his talk: the benefits of a master/apprentice system, the skills we teach versus the skills we should teach, and the importance of paying it forward.

For the most part, the current way of learning in the web industry is either a solo-journey, where the student teaches themselves from a variety of different materials, or as a more traditional one-to-many teaching style, usually through conferences, workshops or courses. However, looking at the master/apprentice model, there are some obvious benefits. Not only is dedicated time given from someone who already knows their craft inside out, but there is also an exchange of skills and values going on between master and apprentice that shapes both parties.

Another interesting point Christopher touches on is that current ways of teaching design focusses on skills, techniques, craftsmanship and business. However, he suggests that we need to look at more fundamental aspects, including self belief, confidence, manners and politeness. He believes that focussing on these core values can help shape a designer much better than just tooling them with the practical aspects of the job.

Finally, Christopher echoed what I’ve been hearing a lot at conferences in the past few years, which is around the concept of paying it forward. Similar to Seb’s call to ‘Play, Create, Share‘, Christopher makes the point that the industry can only get better when we share and teach, whether it be through writing, speaking or just building and talking about it. I completely agree with the sentiment, and think it’s really important that there are people who are looking at what they can do to help shape our industry.

Josh Brewer and Twitter

One of the definite highlights of the day was seeing Josh Brewer, one of the design leads for Twitter, talk through the problems and process of redesigning Twitter. Firstly, it was refreshing to see a company being transparent about their design processes, especially a company as public and big as Twitter. This kind of insight is a great tool to teach others about key aspects of product design, and sharing your failures as well as your successes helps others learn the to dos and not to dos.

Josh took us through the original concepts they had for ‘new new Twitter’, including a key concept of content pivots, where you can easily swipe between your base feed, a photo feed, and a content feed. However, according to Josh, it was a classic example of design not talking to engineering early enough to discuss technical limitations for the platform that meant that a lot of the design features couldn’t be incorporated for this release. Another interesting insight was that a lot of the design features that get incorporated aren’t the result of endless meetings, brainstorms, testing sessions etc, but the insight of a single designer, who then prototypes their idea and convinces the rest of the team that it’s worth putting in. It reminds me of Jay Fanelli’s article for The Pastry Box Project, and how we should be mindful of the fact that when we complain publicly (and snarkily) about something in a service we use, there’s a good chance the single person who’s idea it is is potentially listening.

Wrapping up

This is just a snapshot of the day, and doesn’t quite sum up how inspiring the whole day actually was. From Ashley Baxter‘s debut talk about how she took over her dad’s insurance company at 18, and is now taking it down the software/service route, to the brilliant Noah Stokes talking about his journey as a designer, and the lessons he’s learnt along the way, it was a great day, without one flawed speaker. Special mention also goes to Jeremy Keith, who jumped in only a few days before to cover John Allsopp’s session. As always, Jeremy delivered a session with wit, flair and general awesomeness that few others match. Aside from the talks, it’s always lovely to visit Newcastle and talk to the folks who are building such an awesome web scene for the North East. A huge thanks to Gavin for having us at Industry.

As promised, here are the two sketchnotes I managed to pull together on the day:

 

Matt Denton’s job is a job we wished we could all do! Matt builds solutions for movie special effects but not just software CGI, Matt builds animatronics too.

With an education in electronics and an apprenticeship with Marconi, Matt dropped out of University when he got the opportunity to join a small special effects company. Finding his niche adding the electronics to models made by the company, Matt soon established his own network of movie contacts and created Micro Magic Systems (http://www.MicroMagicSystems.com) in 1999, ‘to supply animatronic, robotic and puppet control systems and services to the film and television industry’.

Matt now offers a number of solutions, both hardware and software, which ‘have played pivotal roles in award-wining productions’, including the Harry Potter series and music videos (Massive Attack) to commercials (Lloyds TSB).

Matt uses a wide range of operating systems to implement his solutions with C. From DOS based systems that ‘just keep running’, to Windows CE embedded, Linux and PIC microprocessors. As most of Matt’s electronics work usually results in custom built circuit boards, he works below the hobbyist module world of Arduino and Raspberry Pi.

He also has a nomadic approach to projects. To keep costs low, Micro Magic Systems doesn’t have a permanent workshop. As projects can be located anywhere in the world, Matt assembles a workshop and a team dynamically, with the skills, tools and location required per project. He does have a trailer based fabrication workshop which includes a high quality CNC device, that can be hired out to movie locations as required.

I first linked up with Matt when my own interest in robotics led me to his Hexapod implementation – which is available in kit form (http://www.hexapodrobot.com/store/). The Hexapod is beautifully made, and can be driven using Matt’s custom HexEngine servo control board – allowing higher level direction control of the hexapod with simple movement commands such as forward and turn instructions from a control machine. The smooth, life like movement of the hexapod has landed it several movie roles where it is usually dressed in an appropriately creepy crawly disguise.

I recently had the opportunity to catch up with Matt on his latest creation; the biggest, all-terrain operational hexapod robot in the world, called the Mantis (http://www.MantisRobot.com). Conceived in 2007, the Mantis has taken several years to make its first debut at the 2012 Bestival UK.

Mantis is colossal, weighing in at nearly 2 tonnes, with a 5 metre diameter in a neutral standing position. Each leg weighs 130kg, and there is a sizable 2.2ltr Perkins diesel engine on the back to drive the hydraulic system. The Mantis hydraulics’ require 165 bar @ 150 litres per minute maximum to move the legs.

This is a big machine, with a suitably impressive computer control system. The key driving system is a Linux PC running a port of Matt’s HexEngine (developed from his small hexapod solution). This communicates to the drive and feedback systems via a CAN bus to two operator control units, the engine control unit (dsPIC), a hydraulic control unit and 6 actuator PID control and feedback units (dsPIC). This is all presented back to the driver under the control of a Grayhill touch panel PC running Windows CE. In addition, there are more feedback sensors and a lighting system.

The Mantis can currently move at a sedate 1mph, although software simulation shows 4.5mph is possible. When you have six, 130kg legs moving under hydraulic control a cautious approach is best. There is still plenty of fine tuning to do which can improve the Mantis performance.

An initial design goal was to have each leg weigh less than 100kg. However, this wasn’t achievable with the hydraulic RAMs available and affordable at the time. Each leg is made from steel; the team now believe that with greater understanding of the stresses and a better structural analysis, the legs could now be made in aluminium. They have also discovered better hydraulic RAMs with built in encoders. Although these were initially thought to expensive, the team found adding external encoders to standard RAMs proved time consuming and added weight to each leg.

Hydraulics of this size was a new area for Matt and his team. Lots of initial trade-offs were made in initial design and purchasing decisions, taking advantage of easily available parts rather than researching more technically challenging solutions. Now with the benefit of the build experience, some of these decisions would be done differently.

The Mantis project has generated an interesting range of opportunities for Matt beyond the normal movie effects; the most notable from a manufacturer of underwater mining machines, who see the potential in the hexapod design to secure a stronger hold on the sea floor. The Mantis is now available for private hire, custom commissions, events and sponsorship.

Matt has a fairly unique job, but there is commonality with our roles as software programmers, and as such we can learn from Matt. Matt has the self-belief to take on new tasks which require learning new skills and new technologies; his prepared to explore the edge of the envelope, the untested and the all new idea. And his has that designer’s eye to deliver a quality of implementation which makes all his creations extra special.

Find out more about .NET Gadgeteer

You’re tired, hungry and can’t be bothered to cook. What if you could pick up your phone and ask it to order you your favourite pizza for delivery without you even having to make a call? Sounds good? Here’s the full story from the team at Future Platforms who built the Domino’s Pizza app for Windows Phone…

“In 2012 Domino’s Pizza added Windows Phone to its range of m-commerce platforms available to their customers, with a Windows Phone 7 app we built for them. The app’s successful development was so popular with Domino’s that it became a prototype for the company’s mobile work going forward.

So in January 2013 we began work on a Windows Phone 8 version for them, looking to make the most of the platform’s advantages. We wanted to not only create a ‘Domino’s store in your pocket’, or even an e-commerce store in your pocket, but to take advantage of the new Windows Phone functionality available on WP8. For example, the menu is rendered within the Windows Phone panoramic interface, live tile notifications notify users of the latest meal deals on offer in their nearest store, NFC tags are activated and voice recognition technologycan activate the app with commands such as ‘Domino’s, feed me’ or ‘Domino’s, I’m hungry’.

“I just sat there staring at the tracker until I heard a knock…I STILL LOVE IT” Jetfire

“The easiest and best way I’ve ever ordered pizza.  Thanks Domino’s I’m no longer hungry.” Christopher

“Great app! Couldn’t ask for anything better.  Absolutely the best way for ordering Domino’s” Marco

“Awesome, works flawlessly. I use it all the time now when ordering a home delivery. Great app, a must have for all Dominos Pizza Windows Phone fans.” Phillip

“Excellent, slick UI makes the whole process simple and user friendly.” Aidan

Alex Vitty, Head of UX, explained the process for designing the user journey; “We tried to keep the design as simple as possible in order for the products to take centre stage. We incorporated the Windows Phone 8 modern UI principles and overlaid the new Domino’s branding. We started the process by mapping out the key journeys from the website and simplified them as much as possible. We combined the journey for order a menu pizza with customizing a pizza which made the whole pizza ordering process much more intuitive.

Once Domino’s had decided to use the NFC and voice activation features we had to define how they would provide most benefit to the users. We reviewed the user journey to establish where they would provide shortcuts to the already streamlined process. This took quite a few iterations before we came to a solution which is both beneficial to the user and shows off the features.

Developers Kader Kawsar and Martin Chandler have a wide range of web development skills, but used C# and Java converted to JavaScript using GWT to run on Kirin: “The app incorporates some innovative Windows Phone functionality such as voice activation and NFC, which required a bit more work. We wanted every feature to add to the app’s usability, rather than just be a gimmick, so we worked a lot on making sure the VA commands do exactly what users want.

The main development tools used were Visual Studio 2012 and Eclipse. VS2012 provides the development tools for coding and designing the interface as well as the tools for unit testing your code. Eclipse provided the development environment for the Java components and JavaScript components of the application. GIT was used as the source control platform for the application code along with GIT Extensions on Windows as a UI to the GIT repository. We used JIRA to manage the sprints and story cards for the application and provide the general burn down etc. for the development.

We built the Domino’s WP8 app using Kirin, which is all about ingenious and efficient cross-platform development for us. Kirin gives us the option to migrate and develop the mobile app functionality onto another platform very easily. This means that Domino’s can move quickly and resourcefully onto emerging mobile platforms in the future, keeping their customers happy and their name synonymous with digital innovation. On this app Kirin made our lives easier because its back end business logic is built generically for cross-platform support.

Windows phone emulator was mainly used for testing during development. The emulator was very good in simulating the features being developed and was very responsive and fast. Real phones were used for key features such as NFC and Voice Activation as well as being used by the test team. Developing with Windows Phone is a totally different experience than, for example, trying to build Java ME apps on the Windows Mobile device in the past, which to be honest was not pleasant. The Windows Phone development environment has a much better IDE and method of development. Setting started with developing the Windows phone apps is very easy with freely available tutorials, samples and tools. However, learning of the concept of Model-View-ViewModel (MVVM) pattern is required for better understanding of the Windows phone development. The MVVM is not a very difficult pattern to grasp. Visual Studio 2012 worked extremely well with Blend, which helped creation of the user interface with ease. Starting up app from scratch with Windows phone is very quick. However, this was sometime a drawback because Visual Studio generated code where were not required, which was acceptable from a generic tool.

Implementation of the voice commands was easy with the Voice Command Definition File. However, getting the phone to behave as required with the voice commands were particularly challenging because some voice commands behaved differently between the phone device and the emulator.  This was probably due the hardware differences.  Since the app was to be used on the mobile devices therefore the final development was carried out on the device, whereby the commands were arranged in certain order for them to be recognised, in order to overcome the difference in development environments.

Voice activation itself is straight forward to implement and the technology examples and documentation provide reasonable information on the process for supporting voice activation. Testing was quite funny to see as various members of the team shouted various commands at their phones – I’m not sure I could emulate an Irish accent myself though!

As part of the implementation we wanted to provide the capability to dive into the application with deep linking too so commands such as “Dominos give me a deal” could be implemented in the future to take the customer directly to current deals for example. This aspect provides the app with a fun feel for the user and hopefully makes them feel happy when they use this feature to interact with the application and their device.

As a relatively new technology the implications of what can be achieved with NFC are not fully realised at present. There are two primary ways in which the technology can assist the user and in the Dominos application we have both approaches in play; firstly as an embedded tag scan which allows the user to scan a tag at a specific point in time – when they’re on the voucher view. Secondly, as an application launch tag which can be used to launch the application – in this case to save a voucher for use later or to take the user to a meal deal. There is a lot of potential for this capability so the features provided by the application may be expanded in the future. Being able to save multiple types of voucher to save money on orders or perhaps being able to drop products into the basket by simply scanning a menu demonstrate how the technology can assist with the users experience of building and placing an order – making it easier.

The implementation itself relies on the same deep linking capabilities mentioned earlier. As with the voice activation features good information exists to assist with the code required to implement the NFC features. The bigger challenge is thinking about how the feature can aid the user and how to make that relevant and if possible fun for the user.

In order to develop and test this feature we needed two extra components that don’t currently come out of the box with Visual Studio or the emulator. The first is the tags themselves as the emulator doesn’t appear to provide any capabilities for mocking an NFC event so you need some real tags to test with. The second component is being able to write the information we desire to the tags. Some third party tools are available for this but we found the example tag writers provided on the MSDN better for our purposes.

Each time we demonstrated the apps NFC features they were received very well and our tags left with the audience and copies of the app!! It’ll be great to see some posters or menus that use these features.

Our strategy with Domino’s mobile products is for them to integrate seamlessly into a multichannel ordering process, so our Windows Phone 8 app does everything their e-commerce site does, such as ability to log in to the same account online or on the app, personalized information for returning customers, shopping baskets and a ‘Pizza Tracker’ to make sure their customers are getting a consistently great Domino’s experience no matter what platform they’re using.

When you’re building apps across platforms, from the developer’s perspective, separation of concern is vital for developing cross platform apps whereby the business logic could reside within the Kirin JavaScript code and the user interface code could reside with native device code. Intuitive and user friendly interface as well as performance of the apps are important too.

The UI needs to be consistent through-out so the user is always sure and comfortable with the choices available to them and what they can do to interact with the application and achieve their desired objectives. XAML provides great support for UI consistency with templates and styles that allow for re-use. These assets can also be re-used on other Windows platforms too.

Consider how the interesting technologies provided by the platform can assist your user with how they interact with your app; to make tasks quicker and easier or to make tasks more fun and interesting. “Shake me” to add some sides might be a useful short cut in the application but it might also frustrate the user if it happens in error so don’t use a technology feature just because it’s there.

If it can’t be slick then make it easy; in some places you may need to collect a reasonable amount of information from the user so try to make it as painless as possible.

As with any application the internal architecture of the application itself is important so the application remains responsive every time the user performs a task. Consider your deep linking functionality upfront as this will also help to keep your implementation cleaner and more focused. Async, async, async – make sure everything that can be performed in the background is performed in the background.

Tools for me have been a key feature of the Microsoft technology stack. Visual Studio is slick and efficient and provides just about everything you could think of for developing just about any type of application you could imagine. For business applications the ability to develop secure and scalable back-office applications with front-office components built in the one technology and then deploy those features to users through a range of different devices from Phone and Xbox to tablets, laptops and desktops – it represents a very unified corporate world. The tools help make the Windows development process more fun than building Android or iOS although the tools for these have both improved massively in the last couple of years.

If you’re still undecided whether to start building for Windows Phone all I can say is get involved. Currently Windows Phone has a smaller market share than other platforms but that’s also a great opportunity to get your app recognised on the platform early. The devices running Windows Phone 8 have been improving too so they really can compete against the phones that run other platforms. With the added benefits of the Windows desktop market and the Xbox gaming platform your app can reach a very wide and diverse audience not being restricted to just the phone and tablet. That said the tablet themed devices such as Surface Pro that can run a full Windows 8 desktop are starting to appear so we now have a tablet that can do more than play games, surf the internet or read email.

I can imagine it won’t be too long before I can order a pizza directly from my Xbox, flick through the menu by gesturing at the Kinect and then back to my movie!”

For the majority of us, cheesy kung fu movies are something we grew up with and if we’re honest still hold a secret passion for. That’s why we were so excited to interview the studio behind Buddha Finger, which has really captured that 1980′s feeling while also providing fast, exciting game play. We chatted with Anna Marsh, the Design Director at Lady Shotgun studios to find out a little more about the project.

What, in your opinion, is unique about Lady Shotgun as an indie game studio?

I started Lady Shotgun initially because I’d become a mother, and I wanted to work flexible hours and cut the commute out.  My friends Sarah – who I’d worked with at Eidos – and Gaby – who I knew as our children went to the same creche – were both in similar situations.  That was the catalyst, the three of us wanted to create something together around our childcare requirements.  So that’s pretty unique, a studio started by three mums   For Buddha Finger we all worked from our own homes and although the company has outgrown my home now and needs to move to an office space, I’m really keen to allow our team members who prefer to work from home do so.  Commuting can be such a massive waste of time and energy in my opinion and when people can work their favoured hours rather than being forced into office hours I find they’re far more productive. So that aspect means that we can employ a far more diverse range of developers than many studios, indie or otherwise.

What is the inspiration behind Buddha Finger?

I wanted to design a game that really used the touchscreen interface in an immediate way, I like designing what the game is going to feel like first so I was searching for something that would feel great with a touchscreen.  I was watching Kung Fu Panda with my daughter and the part where the old wise tortoise Oogway beats the powerful tiger Tai Lung, I realised that the touchscreen would be the perfect way to capture the feel of that mystical kung fu pressure point attack. The mechanics were inspired by Elite Beat Agents – press the points in numerical order – but instead of it being based on rhythm, it’s based on how fast you go. That introduces an element of risk/reward, the faster you go, the higher your score, but the more likely it is you will make a mistake.

How did you settle on the final design and style of the game?

I adore kung fu films and those cheesy 1980s action movies with Jean Claude Van Damme, Steven Segal,  and that seemed to suit the idea of the mystical kung fu style well, so we based our aesthetic and narrative on this idea.  I had a lot of fun looking through reference stuff with Gabriela Pavan, the lead artist, and picking out actors and poses to base the characters on, and coming up with ideas for locations and story with writer Katharine Neil (whos a great indie developer in her own right!) inspired by these films.  Katharine did a lot of watching these kinds of movies for research too! She called it a Van Dammathon

What’s your process for designing the user experience / journey?

I have quite a particular way of working actually – if I can’t fully visualise the fundamental, “second to second” gameplay I find it impossible to do anything.  So I spend some time holed up on my own working that out on paper, then when I understand it, I can start talking to the rest of the team and feedback.  For Buddha Finger after I’d worked out the gameplay, I made a flow chart with all the skills we need to introduce to the player, and roughly the number of levels we were aiming for, then I sit down with the story writer, Katharine, and we started to spin out ideas for. Gaby had already designed many of the bosses, so looking at them and coming up with who they were and the locations they could appear in gave us the skeleton of the story, and we fleshed dout using our “kung fu/cheesy 1980′s action film” reference. And finally, I then tried to ramp up the difficulty throughout the game, and use some special levels with different “enemies” – like, a woman in labour, you help her give birth with the power of you kung fu technique! – to mix things up a bit.

What do you think the biggest challenges are in designing for touch screens compared to traditional inputs?

I much prefer designing for touch screens now actually! I think they’re more immediate and intimate than traditional controllers, the player is directly in touch with the game. The big change is I think that with a controller, most of your actions are relative to a player character – jump, punch, shoot, whatever.  With a touchscreen, the actions become more relative to the whole screen – so, if I want my character to move forwards I tap somewhere in the environment  for them to move to, rather than push the character forwards.

With Buddha Finger I designed something that just wouldn’t work with a traditional controller because I wanted to use that interface in an immediate way, it translates a real world action of pressing points with your fingers to pressing those points on a screen, its quite a direct translation of the real world to the game world which is why I think it works.  I wanted to make players feel like “finger ninjas”, so I spent a lot of time setting up the positions of the points and the time pacing between them, so that the player’s hand movements would become something reminisent of classic kung fu film choerography.

What is unique about the Windows/Windows Phone versions of the game?

So far we’ve released only on iOS before, which we did simply because we had the most experience on this platform. For Windows we have altered some of the text and images to the age rating below 12+ , we’re on track to add an “easy mode” very soon to make it easy enough to play for younger players.  We’ve also added some improvements to the UI – the direction of the spiral points is much clearer for example.  And, we’ve included a trial mode – which is made very easy on Windows because there’s no necessity to add IAP to do it.  That i’m very pleased by – letting players try before they buy is really key to showing the game off.  For Windows 8 we’ve also included mouse and keyboard controls and a landscape screen mode.

What is the most important lesson you learned while developing Buddha Finger?

Patience   You have to take it as it comes as an indendent developer – you simply don’t have the resources to brute force things through if they’re not happening naturally.  Coming from console development, it can be difficult at first but you soon learn to keep a variety of stuff to do on the task list so if, for example, your audio person has to take a paying freelance job to pay their rent or whatever in the middle of implementing sound, you switch to doing some PR stuff for a while. that way you keep things rolling around obstacles.

With each of the founding managers working in different countries, how does that affect your development process and what tools do you use to collaborate?

The whole team for Buddha Finger worked from their own homes, and we were pretty scattered! The only way we can do this is by being very organised, I did a load of preproduction right at the start of development that allowed us to break the game up into chunks and assign to the different team members.  We used Team Lab and Assembla to co-ordinate tasks, and I’ve used Jira with Lemon Moose who have helped out with the ports.  Keeping everything in one place using one of these tools this helps a lot, it can be very difficult to find informaiton in emails after just a few weeks working on a project.

How do you build your games to work across a range of platforms?

Well we originally started off as iOS native, using Coco’s 2D, simply because it was the platform the team had the most experience in and this was the fastest.  In future we’re looking to use a cross platform engine from the get go though.  We have partially used Marmalade for the ports but almost all the Windows version is Lemon Moose’s own game engine.

One decision that really worked was to make the game as data driven as possible. That basically means that the code provides the framework to the game, but almost all the content – which enemies are in what levels, how the levels and cutscenes link together, where the points appear on each enemy and the scores the player will ge from pressing them – is kept in XML data files.  It keeps the code as mimimal and clean as possible and lets the coders concentrate on code, whilst I concentrate on making the game fun to play.  Its meant that Lemon Moose have been able to put together the ports reletively swiftly.

What advice would you give anyone working across platforms to make sure they stay true to the ethos of the OS, brand guidelines etc?

Using a cross platform engine helps a lot with technical issues. There are downsides, of course, but for our next projects we’ll do cross platform from the get go.  Doing submissions accross mulitple app stores can take up a lot of time so make sure you have a team memeber who’s prepared and has the time devoted to do the submissions.  There can be a big difference in how age ratings are treated between platforms for example, and screenshots must be correct proportions for each platform.

There are some noticable “brand” differences between the platforms in terms of content – a quick evaluation, I would say:  Apple seem to be focus on games with high production values – a strong, beautiful aesthetic is important. Windows is very family orientated and like games parents and children can play together, and particularly Windows 8 is very hot on age ratings.  BlackBerry are keen on social aspects like leaderboards being implemented. Android I admit looks like a bit of a free for all right now!

I suppose the key thing is to make a great game that looks good and then you’ll improve your chances on all platforms.  After that, you need to either focus on one platform at a time for your submissions, or make sure you do a lot of prep work on all platforms to make sure you’re ready to submit on all of the simultaneously.

What drew you to the Windows 8 and Windows Phone platforms for the game title?

I was showing Buddha Finger with Katharine at the Eurogamer Expo and a former colleague of mine who now works for Microsoft passed by and played the iOS version. He loved it, and passed our details to the Phone team and when I got in touch with the team they were so very enthusiastic and supportive that it swayed my decision to make the first port to Windows.

What has been the experience in developing for the platforms?

Excellent! Granted, we’ve had a few hiccups in the submission process which seems just due to the newness of the platforms, but there’s excellent access to support from Microsoft.  As well as the awesome tech evangelist we’ve been working with the online support is great, you can get tech support via instant chat system which is very helpful.

What’s next for Lady Shotgun?

We’ve got few projects potentially in the pipeline, we’ve got as far as a couple of basic prototypes and some very sweet concept art!  One is a FPS with intuitive touch screen controls, and the other something for older tablet owners. I’m very excitied by the possibilities but to be honest I wont’t get time to really concentrate on anything properly until I’ve done a few more weeks of PR-y stuff for the Windows Buddha Finger.  One of the things about being indie which is simultaneously great and hard is that I do so many different jobs, I’m designer, project manager, PR, QA, production and art intern, business development…. I’m the only full time member of Lady Shotgun so it can get crazy! But, it can also take me in really fun and interesting directions so for the time being at least, I’m enjoying going with the flow!

Ready to build your game? That’s great, register today for a Windows Store account, download the Windows 8 SDK and you’ll be flying.

Or do you want to get something built in just 10 minutes?  Then  make sure you check out ZipApp.