Wednesday, September 28, 2011

Radio Silence

Hey gang,

This is going to be a pretty long post as there is quite a lot to cover and I want to go over everything. So, as anyone who reads my blog is aware, there has been a long time since the last post, there has also been a lot of things happening on my end but I won't make up excuses, I've been lazy. I've also been flagging at my app idea, which, unfortunately, is now in the trash can until such times that I can be bothered to pick it back up again.

The issue with Flip the Switch (it got a name!) was that it was structurally broken from day 1, there are so many holes in the code as we speak that the more efficient way for me to fix it would be for me to start again - which, co-incidentally I'm doing! My major gripes so far with developing for Android with Flash, and anyone who is thinking of getting into the market as well, please consider this list before you get started, as it'll save you a lot of time in the long run.

 - Flash to Android debugging; is a really annoying thing to set up and to run in the background whilst you micro-manage code. It's fiddly and if you run a few harddrives on your computer like me, you can spend ages with annoying error codes in Flash Builder as one thing can't see another thing etc. etc.

- Android Manifest.xml editing; this one is slightly my fault, I will admit, but I'm yet to come to a suitable fix for the issue as well. There is one thing that will always get game developers when you start developing for android - you have to deal with different resolutions, different dpi's and different hardware. The first two are the most concerning, because anything that you code into your game in pixels is going to come out different screen to screen, it's possible to make this a little easier on yourself through some pretty complex Flash coding - which I'll be posting up here in the vain attempt to get a little more traffic through, but all in all, it's pretty damn hard to get the swf file to scale to different dpi's and screen sizes and not have issues with sprites being cut off.

- AMAZING ANDROID 2D BOX COCO ENGINES! This is something, that I have to say, after almost a month of going through has irked me more than anything. I don't know if it's a personal trait, or if it's a global problem that the world suffers, but in the last month, I've tried to learn to use no less then seven engines for Android, most of which, obviously are based in Java, but boast "Amazingly easy to learn!" & "Instant integration!" I've got to say, it's saddening to see things like this. I'll be honest with you, it's great if you're able to get your hands on a fully fledged game engine and just start pumping out games - but realistically, the chances of you being able to just pick one up, and unassisted (most documentation is pretty lax) just start to churn out great game ideas, are not great.

This has been the single biggest time-waster that I've had - I come across a problem with my current code, go searching and the only support that I find goes something akin to this "Oh, I had this problem, and then I started using engine X and all my problems were fixed and I found five bucks!"

I've come to the conclusion that if you feel the need to use an external game engine you're one of two things:

 - Lazy
 - Shouldn't be programming games.

Getting help phoned in is (I feel) cheating, if there is something that the game engine does that you don't understand (it just does something magic and you get a game out the other end) then you shouldn't be using it, I've started to program a new game, and I'm essentially laying out a fully functional game engine to go along with it, and I'm going to take the long road and learn how all the parts fit into each other - it's going to be harder and probably more frustrating then going and picking up one of the many free engines, but when I'm through with it, you know what? I'll have my own game engine that I know back to front and can manipulate as I see fit, and no open source, free, paid for, whatever, engine out there can say that for each individual user.

As you can see there's been a bit of a block in the creative flow of my programming, which has largely been caused by needing help and being confronted by a bunch of mindless Zombies reeling off engine names at me -.-

But, there has been other things that I have come across that I feel contributed to Flip the Switch going onto hold. Such as the fact that in all reality, I was finding it very difficult to code anything new into the game and as such wasn't getting any closer to putting something onto the market, and this is the big thing! What I want is something that is going to be quick to develop (relatively) can support itself (ad support) and will ultimately give me a good idea of what it's like to receive feedback and change and update a game depending on what the users have to say.

Those three points listed above are something that I want to talk about too; having something that is quick to develop from idea to prototype to beta to release is CRUCIAL in the app field, because if you've thought of it, you can almost guarantee that there is someone else that has thought of it too and might be quicker at coding then you, or have a team of monkeys with him to help. So the simplest ideas are often the best - and when I first sat down to think of ideas, Flip the Switch seemed simple, I was thinking of all of the elements that I was going to implement, and now on the other side I can appreciate more then ever exactly what goes into a games development.

Having an app that supports itself is something that is very important too - and it's a real problem for people that are developing through AIR for Android as there is pretty much only one choice - AdMob, which you can put as a overlay on your game, app or whatever and just sit there. The real problem with that is that AdMob isn't exactly know for it's great income, and the mobile advertising market is something that belongs in a complete other blog post (yes, I'll do one, I promise.) But the major companies that are doing advertising that you can use in an app are things like Millennial Media & TapJoy - both of which only offer a Android SDK - which of course is in Java, and totally unusable by myself. So admittedly, from an income perspective, Flash - not the way to go until such times as there is support for people such as myself (when it happens, it will be a happy day!) This then leads me back to my freemium post which I made a while back, but I'll cover again in another post.

Finally there's the feedback that people that use your app will give - negative, positive, anything that a person says about any app that is made will change what is done to it in future updates, and as such, having a total of 0 apps on the market, means that I have NO idea if any of my game ideas are going to sell well, if at all!

Well, that's pretty much all that I've learned about the fickle mistress that is the Android App Market since you last heard from me. Where am I going from here? Well, I'm going to cut a lot of the fat away from what I've been developing over the past month, it's been in drips and drabs, and ultimately has led nowhere so I want to perk things up and start afresh and see how that gets me going. I'm starting on a new game, but am taking a real solid interest on getting the game engine and logic side of things right so that should I get to completion of the game I'll then be able to use that knowledge, and even perhaps some code on new projects that I start.

The game that I'll be making (and I know it's already on the market, doesn't mean I'm not going to make it) is a simple constant scrolling game, using the accelerometers in the phone or keyboard input move your player back and forth to drop down slots to avoid being pulled off the top of the screen - simple idea and with a bit of polish can go far. I'm not going to try and aggrandize this idea with anything else at this point - I'm going to release it with a easy, medium and hard difficulty, a scoring system and that's it.

I'm not expecting it to go far, but what I do want to do is get it out there! And then once I have, start working on more additions to it to get people coming back (think new power-ups etc etc.) But for the mean time, I'm working on this simple idea and am sticking to it till it's done.

Another thing that I wanted to do was to organize starting to create some tutorials for any aspiring app creators that might happen on my blog (I dunno, they might :S) But I'm going to try and put a few together with my own personal spin on them for people looking to make games with android using just a simple physics engine and their own know - how.

In the mean time though, it's three in the morning and I need some sleep I think... Maybe.


Post a Comment