Summing up the results of the recently completed online competition among developers, its organizer – the company Snegoffon – highlighted a number of questions that every developer should ask himself before starting work – and shared them with App2Top.ru .

Snegoffon - о чем должен спросить себя разработчик перед разработкой

The competition started in March of this year and lasted three months. The incentives were: a cash prize of $ 41,200 (distributed in several categories), the opportunity to “show yourself”, as well as get advice and recommendations from experts.

A lot of good works were received, but there were also bad ones. Of the two hundred projects sent, nineteen reached the final. A third did not pass the first stage of moderation, the rest fell away halfway to the final. Based on the unsuccessful experience of the participants, as well as on the list of the most common mistakes, we have created a list of questions that every developer should ask himself before creating a product.

1. What do I mean?

The analysis of the results of the competition showed that a fairly large proportion of developers do not formulate their thoughts well. The task of the contestants was to present their application or the idea of this application in the form of a description of the gameplay and a general vision of the future project. What happened: a stream of thoughts divorced from reality, a crumpled narrative in several paragraphs, numerous grammatical errors.

Why is this a problem?

The market for mobile games and applications is already very large. However, if you cut off the TOP, start carefully sorting through and reading into already published projects, you will notice how many games / applications there are also vaguely described or described with errors. They have practically no chance of living, not to mention a good income, and after all, time and effort were spent on the creation.

How should I?

Whatever goal you have in front of you – participation in the competition, filling out the application description, writing a review, press release, etc. – do not be lazy, approach it wisely. Write simply, to the point and, of course, without mistakes.

2. How original is my project?

If you suddenly decide to create a game, check out the app stores. Perhaps someone has already created fifty such games before you, and the user is still playing the ancestor application. Is that so? Think again!

During the development competition, it turned out that developers do not like to invent new things, preferring to look at the TOP, take an idea, replace the main “animal” and make another clone.

Why is this a problem?

The user perfectly distinguishes the clone from the original. And in most cases gives preference to the original project.

How should I?

Even if you haven’t come up with a completely new idea, think about how you can improve the original application. It is to improve, not to change. Ask your friends what they lack in this application, create an impromptu focus group and make the product as different from the original as possible.

3. How am I going to make money from the game?

And here is another common problem of developers, revealed during the competition. Getting more or less interesting work, the expert council always asked the author the question: how are you going to monetize your application? And almost always got a strange answer: “monetization is not provided.”

Why is this a problem?

Altruism is a good thing, but the activity should bring income. Otherwise, you will soon become both uninteresting and time-wasting.

How should I?

The sources of monetization are thought out in advance, at the stages of project planning. Ideally, there should be at least two or three of them: a paid product, advertising, offers, internal sales, etc. Study this question and choose the best option for your application.

4. Did I overcomplicate the game?

This point, of course, is subject to discussion and not in all 100% of cases is the only correct solution. However, within the framework of the developers’ competition, the expert council gave preference to applications and games from among the simple ones. Easy, understandable to a wide audience plot \ functionality, user-friendly interface, a sufficient number of explanations. Such projects were in the final of the competition. Among them, for example, the game “Grow a tree”, during which the user greens the planet; a service for co-writing books and articles; a useful project in everyday life “Home cook” (will prompt a dish consisting of ingredients in your refrigerator); a cute designer of video novels “Line of Dreams” and so on.

Why is this a problem?

Not really a problem and there are, indeed, complex developments that require special functionality, management methods, etc. But, if you are working for a wide audience, then the product should be appropriate.

How should I?

If your target audience is people of different ages, professions, views, and you are rather creating an entertainment product, try not to complicate your development. Do not load up with unnecessary information, do not pile up the interface. Try to speak to the user in a language that is accessible to him. Add hints, virtual assistants – everything to make it easier for the user.

5. What will the lawyer say?

At first, the developer works for himself. One day he may have a publisher, or the opposite may happen. To prevent this from happening, study the legal issues of the digital world, copyright. There are a lot of pitfalls, changes often happen. For example: several projects came to the competition, the rights to which, as it turned out already at the awarding stage, already belong to legal entities. And this became a problem, because according to the rules, work that was not burdened with legal responsibilities was accepted, since the organizer was looking for projects for his publication. Further proceedings cost nerves and time to both sides. As a result, the authors who violated the rules did not receive prizes.

Why is this a problem?

As you know, life is full of surprises. Suddenly, someone may offer you to buy out your project or, for example, accuse you of plagiarism, and perhaps you yourself will find that your game / application has been cloned and is being promoted with might and main.

How should I?

It is necessary to be “in the subject”. To do this, study the experience and mistakes of colleagues (read the blogs of developers on the web), familiarize yourself with copyright and always read contracts, agreements and rules before taking part in an event.

Tags: