Misc Posts

My Third Coding Epiphany

My Third Coding Epiphany

I have been meaning to write this post for a while now and since I have spent most of this month back in the UK visiting friends and family I don’t have all that much to share technically so I thought it was about time I got this post done.

Over the course of my 23 years of coding I have had a number of what I call “Code Epiphanies”. These are moments in my coding career where fundamental changes in how I code have taken place.

Why I probably won’t be making another mobile game ever again

Why I probably won’t be making another mobile game ever again

Exactly one month ago I wrote about a new app I had developed for Android called Credit Redeemer. Thanks to Google and my naivete this simple one week project has dealt a crushing blow to my indie game development career.

The idea for Credit Redeemer was simple; allow users to convert unused Google Play credit into paypal payments.


I thought as there were 3 other competitors on the market that did the same thing; Rebatr, Payback and Cashify then Credit Redeemer would be fine. I was a little worried about the terms of service but I assumed as they had been on there for years already then must be fine.

3 days after launch I received this email from Google:

Needless to say I was shocked, worried, upset and annoyed. Not only was Credit Redeemer taken down but my entire Google Play Developer account terminated including Mr Nibbles, Mr Nibbles Forever and Ectoplasm.


I of course immediately appealed stating that I wasn’t aware of any previous violations and asking for more information. Surely it must be some sort of mistake? 3 days later I get the following:


Wow okay so now I am really worried. It seems like it’s a robotic reply, even if “Bruce” is a real person he certainly hasn’t read what I said in the appeal and hasn’t offered any more information or reason for the lack of extra information.

At this point I decided to dig back through my inbox looking for previous mentions to Google Play and violation. The only thing I could find was from 2 years ago when I received what I believed to be warnings regarding an OpenSSL vulnerability in the AirSDK.

I didnt action on the error as it was for Ectoplasm, a hackathon project, plus I was travelling at the time, I assumed that it would just be automatically disabled. This was a big mistake I really should have paid attention to it as this counts as a strike against your developer account.

I emailed “Bruce” back again and received:


So thats that as far as Google is concerned. They offer no other way to appeal or state your case.

I decided not to give up just yet. I contacted a couple of friends I knew who worked at Google. One said they couldn’t get any more info other than the public appeals page and other did get a little further and received the following:


Wow, so finally I can confirm that it was indeed Credit Redeemer that was a cause of the ban. Money laundering does indeed sound serious but I wasn’t aware that the app was money laundering else I wouldn’t have even started it.

I know ignorance is no defence when it comes to the law but I assumed that as there were other apps on the store that did the same thing and had been there for years precedent had been set and is still being set as Rebatr is still on the store.

It seems really seems unfair that I got a total account ban without a warning, I think my reply sums it up:


It has been almost 2 weeks, I have had no reply.

I have tried contacting some people from the Google Developer Relations department on LinkedIn (yes I have resorted to spamming LI) but they just give me the party line “use the public appeals process” before they stop replying.

Short of walking into the Google Office (someone else in the same situation tried this already and got turned around by security) then I don’t know what to do.

So I think thats it. By Google’s rules:

Do not attempt to register a new developer account. Any new accounts will be closed and your developer registration fee will not be refunded.

So I may never attempt to re-upload any of my other games and I may never again upload anything to the Google Play store.

Thing is, this doesn’t just stop my ability to make games for the Google Play store it probably stops me from ever making a mobile game ever again. Why would I start working on a mobile game when I know that even if it’s a success on iOS I can never port it over to Google Play?

So if you have any suggestions on other avenues to take or people to contact then please do contact me: mike.cann@gmail.com.

Indie Game Project Management with Trello

Indie Game Project Management with Trello

Project management is one of those things that can easily be shrugged away and forgotten about when developing indie games. The temptation is to just leap in and start making without any thought to what the priorities are or how long things are going to take.

This is all well and good when its only one of you working on the project but when you start involving multiple people things get a bit more tricky. It becomes difficult for everyone to know what everyone else is doing or what they should be doing next.

There are lots of tools out there to help with project management such Zoho or Teamwork. I invested quite a few of them but in the end I settled upon Trello.

Trello isn’t strictly a project management tool per se rather its more of a flexible organisational tool. You can use it however you want really and it’s that flexibility, ease of use and importantly pricing (free) that attracted me towards it for managing my indie game projects.

Projects are split into “Boards”:

screenshot_021 Sep. 21 13.48

Within a board you have a number of “Lists” which in turn contain “Cards”

screenshot_022 Sep. 21 13.49

Cards and easily be created, removed and dragged between lists:


The way I use it is to have each list represent a milestone or category and each card represents a single task. When a task is completed it is simply dragged to the “Done” list:

screenshot_024 Sep. 21 14.20

Priority is indicated by the order in the list, the higher the card the higher priority. The person responsible for that task is indicated by who is the “member”:

screenshot_025 Sep. 21 14.22

A task using labels I can indicate some important info about a particular task such as it is blocked for example:

screenshot_026 Sep. 21 14.23

Clicking a single card lets you bring up its details which lets you attach files for that task, add a description, checklist, comments and much more:

screenshot_028 Sep. 21 14.24

For me its a really flexible, simple cost effective and (oddly enough) fun way to manage a small indie project.