Rollscape

A game where you develop your reflexes by avoiding obstacles with simple mechanics at different levels, basically focusing on having a good time. While doing all this, it aims to relax the player with its stable design and colorful content that does not tire you and your device. At the same time, it has been developed to establish direct one-on-one contact with entertaining content in addition to development with its worked-on graphics. Goals of the game: + Using fun time-spending techniques while spending time. + A great first impression with access to interesting content. + Offering understandable puzzles with basic mechanics. + Applying psychological techniques for a sense of accomplishment. + Applying psychological techniques on the sense of curiosity in people by ensuring continuity. + Applying dynamic memory usage management by capturing the moment when visual content, mechanics and story are simply the most productive at the same time, creating wonderful short-term memories in the player's brain. + Keeping the player in a semi-conscious state for a short time. In other words, ensuring that environmental awareness is semi-maintained without fully focusing on the game. + Applying techniques that will make the player feel psychologically safe. -- The game has new but solid foundations. However, the game needs to be taken care of additionally outside of the normal development process. Our development team is always aware of this, and in order to turn some of our disadvantages into opportunities, such as the small number of team members, experience problems in our infrastructure, etc., we prefer to structure our working model in a way that is one level more intertwined with the user compared to normal methods. According to all these, we manage a feedback process that will be our policy. Therefore, starting from this application, we would like to provide information about this policy specifically for this application. Feedback: - Regardless of the characteristics of the users, all feedback to the application is recorded by us. - Feedbacks are divided into groups, primarily problems. - A sorting is made among the problems according to their complexity, and the priority is focused on problems that will not disrupt the stability and can be solved. - The second most important thing for us is the requests and feedback for adding new features to the application. However, we do not group them specifically. Therefore, with an open voting logic, we try to implement the development request we encounter the most, if it is something applicable. -- Our development team is the most important part of our entire process. So, if we need to give some information about them. Development Team: + We prefer to work with fewer people than we do. However, don't get me wrong, this is a simple method we need to apply to increase our resource amount per person. + We prefer to be efficient in our projects. Therefore, we think at least twice when we start work that we cannot achieve. + Not directly during development, but our content always focuses on achieving more functions with fewer resources, as if there was a resource shortage. However, it is important that this situation does not make the content multifaceted. + Our direct response time may be short. For example, if you send us a message through our communication channels, we usually try to respond immediately. However, it may take a long time for your request to reach a conclusion, as we are generally focused on determination. + We are always open to development, that is, suggestions, and our team's motto can be said to be "to produce digital content in the simplest way with the least resources." + We make a formal planning process for every work we do. This will happen automatically according to our development policies. Because we are few in number, we need to put our actions in a certain order. We first announce these plans on our website.