In fact, mobile game development is a process of continuous development, sometimes (often) means the idea will be to fight back program, and try again in the future. Therefore, we prefer to feel that they have a reliable answer, and then get players to share the details about a certain topic.
Maybe we can create a community manager on "in the office talking about" what it was like in the end a detailed overview (including examples). Through a story to tell Diablo 3 items Describe the middle of the process, whether technical, budgetary, art, copywriting, translation, testing, anti-workers, all of this. Through this real-life examples, you can help your users understand the changes in the end is how it happened. Sometimes the best way is to let everyone know "how sausage is made out of."
Development process by opening the window, you can greatly reduce the forum "What are they doing?" Or "How hard can it?" Such a meaningless post. Let us look at the developer's hard, let's look at how some of the ideas are ultimately rejected because of stringent scrutiny, of course, let us also look at those success stories buy d3 items.
Do not offer players "It's hard," such an interpretation, or the context of the development process type description please say more detail some of it. We do not want to know your secret formulas or trade secrets, just want to learn traditional development management process.
没有评论:
发表评论