![]() Users are often welcomed with messages like this: I place links and buttons inside the app that lead users to functionalities that are not yet developed. One of the best way to do this is by using action intent hints. Our users will be in charge of how the product will be shaped from the launch moment and on. This means we launch products not when we believe that particular products is ready, but when we think that, even if not ready, people will find it useful. We are big fans of the Minimum Viable Product model, though Rand from moz.com got us very curios about the Exceptional Viable Product model. While the first version is easier to implement, the second allows us to check the actions for each user so, if he will contact us via support or sends a tweet or visits our website from a different device, we’ll already have a nice history of his actions.īased on the logs we can then generate charts like the following, that give us a broad look on actions taken by the users: Action intent, true feedback We’re taking a bit more complex approach, but it pays off: as user actions are happening in more than one visit session, we setup logs in our app that save each user action. The easiest way to deal with this is to setup a Google Analytics funnel for the process. Without getting through them, they will never become potential customers, so tracking how they are dealing with each step or action is vital. Completed actions, just as important as errorsĪs the first users are getting welcomed by the application they’ll need to go though a number of steps and actions to see the benefits of using it. You’ll move on to better error tracking methods, but for now, it’s the easiest way to track the errors in your app and react quickly to them. In time, the number of errors will grow and this will overwhelm you. So, no matter if I am in front of my e-mail or not, I am aware of the errors going on in my app in real time. On my smartphone I use an e-mail push app that will notify me with a splash screen and sound signal each time an error occurs. I then forward all those e-mails to my own account. Here is how I usually deal with it: setup an e-mail account with the sole purpose of receiving e-mail errors. It’s even better to communicate with your users via e-mail and let them know you area aware of the error and it will be fixed asap.īeing proactive is something we can afford at this stage and users love it. If you are notified in real time about possible errors, you will react accordingly and try to fix it asap. At this point, reaction time and communication are crucial. Nobody likes errors, especially app users. Like it or not, users will encounter errors when dealing with any app, especially if it is new one. More than anything we need hints on how to make them love our application. We need to count on metrics that help us convert those first users into customers. starts with a letter and is followed by letters, numbers, or underscores.At this stage metrics like churn rate, recovery rate, lifetime value mean pretty much nothing to us (but if you are interested in them, here is an article that does them great justice).You can reference issues in YouTrack using - (for example YT-101, Api_32-143 or gl-030) where: You can also disable GitLab internal issue tracking in this project.įor more information about the steps and consequences of disabling GitLab issues, seeĬonfigure project visibility, features, and permissions. This link takes you to the appropriate YouTrack project. Select Save changes or optionally select Test settings.Īfter you configure and enable YouTrack, a link appears on the GitLab. ![]() GitLab replaces :id with the issue number. Issue URL: The URL to view an issue in the YouTrack project.Project URL: The URL to the project in YouTrack.Select the checkbox under Enable integration.On the left sidebar, select Settings > Integrations.On the top bar, select Main menu > Projects and find your project.To enable the YouTrack integration in a project: JetBrains YouTrack is a web-based issue tracking and project Reference YouTrack issues in GitLab YouTrack.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |