Historical Portfolio. Part 1: Introduction

  • PublicPublic
Historical Portfolio. Part 1: Introduction

Hello, this is Alexander K., founder of Cyborgs.pro. This is the first part of our portfolio, and it is not a showcase but a story: the company's path from its founding to today, through the conditional "eras" of mobile development that we have lived through ourselves.

The decision to create the company was made in September 2013.

If you remember those times well, feel free to scroll down to the first projects. If you were young back then, read on: it will become clear what we had to work with and how.

A Short Retrospective

Operating systems. Android 4.3 Jelly Bean (July 2013) and the fresh Android 4.4 KitKat (October 2013). Apple released iOS 7, the very one that started the "flat" design trend.

Devices. On Android, people fixed the Samsung Galaxy S4, HTC One, LG Nexus 5, and Samsung Galaxy Note 3. I had a Sony Xperia Z, a waterproof flagship from the Japanese, almost science fiction for its time. China was only just making its way into the European market: the popular ones were the Huawei Ascend P6 and Lenovo K900, and for geeks the Xiaomi Mi2S and Mi3. Put CyanogenMod on one of those, and it turned into a rocket.

Apple had the iPhone 5s and 5c: compact, with no water protection and no wireless charging.

Games. It was a funny time. Everyone was hooked on Doodle Jump, the hastily thrown-together Flappy Bird became a hit, everybody was running in Subway Surfers, and at the other extreme stood the monster that was Asphalt 8.

A Mistaken Idea

I've been in IT since 2003. Sometimes I played games on my phone and looked at the hits, and a thought took root in my head: "What blows up can be made on my own, without much effort. The games are simple, so popularity won't keep us waiting." How wrong I was!

To that end, we put together an offline team: me, a designer, a programmer, and even an office manager. She also ran, and still runs, all of our social media. The term SMM still sounded exotic back then: we posted on Google+. Does anyone even remember that? And now there's no saving us from her videos :)

The Cyborgs Engine

The first thing we did was write our own engine, Cyborgs: in Java and for Android only. Today, if you want to make a mobile game, there is a whole bunch of free engines to choose from. Back then Unity was raw and buggy, and almost nobody had made mobile games with it yet: for a light 2D game on Android it was a heavyweight.

The engine let us make very fast games: basic physics, sprite (and later skeletal) animation, a level editor, and a pile of small things. It weighed about 300 kilobytes. An empty Unity project today weighs 10 times as much, or even 50, while our whole game fit in half a megabyte.

The homegrown engine became the core, the seed of the company, from which everything else grew. It's a pity that a few years later we lacked the resources to develop it further: we had set a very high pace after the start.

First Games

Christmas Snowman Jump. Our first test and an analog of Doodle Jump. You jump endlessly, shoot, and dodge trouble. The game turned out fun, attracted a few thousand players, and gave us our first experience. The shot sound, that very "pop," was recorded by our designer using his own voice. So the snowman "popped" enemies in no time, however that may sound ))

Christmas Snowman Jump is our first test and a Doodle Jump analog

Space Brain Defence. A hilarious gyroscope-based game. The robot shoots on its own, while you control it by tilting your phone and by triggering a super shot. Like in the 1992 Galactix, the enemies swarmed, flew around, and broke apart into pieces, there were a couple of bosses, and everything used sprite animation. Two locations with several levels each.

Space Brain Defence: gyroscope shooting, two locations, and a couple of bosses

I still really like this game. Maybe I should bring the project back to life? The source code is lying around somewhere, and the APK for Android 2.3 through 4.3 has survived. I wonder if it would run on Android 17?

First Orders

Orders started coming in, and we built them on our own engine.

Flying Flurry. A 2D side-scrolling runner about a helicopter.

Flying Flurry is a 2D side-scrolling runner about a helicopter

Kite Flight. Either a vertical runner or Doodle Jump, or rather a mix of the two. You control a kite, fly upward, and dodge obstacles. As far as I remember, it couldn't shoot: the kite had no turrets, after all )

Kite Flight: a kite flies upward and dodges obstacles

On outsourced projects, we learned how to build turnkey apps. Clients needed analytics, Crashlytics, and various ad aggregators. We were integrating all of this for the first time, and on top of that, into our own engine.

Flash Cards: our first earnings

Even then, app stores allowed selling additional chapters and extra content. We tested this on Doman Flash Cards: half of the cards were free, half were paid.

Flash Cards: Doman cards, half free, half paid

For those who don't know: these are pictures, static or animated, that children use to learn objects and language. It's simple: the child taps the screen and gets a picture with its name. It's a good app, and my own kids used it on tablets too.

It was this app that brought the company its first money from its own apps.

Lessons of the first era

I've already written that we were wrong. Here's another mistake: we believed that ads inside our apps would bring in money. If you have thousands of users, they won't.

This gave rise to one of our core principles: expertise. Over the years, we've learned to say honestly what will work and what won't. Today neural networks learn from this kind of experience, but we went through it ourselves, with our own money and our own time.

Instead of an afterword

These are the days of doomscrolling: people flip through their feeds faster than they read. But you read all the way to the end, and I sincerely congratulate you on that!

In the next part, I'll tell you how the story of our engine ended and what happened next. Stay tuned! ))