2. Mobile App Dev with Atlassian
How Team Productivity Drives Product Quality
Josh Devenny and Tarun Nimmagadda
JIRA Product Manager, Atlassian and Chief Operating Officer, Mutual Mobile
18. Check in code Build the app
2.0
Test the app
Distribute the app
19. Check in code Build the app
2.0
Test the app
User has feedback Distribute the app
20. Check in code Build the app
2.0
Test the app
User has feedback Distribute the app
21. I wish it was easy to give feedback to
@Facebook. The#Facebook iPad app
SUCKS. It is sooo slow & glitchy. I end
up using the web.
Angry Social Media User
109. Watch a hi-def video of the
I entire user session along III
with touch events
II
IV
110. Watch a hi-def video of the
I entire user session along III
with touch events
Jump to any “screen” or
II view in the app, by clicking
on the timeline below. IV
111. Watch a hi-def video of the Jump to any “screen” or
I entire user session along III view in the app, by clicking
with touch events on the timeline below.
Jump to any “screen” or
II view in the app, by clicking
on the timeline below. IV
112. Watch a hi-def video of the Jump to any “screen” or
I entire user session along III view in the app, by clicking
with touch events on the timeline below.
Jump to any “screen” or
II view in the app, by clicking See how long every tap,
on the timeline below. IV pinch or press lasted on
the timeline.
119. 1. Listening to your mobile users is critical
2. Incorporating feedback into an efficient
development cycle
120. 1. Listening to your mobile users is critical
2. Incorporating feedback into an efficient
development cycle
3. How to use Atlassian and Mutual Mobile
tools for Mobile Development
121. “Build quality mobile apps by increasing your
productivity with @Atlassian and @MutualMobile
tools.”
#summit12
Hi there! My name is Josh Devenny and as Ken just mentioned, I’m one of the JIRA product managers. Today I’ll be talking to you about how you can increase the quality of your mobile app by increasing the productivity of your team.\n
To start off, I’d like to ask you a quick question - can I have a show of hands of how many of you are actively developing mobile applications at your company?\n\nAnd how many people are planning to build a mobile app in the next 12 months?\n
I will be speaking to you about two central ideas.\n\nFirstly, the importance of feedback from your end users in the app development process, and how this can help you build relationships with your users. \n\nSecondly, taking this feedback that you have received, and ensuring that it makes it’s way through the development process as quickly and as efficiently as possible. Atlassian tools, as well as tools from HockeyApp and Mutual Mobile, give you the ability to rapidly iterate on this feedback will help you get more of those 5-star ratings.\n\nIntegrating feedback from your users into your mobile development process is crucial to creating quality mobile apps.\n\nFinally, Tarun will tell you how Mutual Mobile builds over 50 mobile apps simultaneously using a combination of Atlassian, HockeyApp and their own tools\n
I will be speaking to you about two central ideas.\n\nFirstly, the importance of feedback from your end users in the app development process, and how this can help you build relationships with your users. \n\nSecondly, taking this feedback that you have received, and ensuring that it makes it’s way through the development process as quickly and as efficiently as possible. Atlassian tools, as well as tools from HockeyApp and Mutual Mobile, give you the ability to rapidly iterate on this feedback will help you get more of those 5-star ratings.\n\nIntegrating feedback from your users into your mobile development process is crucial to creating quality mobile apps.\n\nFinally, Tarun will tell you how Mutual Mobile builds over 50 mobile apps simultaneously using a combination of Atlassian, HockeyApp and their own tools\n
I will be speaking to you about two central ideas.\n\nFirstly, the importance of feedback from your end users in the app development process, and how this can help you build relationships with your users. \n\nSecondly, taking this feedback that you have received, and ensuring that it makes it’s way through the development process as quickly and as efficiently as possible. Atlassian tools, as well as tools from HockeyApp and Mutual Mobile, give you the ability to rapidly iterate on this feedback will help you get more of those 5-star ratings.\n\nIntegrating feedback from your users into your mobile development process is crucial to creating quality mobile apps.\n\nFinally, Tarun will tell you how Mutual Mobile builds over 50 mobile apps simultaneously using a combination of Atlassian, HockeyApp and their own tools\n
I will be speaking to you about two central ideas.\n\nFirstly, the importance of feedback from your end users in the app development process, and how this can help you build relationships with your users. \n\nSecondly, taking this feedback that you have received, and ensuring that it makes it’s way through the development process as quickly and as efficiently as possible. Atlassian tools, as well as tools from HockeyApp and Mutual Mobile, give you the ability to rapidly iterate on this feedback will help you get more of those 5-star ratings.\n\nIntegrating feedback from your users into your mobile development process is crucial to creating quality mobile apps.\n\nFinally, Tarun will tell you how Mutual Mobile builds over 50 mobile apps simultaneously using a combination of Atlassian, HockeyApp and their own tools\n
I will be speaking to you about two central ideas.\n\nFirstly, the importance of feedback from your end users in the app development process, and how this can help you build relationships with your users. \n\nSecondly, taking this feedback that you have received, and ensuring that it makes it’s way through the development process as quickly and as efficiently as possible. Atlassian tools, as well as tools from HockeyApp and Mutual Mobile, give you the ability to rapidly iterate on this feedback will help you get more of those 5-star ratings.\n\nIntegrating feedback from your users into your mobile development process is crucial to creating quality mobile apps.\n\nFinally, Tarun will tell you how Mutual Mobile builds over 50 mobile apps simultaneously using a combination of Atlassian, HockeyApp and their own tools\n
I will be speaking to you about two central ideas.\n\nFirstly, the importance of feedback from your end users in the app development process, and how this can help you build relationships with your users. \n\nSecondly, taking this feedback that you have received, and ensuring that it makes it’s way through the development process as quickly and as efficiently as possible. Atlassian tools, as well as tools from HockeyApp and Mutual Mobile, give you the ability to rapidly iterate on this feedback will help you get more of those 5-star ratings.\n\nIntegrating feedback from your users into your mobile development process is crucial to creating quality mobile apps.\n\nFinally, Tarun will tell you how Mutual Mobile builds over 50 mobile apps simultaneously using a combination of Atlassian, HockeyApp and their own tools\n
Let’s look at a chart of how the level of user retention drops if your users are frustrated by problems with your application.\n\nIn the 90’s, the land of custom apps, people had massive switching costs and were stuck with your product most of the time. As they were able to move off your product, they would, but it would be a very slow process over time.\n\nThe naughties (For those of you in the US, that means the 2000's) came around and Web 2.0 hit the shelves ;). Switching costs dropped dramatically, which meant that user retention dropped much faster over a much shorter period of time. Feedback from your users began to become rather important to your development cycle.\n\nNow - Apple has redefined the way we download, buy and use mobile applications. Instead of having an app that does 10 things, you download an app that does one; and what do you do if one frustrates you? You make it shake in fear ;) and then delete it. There are so many other options out there, users switching costs are at rock bottom. IF YOUR MOBILE APP DOESN’T PLEASE YOUR USERS, THEY’RE GOING TO SWITCH TO A DIFFERENT APP!\n\nYou need to construct a channel of communication with your users and listen to their feedback. You want to keep them happy so that they continue using your app!\n
Let’s look at a chart of how the level of user retention drops if your users are frustrated by problems with your application.\n\nIn the 90’s, the land of custom apps, people had massive switching costs and were stuck with your product most of the time. As they were able to move off your product, they would, but it would be a very slow process over time.\n\nThe naughties (For those of you in the US, that means the 2000's) came around and Web 2.0 hit the shelves ;). Switching costs dropped dramatically, which meant that user retention dropped much faster over a much shorter period of time. Feedback from your users began to become rather important to your development cycle.\n\nNow - Apple has redefined the way we download, buy and use mobile applications. Instead of having an app that does 10 things, you download an app that does one; and what do you do if one frustrates you? You make it shake in fear ;) and then delete it. There are so many other options out there, users switching costs are at rock bottom. IF YOUR MOBILE APP DOESN’T PLEASE YOUR USERS, THEY’RE GOING TO SWITCH TO A DIFFERENT APP!\n\nYou need to construct a channel of communication with your users and listen to their feedback. You want to keep them happy so that they continue using your app!\n
Let’s look at a chart of how the level of user retention drops if your users are frustrated by problems with your application.\n\nIn the 90’s, the land of custom apps, people had massive switching costs and were stuck with your product most of the time. As they were able to move off your product, they would, but it would be a very slow process over time.\n\nThe naughties (For those of you in the US, that means the 2000's) came around and Web 2.0 hit the shelves ;). Switching costs dropped dramatically, which meant that user retention dropped much faster over a much shorter period of time. Feedback from your users began to become rather important to your development cycle.\n\nNow - Apple has redefined the way we download, buy and use mobile applications. Instead of having an app that does 10 things, you download an app that does one; and what do you do if one frustrates you? You make it shake in fear ;) and then delete it. There are so many other options out there, users switching costs are at rock bottom. IF YOUR MOBILE APP DOESN’T PLEASE YOUR USERS, THEY’RE GOING TO SWITCH TO A DIFFERENT APP!\n\nYou need to construct a channel of communication with your users and listen to their feedback. You want to keep them happy so that they continue using your app!\n
Let’s look at a chart of how the level of user retention drops if your users are frustrated by problems with your application.\n\nIn the 90’s, the land of custom apps, people had massive switching costs and were stuck with your product most of the time. As they were able to move off your product, they would, but it would be a very slow process over time.\n\nThe naughties (For those of you in the US, that means the 2000's) came around and Web 2.0 hit the shelves ;). Switching costs dropped dramatically, which meant that user retention dropped much faster over a much shorter period of time. Feedback from your users began to become rather important to your development cycle.\n\nNow - Apple has redefined the way we download, buy and use mobile applications. Instead of having an app that does 10 things, you download an app that does one; and what do you do if one frustrates you? You make it shake in fear ;) and then delete it. There are so many other options out there, users switching costs are at rock bottom. IF YOUR MOBILE APP DOESN’T PLEASE YOUR USERS, THEY’RE GOING TO SWITCH TO A DIFFERENT APP!\n\nYou need to construct a channel of communication with your users and listen to their feedback. You want to keep them happy so that they continue using your app!\n
Let’s look at a chart of how the level of user retention drops if your users are frustrated by problems with your application.\n\nIn the 90’s, the land of custom apps, people had massive switching costs and were stuck with your product most of the time. As they were able to move off your product, they would, but it would be a very slow process over time.\n\nThe naughties (For those of you in the US, that means the 2000's) came around and Web 2.0 hit the shelves ;). Switching costs dropped dramatically, which meant that user retention dropped much faster over a much shorter period of time. Feedback from your users began to become rather important to your development cycle.\n\nNow - Apple has redefined the way we download, buy and use mobile applications. Instead of having an app that does 10 things, you download an app that does one; and what do you do if one frustrates you? You make it shake in fear ;) and then delete it. There are so many other options out there, users switching costs are at rock bottom. IF YOUR MOBILE APP DOESN’T PLEASE YOUR USERS, THEY’RE GOING TO SWITCH TO A DIFFERENT APP!\n\nYou need to construct a channel of communication with your users and listen to their feedback. You want to keep them happy so that they continue using your app!\n
Let’s look at a chart of how the level of user retention drops if your users are frustrated by problems with your application.\n\nIn the 90’s, the land of custom apps, people had massive switching costs and were stuck with your product most of the time. As they were able to move off your product, they would, but it would be a very slow process over time.\n\nThe naughties (For those of you in the US, that means the 2000's) came around and Web 2.0 hit the shelves ;). Switching costs dropped dramatically, which meant that user retention dropped much faster over a much shorter period of time. Feedback from your users began to become rather important to your development cycle.\n\nNow - Apple has redefined the way we download, buy and use mobile applications. Instead of having an app that does 10 things, you download an app that does one; and what do you do if one frustrates you? You make it shake in fear ;) and then delete it. There are so many other options out there, users switching costs are at rock bottom. IF YOUR MOBILE APP DOESN’T PLEASE YOUR USERS, THEY’RE GOING TO SWITCH TO A DIFFERENT APP!\n\nYou need to construct a channel of communication with your users and listen to their feedback. You want to keep them happy so that they continue using your app!\n
Let’s look at a chart of how the level of user retention drops if your users are frustrated by problems with your application.\n\nIn the 90’s, the land of custom apps, people had massive switching costs and were stuck with your product most of the time. As they were able to move off your product, they would, but it would be a very slow process over time.\n\nThe naughties (For those of you in the US, that means the 2000's) came around and Web 2.0 hit the shelves ;). Switching costs dropped dramatically, which meant that user retention dropped much faster over a much shorter period of time. Feedback from your users began to become rather important to your development cycle.\n\nNow - Apple has redefined the way we download, buy and use mobile applications. Instead of having an app that does 10 things, you download an app that does one; and what do you do if one frustrates you? You make it shake in fear ;) and then delete it. There are so many other options out there, users switching costs are at rock bottom. IF YOUR MOBILE APP DOESN’T PLEASE YOUR USERS, THEY’RE GOING TO SWITCH TO A DIFFERENT APP!\n\nYou need to construct a channel of communication with your users and listen to their feedback. You want to keep them happy so that they continue using your app!\n
Let’s look at a chart of how the level of user retention drops if your users are frustrated by problems with your application.\n\nIn the 90’s, the land of custom apps, people had massive switching costs and were stuck with your product most of the time. As they were able to move off your product, they would, but it would be a very slow process over time.\n\nThe naughties (For those of you in the US, that means the 2000's) came around and Web 2.0 hit the shelves ;). Switching costs dropped dramatically, which meant that user retention dropped much faster over a much shorter period of time. Feedback from your users began to become rather important to your development cycle.\n\nNow - Apple has redefined the way we download, buy and use mobile applications. Instead of having an app that does 10 things, you download an app that does one; and what do you do if one frustrates you? You make it shake in fear ;) and then delete it. There are so many other options out there, users switching costs are at rock bottom. IF YOUR MOBILE APP DOESN’T PLEASE YOUR USERS, THEY’RE GOING TO SWITCH TO A DIFFERENT APP!\n\nYou need to construct a channel of communication with your users and listen to their feedback. You want to keep them happy so that they continue using your app!\n
Let’s look at a chart of how the level of user retention drops if your users are frustrated by problems with your application.\n\nIn the 90’s, the land of custom apps, people had massive switching costs and were stuck with your product most of the time. As they were able to move off your product, they would, but it would be a very slow process over time.\n\nThe naughties (For those of you in the US, that means the 2000's) came around and Web 2.0 hit the shelves ;). Switching costs dropped dramatically, which meant that user retention dropped much faster over a much shorter period of time. Feedback from your users began to become rather important to your development cycle.\n\nNow - Apple has redefined the way we download, buy and use mobile applications. Instead of having an app that does 10 things, you download an app that does one; and what do you do if one frustrates you? You make it shake in fear ;) and then delete it. There are so many other options out there, users switching costs are at rock bottom. IF YOUR MOBILE APP DOESN’T PLEASE YOUR USERS, THEY’RE GOING TO SWITCH TO A DIFFERENT APP!\n\nYou need to construct a channel of communication with your users and listen to their feedback. You want to keep them happy so that they continue using your app!\n
Let’s look at a chart of how the level of user retention drops if your users are frustrated by problems with your application.\n\nIn the 90’s, the land of custom apps, people had massive switching costs and were stuck with your product most of the time. As they were able to move off your product, they would, but it would be a very slow process over time.\n\nThe naughties (For those of you in the US, that means the 2000's) came around and Web 2.0 hit the shelves ;). Switching costs dropped dramatically, which meant that user retention dropped much faster over a much shorter period of time. Feedback from your users began to become rather important to your development cycle.\n\nNow - Apple has redefined the way we download, buy and use mobile applications. Instead of having an app that does 10 things, you download an app that does one; and what do you do if one frustrates you? You make it shake in fear ;) and then delete it. There are so many other options out there, users switching costs are at rock bottom. IF YOUR MOBILE APP DOESN’T PLEASE YOUR USERS, THEY’RE GOING TO SWITCH TO A DIFFERENT APP!\n\nYou need to construct a channel of communication with your users and listen to their feedback. You want to keep them happy so that they continue using your app!\n
Let’s look at the current state of the way we do things...\n1) a developer writes the app\n2) it’s then checked into a repository\n3) it’s manually built and packaged into an app\n4) It has a little bit of end user testing (sometimes it doesn’t have any!)\n5) It’s distributed to users through an app store\n6) If the user has feedback, they get rather frustrated because they don’t know where it’s meant to go, and either a) don’t send any feedback or b) they complain about it in a number of places, including...\n
Let’s look at the current state of the way we do things...\n1) a developer writes the app\n2) it’s then checked into a repository\n3) it’s manually built and packaged into an app\n4) It has a little bit of end user testing (sometimes it doesn’t have any!)\n5) It’s distributed to users through an app store\n6) If the user has feedback, they get rather frustrated because they don’t know where it’s meant to go, and either a) don’t send any feedback or b) they complain about it in a number of places, including...\n
Let’s look at the current state of the way we do things...\n1) a developer writes the app\n2) it’s then checked into a repository\n3) it’s manually built and packaged into an app\n4) It has a little bit of end user testing (sometimes it doesn’t have any!)\n5) It’s distributed to users through an app store\n6) If the user has feedback, they get rather frustrated because they don’t know where it’s meant to go, and either a) don’t send any feedback or b) they complain about it in a number of places, including...\n
Let’s look at the current state of the way we do things...\n1) a developer writes the app\n2) it’s then checked into a repository\n3) it’s manually built and packaged into an app\n4) It has a little bit of end user testing (sometimes it doesn’t have any!)\n5) It’s distributed to users through an app store\n6) If the user has feedback, they get rather frustrated because they don’t know where it’s meant to go, and either a) don’t send any feedback or b) they complain about it in a number of places, including...\n
Let’s look at the current state of the way we do things...\n1) a developer writes the app\n2) it’s then checked into a repository\n3) it’s manually built and packaged into an app\n4) It has a little bit of end user testing (sometimes it doesn’t have any!)\n5) It’s distributed to users through an app store\n6) If the user has feedback, they get rather frustrated because they don’t know where it’s meant to go, and either a) don’t send any feedback or b) they complain about it in a number of places, including...\n
Let’s look at the current state of the way we do things...\n1) a developer writes the app\n2) it’s then checked into a repository\n3) it’s manually built and packaged into an app\n4) It has a little bit of end user testing (sometimes it doesn’t have any!)\n5) It’s distributed to users through an app store\n6) If the user has feedback, they get rather frustrated because they don’t know where it’s meant to go, and either a) don’t send any feedback or b) they complain about it in a number of places, including...\n
Let’s look at the current state of the way we do things...\n1) a developer writes the app\n2) it’s then checked into a repository\n3) it’s manually built and packaged into an app\n4) It has a little bit of end user testing (sometimes it doesn’t have any!)\n5) It’s distributed to users through an app store\n6) If the user has feedback, they get rather frustrated because they don’t know where it’s meant to go, and either a) don’t send any feedback or b) they complain about it in a number of places, including...\n
Let’s look at the current state of the way we do things...\n1) a developer writes the app\n2) it’s then checked into a repository\n3) it’s manually built and packaged into an app\n4) It has a little bit of end user testing (sometimes it doesn’t have any!)\n5) It’s distributed to users through an app store\n6) If the user has feedback, they get rather frustrated because they don’t know where it’s meant to go, and either a) don’t send any feedback or b) they complain about it in a number of places, including...\n
Let’s look at the current state of the way we do things...\n1) a developer writes the app\n2) it’s then checked into a repository\n3) it’s manually built and packaged into an app\n4) It has a little bit of end user testing (sometimes it doesn’t have any!)\n5) It’s distributed to users through an app store\n6) If the user has feedback, they get rather frustrated because they don’t know where it’s meant to go, and either a) don’t send any feedback or b) they complain about it in a number of places, including...\n
Let’s look at the current state of the way we do things...\n1) a developer writes the app\n2) it’s then checked into a repository\n3) it’s manually built and packaged into an app\n4) It has a little bit of end user testing (sometimes it doesn’t have any!)\n5) It’s distributed to users through an app store\n6) If the user has feedback, they get rather frustrated because they don’t know where it’s meant to go, and either a) don’t send any feedback or b) they complain about it in a number of places, including...\n
Let’s look at the current state of the way we do things...\n1) a developer writes the app\n2) it’s then checked into a repository\n3) it’s manually built and packaged into an app\n4) It has a little bit of end user testing (sometimes it doesn’t have any!)\n5) It’s distributed to users through an app store\n6) If the user has feedback, they get rather frustrated because they don’t know where it’s meant to go, and either a) don’t send any feedback or b) they complain about it in a number of places, including...\n
Let’s look at the current state of the way we do things...\n1) a developer writes the app\n2) it’s then checked into a repository\n3) it’s manually built and packaged into an app\n4) It has a little bit of end user testing (sometimes it doesn’t have any!)\n5) It’s distributed to users through an app store\n6) If the user has feedback, they get rather frustrated because they don’t know where it’s meant to go, and either a) don’t send any feedback or b) they complain about it in a number of places, including...\n
Let’s look at the current state of the way we do things...\n1) a developer writes the app\n2) it’s then checked into a repository\n3) it’s manually built and packaged into an app\n4) It has a little bit of end user testing (sometimes it doesn’t have any!)\n5) It’s distributed to users through an app store\n6) If the user has feedback, they get rather frustrated because they don’t know where it’s meant to go, and either a) don’t send any feedback or b) they complain about it in a number of places, including...\n
Let’s look at the current state of the way we do things...\n1) a developer writes the app\n2) it’s then checked into a repository\n3) it’s manually built and packaged into an app\n4) It has a little bit of end user testing (sometimes it doesn’t have any!)\n5) It’s distributed to users through an app store\n6) If the user has feedback, they get rather frustrated because they don’t know where it’s meant to go, and either a) don’t send any feedback or b) they complain about it in a number of places, including...\n
Let’s look at the current state of the way we do things...\n1) a developer writes the app\n2) it’s then checked into a repository\n3) it’s manually built and packaged into an app\n4) It has a little bit of end user testing (sometimes it doesn’t have any!)\n5) It’s distributed to users through an app store\n6) If the user has feedback, they get rather frustrated because they don’t know where it’s meant to go, and either a) don’t send any feedback or b) they complain about it in a number of places, including...\n
Let’s look at the current state of the way we do things...\n1) a developer writes the app\n2) it’s then checked into a repository\n3) it’s manually built and packaged into an app\n4) It has a little bit of end user testing (sometimes it doesn’t have any!)\n5) It’s distributed to users through an app store\n6) If the user has feedback, they get rather frustrated because they don’t know where it’s meant to go, and either a) don’t send any feedback or b) they complain about it in a number of places, including...\n
Let’s look at the current state of the way we do things...\n1) a developer writes the app\n2) it’s then checked into a repository\n3) it’s manually built and packaged into an app\n4) It has a little bit of end user testing (sometimes it doesn’t have any!)\n5) It’s distributed to users through an app store\n6) If the user has feedback, they get rather frustrated because they don’t know where it’s meant to go, and either a) don’t send any feedback or b) they complain about it in a number of places, including...\n
Let’s look at the current state of the way we do things...\n1) a developer writes the app\n2) it’s then checked into a repository\n3) it’s manually built and packaged into an app\n4) It has a little bit of end user testing (sometimes it doesn’t have any!)\n5) It’s distributed to users through an app store\n6) If the user has feedback, they get rather frustrated because they don’t know where it’s meant to go, and either a) don’t send any feedback or b) they complain about it in a number of places, including...\n
Let’s look at the current state of the way we do things...\n1) a developer writes the app\n2) it’s then checked into a repository\n3) it’s manually built and packaged into an app\n4) It has a little bit of end user testing (sometimes it doesn’t have any!)\n5) It’s distributed to users through an app store\n6) If the user has feedback, they get rather frustrated because they don’t know where it’s meant to go, and either a) don’t send any feedback or b) they complain about it in a number of places, including...\n
Twitter - and, depending on how influential the person is, it might not turn out so well for your app. The other thing is that Tweets don’t tell you anything about the problem - especially this one!\n\nNo matter how many engineers Facebook has hired, they're still dealing with bad situations like this one. That’s just how tough this problem is. If I'm a Facebook dev, what am I supposed to do with this tweet except for just feeling bad???\n\n
Or it could end up on someone’s blog, which might have 10 readers.. or 10,000 if you’re unlucky.\n\nhttp://www.cultofmac.com/167201/these-are-the-technical-reasons-why-facebooks-ios-app-is-so-terrible/\n
The number one place where you don’t want feedback ending up is here. The dreaded one star review is a horrible feeling. Get enough of them and you’ll end up in 1 star hell! As soon as you’re in 1 star hell, getting people to try it out is quite hard - \n\nHow often do YOU download apps with 1 star ratings?\n
The number one place where you don’t want feedback ending up is here. The dreaded one star review is a horrible feeling. Get enough of them and you’ll end up in 1 star hell! As soon as you’re in 1 star hell, getting people to try it out is quite hard - \n\nHow often do YOU download apps with 1 star ratings?\n
Best case scenario - it ends up with the developer. Problem is, you have no way of letting the user know that you’ve fixed the bug and that they need to update their app, or anyway to ask the user further questions about the problem they’re having.\n
Back to our cycle.. We want to turn this angry user into a happy user. The only way we can do this is by listening to what they have to say, and trying to see if we can help with their problems.\nEssentially, we want to turn this, into this....\n\n
Back to our cycle.. We want to turn this angry user into a happy user. The only way we can do this is by listening to what they have to say, and trying to see if we can help with their problems.\nEssentially, we want to turn this, into this....\n\n
Back to our cycle.. We want to turn this angry user into a happy user. The only way we can do this is by listening to what they have to say, and trying to see if we can help with their problems.\nEssentially, we want to turn this, into this....\n\n
Back to our cycle.. We want to turn this angry user into a happy user. The only way we can do this is by listening to what they have to say, and trying to see if we can help with their problems.\nEssentially, we want to turn this, into this....\n\n
Back to our cycle.. We want to turn this angry user into a happy user. The only way we can do this is by listening to what they have to say, and trying to see if we can help with their problems.\nEssentially, we want to turn this, into this....\n\n
Reducing the number of places where feedback ends up - we want it all to end up with the developer. As your users learn that their feedback is being listened to, and actioned upon through your app updates, they’ll turn into really happy users.\n\nIf you’re lucky enough, you’re hard work will pay off and your happy users will begin spreading their happiness around.. To places like.. Twitter.. Or blogs.. or the app store! ;)\n\nHAVE A DRINK OF WATER\n
Reducing the number of places where feedback ends up - we want it all to end up with the developer. As your users learn that their feedback is being listened to, and actioned upon through your app updates, they’ll turn into really happy users.\n\nIf you’re lucky enough, you’re hard work will pay off and your happy users will begin spreading their happiness around.. To places like.. Twitter.. Or blogs.. or the app store! ;)\n\nHAVE A DRINK OF WATER\n
Reducing the number of places where feedback ends up - we want it all to end up with the developer. As your users learn that their feedback is being listened to, and actioned upon through your app updates, they’ll turn into really happy users.\n\nIf you’re lucky enough, you’re hard work will pay off and your happy users will begin spreading their happiness around.. To places like.. Twitter.. Or blogs.. or the app store! ;)\n\nHAVE A DRINK OF WATER\n
Reducing the number of places where feedback ends up - we want it all to end up with the developer. As your users learn that their feedback is being listened to, and actioned upon through your app updates, they’ll turn into really happy users.\n\nIf you’re lucky enough, you’re hard work will pay off and your happy users will begin spreading their happiness around.. To places like.. Twitter.. Or blogs.. or the app store! ;)\n\nHAVE A DRINK OF WATER\n
Reducing the number of places where feedback ends up - we want it all to end up with the developer. As your users learn that their feedback is being listened to, and actioned upon through your app updates, they’ll turn into really happy users.\n\nIf you’re lucky enough, you’re hard work will pay off and your happy users will begin spreading their happiness around.. To places like.. Twitter.. Or blogs.. or the app store! ;)\n\nHAVE A DRINK OF WATER\n
Reducing the number of places where feedback ends up - we want it all to end up with the developer. As your users learn that their feedback is being listened to, and actioned upon through your app updates, they’ll turn into really happy users.\n\nIf you’re lucky enough, you’re hard work will pay off and your happy users will begin spreading their happiness around.. To places like.. Twitter.. Or blogs.. or the app store! ;)\n\nHAVE A DRINK OF WATER\n
Reducing the number of places where feedback ends up - we want it all to end up with the developer. As your users learn that their feedback is being listened to, and actioned upon through your app updates, they’ll turn into really happy users.\n\nIf you’re lucky enough, you’re hard work will pay off and your happy users will begin spreading their happiness around.. To places like.. Twitter.. Or blogs.. or the app store! ;)\n\nHAVE A DRINK OF WATER\n
Reducing the number of places where feedback ends up - we want it all to end up with the developer. As your users learn that their feedback is being listened to, and actioned upon through your app updates, they’ll turn into really happy users.\n\nIf you’re lucky enough, you’re hard work will pay off and your happy users will begin spreading their happiness around.. To places like.. Twitter.. Or blogs.. or the app store! ;)\n\nHAVE A DRINK OF WATER\n
Reducing the number of places where feedback ends up - we want it all to end up with the developer. As your users learn that their feedback is being listened to, and actioned upon through your app updates, they’ll turn into really happy users.\n\nIf you’re lucky enough, you’re hard work will pay off and your happy users will begin spreading their happiness around.. To places like.. Twitter.. Or blogs.. or the app store! ;)\n\nHAVE A DRINK OF WATER\n
Reducing the number of places where feedback ends up - we want it all to end up with the developer. As your users learn that their feedback is being listened to, and actioned upon through your app updates, they’ll turn into really happy users.\n\nIf you’re lucky enough, you’re hard work will pay off and your happy users will begin spreading their happiness around.. To places like.. Twitter.. Or blogs.. or the app store! ;)\n\nHAVE A DRINK OF WATER\n
Reducing the number of places where feedback ends up - we want it all to end up with the developer. As your users learn that their feedback is being listened to, and actioned upon through your app updates, they’ll turn into really happy users.\n\nIf you’re lucky enough, you’re hard work will pay off and your happy users will begin spreading their happiness around.. To places like.. Twitter.. Or blogs.. or the app store! ;)\n\nHAVE A DRINK OF WATER\n
So how do we get this feedback, and avoid 1-star hell? How do we turn our apps into superstars, and reach five-star heaven?\n\n\n
JIRA is a great place to track, connect and manage your issues. \n\nYou want to get feedback directly from your app. \n\nEach piece of feedback is essentially an issue, so that’s why we built JIRA Mobile Connect. It sits between your JIRA instance and your phone and helps you capture that feedback that you need, directly from your users.\n
JIRA is a great place to track, connect and manage your issues. \n\nYou want to get feedback directly from your app. \n\nEach piece of feedback is essentially an issue, so that’s why we built JIRA Mobile Connect. It sits between your JIRA instance and your phone and helps you capture that feedback that you need, directly from your users.\n
It’s really easy to get started with JMC and collect feedback from your users:\n1. Install the JIRA Mobile Connect plugin in JIRA\n2. Embed the JMC library in your iOS OR Android app - ONLY 3 LINES of Code!!\n3. Submit to the app store\n4. Get feedback from users directly in JIRA!\n\nFeedback is raised directly in JIRA... So what does it look like for your users?\n\n\n
It’s really easy to get started with JMC and collect feedback from your users:\n1. Install the JIRA Mobile Connect plugin in JIRA\n2. Embed the JMC library in your iOS OR Android app - ONLY 3 LINES of Code!!\n3. Submit to the app store\n4. Get feedback from users directly in JIRA!\n\nFeedback is raised directly in JIRA... So what does it look like for your users?\n\n\n
The action to create feedback can be tied to pretty much any object in the interface. Here’s an example of an app called Trendslide, which is currently using JMC on their ‘Info’ page.\n\nAnother example is in an app called JIRA Real Life. The create feedback action is tied to a button with an image of a megaphone on it.\n\nOnce you click the button, this is what you see...\n\n
The action to create feedback can be tied to pretty much any object in the interface. Here’s an example of an app called Trendslide, which is currently using JMC on their ‘Info’ page.\n\nAnother example is in an app called JIRA Real Life. The create feedback action is tied to a button with an image of a megaphone on it.\n\nOnce you click the button, this is what you see...\n\n
The action to create feedback can be tied to pretty much any object in the interface. Here’s an example of an app called Trendslide, which is currently using JMC on their ‘Info’ page.\n\nAnother example is in an app called JIRA Real Life. The create feedback action is tied to a button with an image of a megaphone on it.\n\nOnce you click the button, this is what you see...\n\n
The action to create feedback can be tied to pretty much any object in the interface. Here’s an example of an app called Trendslide, which is currently using JMC on their ‘Info’ page.\n\nAnother example is in an app called JIRA Real Life. The create feedback action is tied to a button with an image of a megaphone on it.\n\nOnce you click the button, this is what you see...\n\n
A screen where users of your app can enter feedback in a number of forms, including:\n* Describe the problem with a text summary\n* Add screenshots AND annotate them\n* Record audio snippets of the problem they’re having\n\nJMC also gives you the ability capture so much more information, including:\n* Track your users location\n* Populate custom fields in your JIRA instance with any data you like\n* Attach any custom data in a text file.\n
A screen where users of your app can enter feedback in a number of forms, including:\n* Describe the problem with a text summary\n* Add screenshots AND annotate them\n* Record audio snippets of the problem they’re having\n\nJMC also gives you the ability capture so much more information, including:\n* Track your users location\n* Populate custom fields in your JIRA instance with any data you like\n* Attach any custom data in a text file.\n
A screen where users of your app can enter feedback in a number of forms, including:\n* Describe the problem with a text summary\n* Add screenshots AND annotate them\n* Record audio snippets of the problem they’re having\n\nJMC also gives you the ability capture so much more information, including:\n* Track your users location\n* Populate custom fields in your JIRA instance with any data you like\n* Attach any custom data in a text file.\n
A screen where users of your app can enter feedback in a number of forms, including:\n* Describe the problem with a text summary\n* Add screenshots AND annotate them\n* Record audio snippets of the problem they’re having\n\nJMC also gives you the ability capture so much more information, including:\n* Track your users location\n* Populate custom fields in your JIRA instance with any data you like\n* Attach any custom data in a text file.\n
A screen where users of your app can enter feedback in a number of forms, including:\n* Describe the problem with a text summary\n* Add screenshots AND annotate them\n* Record audio snippets of the problem they’re having\n\nJMC also gives you the ability capture so much more information, including:\n* Track your users location\n* Populate custom fields in your JIRA instance with any data you like\n* Attach any custom data in a text file.\n
A screen where users of your app can enter feedback in a number of forms, including:\n* Describe the problem with a text summary\n* Add screenshots AND annotate them\n* Record audio snippets of the problem they’re having\n\nJMC also gives you the ability capture so much more information, including:\n* Track your users location\n* Populate custom fields in your JIRA instance with any data you like\n* Attach any custom data in a text file.\n
A screen where users of your app can enter feedback in a number of forms, including:\n* Describe the problem with a text summary\n* Add screenshots AND annotate them\n* Record audio snippets of the problem they’re having\n\nJMC also gives you the ability capture so much more information, including:\n* Track your users location\n* Populate custom fields in your JIRA instance with any data you like\n* Attach any custom data in a text file.\n
A screen where users of your app can enter feedback in a number of forms, including:\n* Describe the problem with a text summary\n* Add screenshots AND annotate them\n* Record audio snippets of the problem they’re having\n\nJMC also gives you the ability capture so much more information, including:\n* Track your users location\n* Populate custom fields in your JIRA instance with any data you like\n* Attach any custom data in a text file.\n
Here’s what it looks like on the JIRA (Developer’s) side of things. All of the info that was in the feedback is neatly placed in JIRA, including:\n* Track the app version where people are experiencing the most issues; tell them to upgrade if they’re on an old version! \n* OS Version - know when older versions of your app are causing your users trouble\n* Language - you might not be supporting the language that is causing a specific problem.\n* Map of the location - the user can opt in to send their location data. If they do, you can identify where problems occur.. Maybe there’s a notorious blackspot in a specific location\n* As well as all of the attachments that were included in the feedback to delve deeper into complex issues.\n
Here’s what it looks like on the JIRA (Developer’s) side of things. All of the info that was in the feedback is neatly placed in JIRA, including:\n* Track the app version where people are experiencing the most issues; tell them to upgrade if they’re on an old version! \n* OS Version - know when older versions of your app are causing your users trouble\n* Language - you might not be supporting the language that is causing a specific problem.\n* Map of the location - the user can opt in to send their location data. If they do, you can identify where problems occur.. Maybe there’s a notorious blackspot in a specific location\n* As well as all of the attachments that were included in the feedback to delve deeper into complex issues.\n
Here’s what it looks like on the JIRA (Developer’s) side of things. All of the info that was in the feedback is neatly placed in JIRA, including:\n* Track the app version where people are experiencing the most issues; tell them to upgrade if they’re on an old version! \n* OS Version - know when older versions of your app are causing your users trouble\n* Language - you might not be supporting the language that is causing a specific problem.\n* Map of the location - the user can opt in to send their location data. If they do, you can identify where problems occur.. Maybe there’s a notorious blackspot in a specific location\n* As well as all of the attachments that were included in the feedback to delve deeper into complex issues.\n
Here’s what it looks like on the JIRA (Developer’s) side of things. All of the info that was in the feedback is neatly placed in JIRA, including:\n* Track the app version where people are experiencing the most issues; tell them to upgrade if they’re on an old version! \n* OS Version - know when older versions of your app are causing your users trouble\n* Language - you might not be supporting the language that is causing a specific problem.\n* Map of the location - the user can opt in to send their location data. If they do, you can identify where problems occur.. Maybe there’s a notorious blackspot in a specific location\n* As well as all of the attachments that were included in the feedback to delve deeper into complex issues.\n
Here’s what it looks like on the JIRA (Developer’s) side of things. All of the info that was in the feedback is neatly placed in JIRA, including:\n* Track the app version where people are experiencing the most issues; tell them to upgrade if they’re on an old version! \n* OS Version - know when older versions of your app are causing your users trouble\n* Language - you might not be supporting the language that is causing a specific problem.\n* Map of the location - the user can opt in to send their location data. If they do, you can identify where problems occur.. Maybe there’s a notorious blackspot in a specific location\n* As well as all of the attachments that were included in the feedback to delve deeper into complex issues.\n
Here’s what it looks like on the JIRA (Developer’s) side of things. All of the info that was in the feedback is neatly placed in JIRA, including:\n* Track the app version where people are experiencing the most issues; tell them to upgrade if they’re on an old version! \n* OS Version - know when older versions of your app are causing your users trouble\n* Language - you might not be supporting the language that is causing a specific problem.\n* Map of the location - the user can opt in to send their location data. If they do, you can identify where problems occur.. Maybe there’s a notorious blackspot in a specific location\n* As well as all of the attachments that were included in the feedback to delve deeper into complex issues.\n
Here’s what it looks like on the JIRA (Developer’s) side of things. All of the info that was in the feedback is neatly placed in JIRA, including:\n* Track the app version where people are experiencing the most issues; tell them to upgrade if they’re on an old version! \n* OS Version - know when older versions of your app are causing your users trouble\n* Language - you might not be supporting the language that is causing a specific problem.\n* Map of the location - the user can opt in to send their location data. If they do, you can identify where problems occur.. Maybe there’s a notorious blackspot in a specific location\n* As well as all of the attachments that were included in the feedback to delve deeper into complex issues.\n
Here’s what it looks like on the JIRA (Developer’s) side of things. All of the info that was in the feedback is neatly placed in JIRA, including:\n* Track the app version where people are experiencing the most issues; tell them to upgrade if they’re on an old version! \n* OS Version - know when older versions of your app are causing your users trouble\n* Language - you might not be supporting the language that is causing a specific problem.\n* Map of the location - the user can opt in to send their location data. If they do, you can identify where problems occur.. Maybe there’s a notorious blackspot in a specific location\n* As well as all of the attachments that were included in the feedback to delve deeper into complex issues.\n
Here’s what it looks like on the JIRA (Developer’s) side of things. All of the info that was in the feedback is neatly placed in JIRA, including:\n* Track the app version where people are experiencing the most issues; tell them to upgrade if they’re on an old version! \n* OS Version - know when older versions of your app are causing your users trouble\n* Language - you might not be supporting the language that is causing a specific problem.\n* Map of the location - the user can opt in to send their location data. If they do, you can identify where problems occur.. Maybe there’s a notorious blackspot in a specific location\n* As well as all of the attachments that were included in the feedback to delve deeper into complex issues.\n
Here’s what it looks like on the JIRA (Developer’s) side of things. All of the info that was in the feedback is neatly placed in JIRA, including:\n* Track the app version where people are experiencing the most issues; tell them to upgrade if they’re on an old version! \n* OS Version - know when older versions of your app are causing your users trouble\n* Language - you might not be supporting the language that is causing a specific problem.\n* Map of the location - the user can opt in to send their location data. If they do, you can identify where problems occur.. Maybe there’s a notorious blackspot in a specific location\n* As well as all of the attachments that were included in the feedback to delve deeper into complex issues.\n
Here’s what it looks like on the JIRA (Developer’s) side of things. All of the info that was in the feedback is neatly placed in JIRA, including:\n* Track the app version where people are experiencing the most issues; tell them to upgrade if they’re on an old version! \n* OS Version - know when older versions of your app are causing your users trouble\n* Language - you might not be supporting the language that is causing a specific problem.\n* Map of the location - the user can opt in to send their location data. If they do, you can identify where problems occur.. Maybe there’s a notorious blackspot in a specific location\n* As well as all of the attachments that were included in the feedback to delve deeper into complex issues.\n
Here’s what it looks like on the JIRA (Developer’s) side of things. All of the info that was in the feedback is neatly placed in JIRA, including:\n* Track the app version where people are experiencing the most issues; tell them to upgrade if they’re on an old version! \n* OS Version - know when older versions of your app are causing your users trouble\n* Language - you might not be supporting the language that is causing a specific problem.\n* Map of the location - the user can opt in to send their location data. If they do, you can identify where problems occur.. Maybe there’s a notorious blackspot in a specific location\n* As well as all of the attachments that were included in the feedback to delve deeper into complex issues.\n
One of the most powerful features of JMC is the ability you get to send back JIRA comments to your users! Not only can you receive feedback directly, you can tell your users when to update, or help them out with any problems that they might have.\n
One of the most powerful features of JMC is the ability you get to send back JIRA comments to your users! Not only can you receive feedback directly, you can tell your users when to update, or help them out with any problems that they might have.\n
It’s really easy to do it too! All you need to do is comment on an issue in JIRA, and it will appear on the users device next time they open your app.\nIf they choose to reply to your response, it will appear as a comment on the same issue in JIRA.\n\nNote, that by using JIRA’s powerful permissions and groups, you can restrict which comments are sent back to the user.\n\n\n
It’s really easy to do it too! All you need to do is comment on an issue in JIRA, and it will appear on the users device next time they open your app.\nIf they choose to reply to your response, it will appear as a comment on the same issue in JIRA.\n\nNote, that by using JIRA’s powerful permissions and groups, you can restrict which comments are sent back to the user.\n\n\n
It’s really easy to do it too! All you need to do is comment on an issue in JIRA, and it will appear on the users device next time they open your app.\nIf they choose to reply to your response, it will appear as a comment on the same issue in JIRA.\n\nNote, that by using JIRA’s powerful permissions and groups, you can restrict which comments are sent back to the user.\n\n\n
It’s really easy to do it too! All you need to do is comment on an issue in JIRA, and it will appear on the users device next time they open your app.\nIf they choose to reply to your response, it will appear as a comment on the same issue in JIRA.\n\nNote, that by using JIRA’s powerful permissions and groups, you can restrict which comments are sent back to the user.\n\n\n
It’s really easy to do it too! All you need to do is comment on an issue in JIRA, and it will appear on the users device next time they open your app.\nIf they choose to reply to your response, it will appear as a comment on the same issue in JIRA.\n\nNote, that by using JIRA’s powerful permissions and groups, you can restrict which comments are sent back to the user.\n\n\n
One great example of the importance of feedback, is from a company called Trendslide. They have an app that visualises all different kinds of trends, from Twitter to Google Analytics. After realising the need for feedback, they implemented JMC and are seeing around 5-6 items of feedback each week, from a user base of around 600. The most common piece of feedback that was raised through JMC was that users didn’t understand the difference between the colours in the graph. \n\n
This issue was tracked in JIRA as part of their development process, and by iterating on the feedback effectively, Trendslide were able to successfully implement a splash screen that solved the problem.\n
Speaking with Jeffrey from Trendslide about this, he said:\n“...we have significantly enhanced that experience and delivered an application that almost immediately brings value to a user.”\n\nThis is a great example of the power of feedback and how it can truly improve your mobile applications.\n\nHAVE A DRINK OF WATER\n
Ok so now we’ve sorted getting feedback in the developer’s hands - we now need to focus on the amount of time spent between point A, when the user creates the feedback, to point B, when the user updates their app and realises their issue has been fixed.\n\nThis is called the: MEAN TIME TO RESOLUTION\n
Ok so now we’ve sorted getting feedback in the developer’s hands - we now need to focus on the amount of time spent between point A, when the user creates the feedback, to point B, when the user updates their app and realises their issue has been fixed.\n\nThis is called the: MEAN TIME TO RESOLUTION\n
Ok so now we’ve sorted getting feedback in the developer’s hands - we now need to focus on the amount of time spent between point A, when the user creates the feedback, to point B, when the user updates their app and realises their issue has been fixed.\n\nThis is called the: MEAN TIME TO RESOLUTION\n
Ok so now we’ve sorted getting feedback in the developer’s hands - we now need to focus on the amount of time spent between point A, when the user creates the feedback, to point B, when the user updates their app and realises their issue has been fixed.\n\nThis is called the: MEAN TIME TO RESOLUTION\n
Ok so now we’ve sorted getting feedback in the developer’s hands - we now need to focus on the amount of time spent between point A, when the user creates the feedback, to point B, when the user updates their app and realises their issue has been fixed.\n\nThis is called the: MEAN TIME TO RESOLUTION\n
Ok so now we’ve sorted getting feedback in the developer’s hands - we now need to focus on the amount of time spent between point A, when the user creates the feedback, to point B, when the user updates their app and realises their issue has been fixed.\n\nThis is called the: MEAN TIME TO RESOLUTION\n
Ok so now we’ve sorted getting feedback in the developer’s hands - we now need to focus on the amount of time spent between point A, when the user creates the feedback, to point B, when the user updates their app and realises their issue has been fixed.\n\nThis is called the: MEAN TIME TO RESOLUTION\n
So how do we minimise the MEAN TIME TO RESOLUTION? How can we ensure that the issue is handled as quickly and efficiently as possible?\n
Here are some tools that you can employ to help you reduce the time that it takes for an issue to go through your dev cycle:\n1) Manage your code with SourceTree\n2) Host your code with Stash for Git in the Enterprise, Fisheye for SVN and Bitbucket for hosted Git and Mecurial\n3) Test, Build and Package your app with Bamboo\n4) Test your app with Replay by Mutual Mobile - stay tuned for an exciting announcement by Tarun\n5) Deploy your app and manage high scale crash reporting with HockeyApp\n
Here are some tools that you can employ to help you reduce the time that it takes for an issue to go through your dev cycle:\n1) Manage your code with SourceTree\n2) Host your code with Stash for Git in the Enterprise, Fisheye for SVN and Bitbucket for hosted Git and Mecurial\n3) Test, Build and Package your app with Bamboo\n4) Test your app with Replay by Mutual Mobile - stay tuned for an exciting announcement by Tarun\n5) Deploy your app and manage high scale crash reporting with HockeyApp\n
Here are some tools that you can employ to help you reduce the time that it takes for an issue to go through your dev cycle:\n1) Manage your code with SourceTree\n2) Host your code with Stash for Git in the Enterprise, Fisheye for SVN and Bitbucket for hosted Git and Mecurial\n3) Test, Build and Package your app with Bamboo\n4) Test your app with Replay by Mutual Mobile - stay tuned for an exciting announcement by Tarun\n5) Deploy your app and manage high scale crash reporting with HockeyApp\n
Here are some tools that you can employ to help you reduce the time that it takes for an issue to go through your dev cycle:\n1) Manage your code with SourceTree\n2) Host your code with Stash for Git in the Enterprise, Fisheye for SVN and Bitbucket for hosted Git and Mecurial\n3) Test, Build and Package your app with Bamboo\n4) Test your app with Replay by Mutual Mobile - stay tuned for an exciting announcement by Tarun\n5) Deploy your app and manage high scale crash reporting with HockeyApp\n
Here are some tools that you can employ to help you reduce the time that it takes for an issue to go through your dev cycle:\n1) Manage your code with SourceTree\n2) Host your code with Stash for Git in the Enterprise, Fisheye for SVN and Bitbucket for hosted Git and Mecurial\n3) Test, Build and Package your app with Bamboo\n4) Test your app with Replay by Mutual Mobile - stay tuned for an exciting announcement by Tarun\n5) Deploy your app and manage high scale crash reporting with HockeyApp\n
Here are some tools that you can employ to help you reduce the time that it takes for an issue to go through your dev cycle:\n1) Manage your code with SourceTree\n2) Host your code with Stash for Git in the Enterprise, Fisheye for SVN and Bitbucket for hosted Git and Mecurial\n3) Test, Build and Package your app with Bamboo\n4) Test your app with Replay by Mutual Mobile - stay tuned for an exciting announcement by Tarun\n5) Deploy your app and manage high scale crash reporting with HockeyApp\n
Here are some tools that you can employ to help you reduce the time that it takes for an issue to go through your dev cycle:\n1) Manage your code with SourceTree\n2) Host your code with Stash for Git in the Enterprise, Fisheye for SVN and Bitbucket for hosted Git and Mecurial\n3) Test, Build and Package your app with Bamboo\n4) Test your app with Replay by Mutual Mobile - stay tuned for an exciting announcement by Tarun\n5) Deploy your app and manage high scale crash reporting with HockeyApp\n
Here are some tools that you can employ to help you reduce the time that it takes for an issue to go through your dev cycle:\n1) Manage your code with SourceTree\n2) Host your code with Stash for Git in the Enterprise, Fisheye for SVN and Bitbucket for hosted Git and Mecurial\n3) Test, Build and Package your app with Bamboo\n4) Test your app with Replay by Mutual Mobile - stay tuned for an exciting announcement by Tarun\n5) Deploy your app and manage high scale crash reporting with HockeyApp\n
Automating this process means that you can spend MUCH more time developing features for your users, and listening, and responding to their feedback.\n
Automating this process means that you can spend MUCH more time developing features for your users, and listening, and responding to their feedback.\n
Automating this process means that you can spend MUCH more time developing features for your users, and listening, and responding to their feedback.\n
Automating this process means that you can spend MUCH more time developing features for your users, and listening, and responding to their feedback.\n
Automating this process means that you can spend MUCH more time developing features for your users, and listening, and responding to their feedback.\n
Automating this process means that you can spend MUCH more time developing features for your users, and listening, and responding to their feedback.\n
Automating this process means that you can spend MUCH more time developing features for your users, and listening, and responding to their feedback.\n
Automating this process means that you can spend MUCH more time developing features for your users, and listening, and responding to their feedback.\n
Automating this process means that you can spend MUCH more time developing features for your users, and listening, and responding to their feedback.\n
Automating this process means that you can spend MUCH more time developing features for your users, and listening, and responding to their feedback.\n
Automating this process means that you can spend MUCH more time developing features for your users, and listening, and responding to their feedback.\n
Automating this process means that you can spend MUCH more time developing features for your users, and listening, and responding to their feedback.\n
Automating this process means that you can spend MUCH more time developing features for your users, and listening, and responding to their feedback.\n
Automating this process means that you can spend MUCH more time developing features for your users, and listening, and responding to their feedback.\n
Automating this process means that you can spend MUCH more time developing features for your users, and listening, and responding to their feedback.\n
To do this, you can set up a Plan in Bamboo, and then create a few Jobs within that plan. Bamboo will automatically check the code out from your repository if you give it your credentials.\n\nHere’s the results that you will see after a successful build of your Plan.\nThe status of each job is listed in the log file that is attached to the build. As you can see here, my app has successfully been uploaded to HockeyApp!\n
HockeyApp is a third-party service that has been developed to manage high-scale crash reporting, as well as beta-test distribution of your app. It has a special integration with JMC, where JMC performs the feedback aspect, while HockeyApp performs crash reporting/symbolication/grouping. By using HA, you can easily increase your number of beta-testers, as well as effectively manage all crash reports in real-time. No more waiting 2 weeks to see your crash reports!\n\n\n
HockeyApp is a third-party service that has been developed to manage high-scale crash reporting, as well as beta-test distribution of your app. It has a special integration with JMC, where JMC performs the feedback aspect, while HockeyApp performs crash reporting/symbolication/grouping. By using HA, you can easily increase your number of beta-testers, as well as effectively manage all crash reports in real-time. No more waiting 2 weeks to see your crash reports!\n\n\n
HockeyApp is a third-party service that has been developed to manage high-scale crash reporting, as well as beta-test distribution of your app. It has a special integration with JMC, where JMC performs the feedback aspect, while HockeyApp performs crash reporting/symbolication/grouping. By using HA, you can easily increase your number of beta-testers, as well as effectively manage all crash reports in real-time. No more waiting 2 weeks to see your crash reports!\n\n\n
HockeyApp is a third-party service that has been developed to manage high-scale crash reporting, as well as beta-test distribution of your app. It has a special integration with JMC, where JMC performs the feedback aspect, while HockeyApp performs crash reporting/symbolication/grouping. By using HA, you can easily increase your number of beta-testers, as well as effectively manage all crash reports in real-time. No more waiting 2 weeks to see your crash reports!\n\n\n
HockeyApp is a third-party service that has been developed to manage high-scale crash reporting, as well as beta-test distribution of your app. It has a special integration with JMC, where JMC performs the feedback aspect, while HockeyApp performs crash reporting/symbolication/grouping. By using HA, you can easily increase your number of beta-testers, as well as effectively manage all crash reports in real-time. No more waiting 2 weeks to see your crash reports!\n\n\n
HockeyApp is a third-party service that has been developed to manage high-scale crash reporting, as well as beta-test distribution of your app. It has a special integration with JMC, where JMC performs the feedback aspect, while HockeyApp performs crash reporting/symbolication/grouping. By using HA, you can easily increase your number of beta-testers, as well as effectively manage all crash reports in real-time. No more waiting 2 weeks to see your crash reports!\n\n\n
HockeyApp is a third-party service that has been developed to manage high-scale crash reporting, as well as beta-test distribution of your app. It has a special integration with JMC, where JMC performs the feedback aspect, while HockeyApp performs crash reporting/symbolication/grouping. By using HA, you can easily increase your number of beta-testers, as well as effectively manage all crash reports in real-time. No more waiting 2 weeks to see your crash reports!\n\n\n
HockeyApp is a third-party service that has been developed to manage high-scale crash reporting, as well as beta-test distribution of your app. It has a special integration with JMC, where JMC performs the feedback aspect, while HockeyApp performs crash reporting/symbolication/grouping. By using HA, you can easily increase your number of beta-testers, as well as effectively manage all crash reports in real-time. No more waiting 2 weeks to see your crash reports!\n\n\n
HockeyApp is a third-party service that has been developed to manage high-scale crash reporting, as well as beta-test distribution of your app. It has a special integration with JMC, where JMC performs the feedback aspect, while HockeyApp performs crash reporting/symbolication/grouping. By using HA, you can easily increase your number of beta-testers, as well as effectively manage all crash reports in real-time. No more waiting 2 weeks to see your crash reports!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
HockeyApp is a powerhouse in crash reporting. Using the same library that JMC uses for small scale crash reporting, HockeyApp symbolicates and groups all of your app’s crash reports. If you have 1000’s of crash reports, HockeyApp will identify which ones are duplicates and group them together. You might end up with only 2 unique crash reports from a few hundred!\n\n\n
Once HA has done it’s magic, you can create issues directly in JIRA! No plugin necessary - all built on the JIRA REST API.\n
Once HA has done it’s magic, you can create issues directly in JIRA! No plugin necessary - all built on the JIRA REST API.\n
This is the HockeyApp interface. Once Bamboo has uploaded your app to HockeyApp using their API, it’s version number will appear here. Each version can have a different distribution list and every user and device can be tracked in the HA interface. You can also access crash reports and will see a range of stack traces and other useful information about each crash.\n\nYou can also see metrics on how many people have downloaded your app, and how many have installed it, as well as how long they’ve used it for.\n\nOne of the really neat features of HA is that you can add new users to the app’s provisioning file, without having to rebuild and reupload your app. This means that you can distribute your app to beta testers while on the go!\n\nHAVE A DRINK OF WATER\n
This is the HockeyApp interface. Once Bamboo has uploaded your app to HockeyApp using their API, it’s version number will appear here. Each version can have a different distribution list and every user and device can be tracked in the HA interface. You can also access crash reports and will see a range of stack traces and other useful information about each crash.\n\nYou can also see metrics on how many people have downloaded your app, and how many have installed it, as well as how long they’ve used it for.\n\nOne of the really neat features of HA is that you can add new users to the app’s provisioning file, without having to rebuild and reupload your app. This means that you can distribute your app to beta testers while on the go!\n\nHAVE A DRINK OF WATER\n
This is the HockeyApp interface. Once Bamboo has uploaded your app to HockeyApp using their API, it’s version number will appear here. Each version can have a different distribution list and every user and device can be tracked in the HA interface. You can also access crash reports and will see a range of stack traces and other useful information about each crash.\n\nYou can also see metrics on how many people have downloaded your app, and how many have installed it, as well as how long they’ve used it for.\n\nOne of the really neat features of HA is that you can add new users to the app’s provisioning file, without having to rebuild and reupload your app. This means that you can distribute your app to beta testers while on the go!\n\nHAVE A DRINK OF WATER\n
This is the HockeyApp interface. Once Bamboo has uploaded your app to HockeyApp using their API, it’s version number will appear here. Each version can have a different distribution list and every user and device can be tracked in the HA interface. You can also access crash reports and will see a range of stack traces and other useful information about each crash.\n\nYou can also see metrics on how many people have downloaded your app, and how many have installed it, as well as how long they’ve used it for.\n\nOne of the really neat features of HA is that you can add new users to the app’s provisioning file, without having to rebuild and reupload your app. This means that you can distribute your app to beta testers while on the go!\n\nHAVE A DRINK OF WATER\n
This is the HockeyApp interface. Once Bamboo has uploaded your app to HockeyApp using their API, it’s version number will appear here. Each version can have a different distribution list and every user and device can be tracked in the HA interface. You can also access crash reports and will see a range of stack traces and other useful information about each crash.\n\nYou can also see metrics on how many people have downloaded your app, and how many have installed it, as well as how long they’ve used it for.\n\nOne of the really neat features of HA is that you can add new users to the app’s provisioning file, without having to rebuild and reupload your app. This means that you can distribute your app to beta testers while on the go!\n\nHAVE A DRINK OF WATER\n
So we’ve made sure that we’re listening to users feedback in our development process and we have a process to minimise the time to resolution. We’ve talked about automated testing and building with Bamboo, distribution and crash reporting with HockeyApp, but what about beta testing? How about usability testing?\n\nTarun is now going talk about how Mutual Mobile uses Atlassian tools, alongside HockeyApp and their own tools to ensure that their development cycle is as efficient as possible. He will also talk to you about what happens from a feedback perspective before the app store (when you’re beta testing your app), or if you’re developing a mobile app for an internal customer\n
\n
We face an exaggerated problem with App Development. \n
\n
One of the key benefits of build automation through Bamboo is that you can create multiple builds with different configurations automatically with every check in. \n
One of the ways we use this capability is by generating an automated “simulator build” which we can send through a curl command to Peaceable which allows us to preview the app within the browser. For those of you who don’t know how Peaceable works, it’s a neat little technology that allows you to fully interact with an app using a simple flash viewer in the browser. So many of our customer stakeholders that help approve the app still don’t have a personal iPhone and this really helps speed approval along. \n
For explicit feedback, we use HockeyApp and Jira Mobile Connect using the integrated plugin. HockeyApp allows us to give our customers a call when the app crashes rather than waiting for them to tell us. Jira Mobile Connect allows us to have a two-way conversation with our stakeholders including when they are reviewing the app while sipping a margarita on the beach.\n\n\n
For explicit feedback, we use HockeyApp and Jira Mobile Connect using the integrated plugin. HockeyApp allows us to give our customers a call when the app crashes rather than waiting for them to tell us. Jira Mobile Connect allows us to have a two-way conversation with our stakeholders including when they are reviewing the app while sipping a margarita on the beach.\n\n\n
For explicit feedback, we use HockeyApp and Jira Mobile Connect using the integrated plugin. HockeyApp allows us to give our customers a call when the app crashes rather than waiting for them to tell us. Jira Mobile Connect allows us to have a two-way conversation with our stakeholders including when they are reviewing the app while sipping a margarita on the beach.\n\n\n
For explicit feedback, we use HockeyApp and Jira Mobile Connect using the integrated plugin. HockeyApp allows us to give our customers a call when the app crashes rather than waiting for them to tell us. Jira Mobile Connect allows us to have a two-way conversation with our stakeholders including when they are reviewing the app while sipping a margarita on the beach.\n\n\n
For explicit feedback, we use HockeyApp and Jira Mobile Connect using the integrated plugin. HockeyApp allows us to give our customers a call when the app crashes rather than waiting for them to tell us. Jira Mobile Connect allows us to have a two-way conversation with our stakeholders including when they are reviewing the app while sipping a margarita on the beach.\n\n\n
For explicit feedback, we use HockeyApp and Jira Mobile Connect using the integrated plugin. HockeyApp allows us to give our customers a call when the app crashes rather than waiting for them to tell us. Jira Mobile Connect allows us to have a two-way conversation with our stakeholders including when they are reviewing the app while sipping a margarita on the beach.\n\n\n
For explicit feedback, we use HockeyApp and Jira Mobile Connect using the integrated plugin. HockeyApp allows us to give our customers a call when the app crashes rather than waiting for them to tell us. Jira Mobile Connect allows us to have a two-way conversation with our stakeholders including when they are reviewing the app while sipping a margarita on the beach.\n\n\n
For explicit feedback, we use HockeyApp and Jira Mobile Connect using the integrated plugin. HockeyApp allows us to give our customers a call when the app crashes rather than waiting for them to tell us. Jira Mobile Connect allows us to have a two-way conversation with our stakeholders including when they are reviewing the app while sipping a margarita on the beach.\n\n\n
For explicit feedback, we use HockeyApp and Jira Mobile Connect using the integrated plugin. HockeyApp allows us to give our customers a call when the app crashes rather than waiting for them to tell us. Jira Mobile Connect allows us to have a two-way conversation with our stakeholders including when they are reviewing the app while sipping a margarita on the beach.\n\n\n
Two kinds of feedback. Spoken and unspoken. How do you really know how/why users are leaving the app, or not completing the checkout process. \n
Two kinds of feedback. Spoken and unspoken. How do you really know how/why users are leaving the app, or not completing the checkout process. \n
\n
\n
The interface is wonderfully simple - the video shows the screen and the user’s face side-by-side. Every touch is also shown on the screen and we can capture multiple fingers, so you really see a pinch or a swipe gesture. Now, some of the touches happen so quickly that it is easy to miss. And that’s where the timeline feature at the bottom comes in. Timeline shows the duration of each touch and the relative durations as well. Timeline also allows you to see the name of the screen/view that the user is currently looking at and how long they have been on that screen. Now, this is awesome because you get to skip right to the screen you are looking for just by clicking on the view. So if you are a product-manager at a retailer and you are experiencing abandonment on the shopping cart screen, you can jump right to the footage of that screen and visually see what’s happening on this screen across many different users. And we are just getting started.\n
The interface is wonderfully simple - the video shows the screen and the user’s face side-by-side. Every touch is also shown on the screen and we can capture multiple fingers, so you really see a pinch or a swipe gesture. Now, some of the touches happen so quickly that it is easy to miss. And that’s where the timeline feature at the bottom comes in. Timeline shows the duration of each touch and the relative durations as well. Timeline also allows you to see the name of the screen/view that the user is currently looking at and how long they have been on that screen. Now, this is awesome because you get to skip right to the screen you are looking for just by clicking on the view. So if you are a product-manager at a retailer and you are experiencing abandonment on the shopping cart screen, you can jump right to the footage of that screen and visually see what’s happening on this screen across many different users. And we are just getting started.\n
The interface is wonderfully simple - the video shows the screen and the user’s face side-by-side. Every touch is also shown on the screen and we can capture multiple fingers, so you really see a pinch or a swipe gesture. Now, some of the touches happen so quickly that it is easy to miss. And that’s where the timeline feature at the bottom comes in. Timeline shows the duration of each touch and the relative durations as well. Timeline also allows you to see the name of the screen/view that the user is currently looking at and how long they have been on that screen. Now, this is awesome because you get to skip right to the screen you are looking for just by clicking on the view. So if you are a product-manager at a retailer and you are experiencing abandonment on the shopping cart screen, you can jump right to the footage of that screen and visually see what’s happening on this screen across many different users. And we are just getting started.\n
The interface is wonderfully simple - the video shows the screen and the user’s face side-by-side. Every touch is also shown on the screen and we can capture multiple fingers, so you really see a pinch or a swipe gesture. Now, some of the touches happen so quickly that it is easy to miss. And that’s where the timeline feature at the bottom comes in. Timeline shows the duration of each touch and the relative durations as well. Timeline also allows you to see the name of the screen/view that the user is currently looking at and how long they have been on that screen. Now, this is awesome because you get to skip right to the screen you are looking for just by clicking on the view. So if you are a product-manager at a retailer and you are experiencing abandonment on the shopping cart screen, you can jump right to the footage of that screen and visually see what’s happening on this screen across many different users. And we are just getting started.\n
The interface is wonderfully simple - the video shows the screen and the user’s face side-by-side. Every touch is also shown on the screen and we can capture multiple fingers, so you really see a pinch or a swipe gesture. Now, some of the touches happen so quickly that it is easy to miss. And that’s where the timeline feature at the bottom comes in. Timeline shows the duration of each touch and the relative durations as well. Timeline also allows you to see the name of the screen/view that the user is currently looking at and how long they have been on that screen. Now, this is awesome because you get to skip right to the screen you are looking for just by clicking on the view. So if you are a product-manager at a retailer and you are experiencing abandonment on the shopping cart screen, you can jump right to the footage of that screen and visually see what’s happening on this screen across many different users. And we are just getting started.\n
The interface is wonderfully simple - the video shows the screen and the user’s face side-by-side. Every touch is also shown on the screen and we can capture multiple fingers, so you really see a pinch or a swipe gesture. Now, some of the touches happen so quickly that it is easy to miss. And that’s where the timeline feature at the bottom comes in. Timeline shows the duration of each touch and the relative durations as well. Timeline also allows you to see the name of the screen/view that the user is currently looking at and how long they have been on that screen. Now, this is awesome because you get to skip right to the screen you are looking for just by clicking on the view. So if you are a product-manager at a retailer and you are experiencing abandonment on the shopping cart screen, you can jump right to the footage of that screen and visually see what’s happening on this screen across many different users. And we are just getting started.\n
The interface is wonderfully simple - the video shows the screen and the user’s face side-by-side. Every touch is also shown on the screen and we can capture multiple fingers, so you really see a pinch or a swipe gesture. Now, some of the touches happen so quickly that it is easy to miss. And that’s where the timeline feature at the bottom comes in. Timeline shows the duration of each touch and the relative durations as well. Timeline also allows you to see the name of the screen/view that the user is currently looking at and how long they have been on that screen. Now, this is awesome because you get to skip right to the screen you are looking for just by clicking on the view. So if you are a product-manager at a retailer and you are experiencing abandonment on the shopping cart screen, you can jump right to the footage of that screen and visually see what’s happening on this screen across many different users. And we are just getting started.\n
The interface is wonderfully simple - the video shows the screen and the user’s face side-by-side. Every touch is also shown on the screen and we can capture multiple fingers, so you really see a pinch or a swipe gesture. Now, some of the touches happen so quickly that it is easy to miss. And that’s where the timeline feature at the bottom comes in. Timeline shows the duration of each touch and the relative durations as well. Timeline also allows you to see the name of the screen/view that the user is currently looking at and how long they have been on that screen. Now, this is awesome because you get to skip right to the screen you are looking for just by clicking on the view. So if you are a product-manager at a retailer and you are experiencing abandonment on the shopping cart screen, you can jump right to the footage of that screen and visually see what’s happening on this screen across many different users. And we are just getting started.\n
\n
User Research Labs are expensive and time-consuming. This means that most companies rarely pay for user research and the ones that do, often do it at the very end of a project leaving them with little time to improve the product before it is released. One of the biggest leap that Replay allows is that it allows you to conduct user research in a operational manner. With every new intermediate/internal build of your app, rather than once a year or once a quarter. This allows for real-continuous improvement of the product where the product, design and engineering teams get feedback in real-time. And unlike user research labs that try to create an artificial environment to replicate the real-world, Replay allows you to capture your users in their natural habitat. Whether they are buying a coffee at Starbucks, or calling a cab on the street, Replay allows us to capture the activity in context without requiring the user to carry *any* equipment.\n
We’ve all seen the famous infographics from Flurry that show the reverse-hockey stick drop-off when users abandon a mobile application months or weeks after it has been released. This is the implicit feedback that users often give us. Abandonment. And there are 10 of these instances for every poor/negative review in the AppStore. Now, unfortunately - the way most mobile analytics technologies work is that they upload the analytics data gathered in the current session, the next time the user opens the app. The trouble with this is that they are unable to get the data from the very last or most recent user session. Now, the knowledge that you get from observing the very last time the user uses your app is arguably orders magnitude more dense and meaningful than every other time that the user has used the app. Replay uses real-time encoding and streaming technology under the hood to allow you to access the footage from the very last user session, seconds after the user has left the app. And we are very very excited about this.\n
\n
Wow.. I’ve been using Replay for the past few weeks, and it’s ability to record the users touch, including multi-touches is great. Put this alongside what screens the user is looking at on a timeline, and you’ve got yourself a killer development tool!\n\nTarun and I have talked to you today about three key ideas:\n1. Firstly, listening to your users is critical in the mobile world. Switching costs are so low that you must keep your users happy, and listen to their feedback. Without this you are almost certain to lose users rapidly.\n2. Secondly, taking this feedback that you have received and incorporating it into an effective development process, that can quickly iterate and efficiently deliver solutions and updates to your users. There’s no point in getting feedback unless you can demonstrate to your users that you’re actioning their feedback\n3. Finally, Tarun talked to you about how Mutual Mobile uses a combination of Atlassian and HockeyApp tools in their mobile development process of over 50 apps simultaneoulsy. He also introduced Replay, which is a killer app to have in your dev cycle for beta and usability testing.\n
Wow.. I’ve been using Replay for the past few weeks, and it’s ability to record the users touch, including multi-touches is great. Put this alongside what screens the user is looking at on a timeline, and you’ve got yourself a killer development tool!\n\nTarun and I have talked to you today about three key ideas:\n1. Firstly, listening to your users is critical in the mobile world. Switching costs are so low that you must keep your users happy, and listen to their feedback. Without this you are almost certain to lose users rapidly.\n2. Secondly, taking this feedback that you have received and incorporating it into an effective development process, that can quickly iterate and efficiently deliver solutions and updates to your users. There’s no point in getting feedback unless you can demonstrate to your users that you’re actioning their feedback\n3. Finally, Tarun talked to you about how Mutual Mobile uses a combination of Atlassian and HockeyApp tools in their mobile development process of over 50 apps simultaneoulsy. He also introduced Replay, which is a killer app to have in your dev cycle for beta and usability testing.\n
Wow.. I’ve been using Replay for the past few weeks, and it’s ability to record the users touch, including multi-touches is great. Put this alongside what screens the user is looking at on a timeline, and you’ve got yourself a killer development tool!\n\nTarun and I have talked to you today about three key ideas:\n1. Firstly, listening to your users is critical in the mobile world. Switching costs are so low that you must keep your users happy, and listen to their feedback. Without this you are almost certain to lose users rapidly.\n2. Secondly, taking this feedback that you have received and incorporating it into an effective development process, that can quickly iterate and efficiently deliver solutions and updates to your users. There’s no point in getting feedback unless you can demonstrate to your users that you’re actioning their feedback\n3. Finally, Tarun talked to you about how Mutual Mobile uses a combination of Atlassian and HockeyApp tools in their mobile development process of over 50 apps simultaneoulsy. He also introduced Replay, which is a killer app to have in your dev cycle for beta and usability testing.\n
Wow.. I’ve been using Replay for the past few weeks, and it’s ability to record the users touch, including multi-touches is great. Put this alongside what screens the user is looking at on a timeline, and you’ve got yourself a killer development tool!\n\nTarun and I have talked to you today about three key ideas:\n1. Firstly, listening to your users is critical in the mobile world. Switching costs are so low that you must keep your users happy, and listen to their feedback. Without this you are almost certain to lose users rapidly.\n2. Secondly, taking this feedback that you have received and incorporating it into an effective development process, that can quickly iterate and efficiently deliver solutions and updates to your users. There’s no point in getting feedback unless you can demonstrate to your users that you’re actioning their feedback\n3. Finally, Tarun talked to you about how Mutual Mobile uses a combination of Atlassian and HockeyApp tools in their mobile development process of over 50 apps simultaneoulsy. He also introduced Replay, which is a killer app to have in your dev cycle for beta and usability testing.\n
Wow.. I’ve been using Replay for the past few weeks, and it’s ability to record the users touch, including multi-touches is great. Put this alongside what screens the user is looking at on a timeline, and you’ve got yourself a killer development tool!\n\nTarun and I have talked to you today about three key ideas:\n1. Firstly, listening to your users is critical in the mobile world. Switching costs are so low that you must keep your users happy, and listen to their feedback. Without this you are almost certain to lose users rapidly.\n2. Secondly, taking this feedback that you have received and incorporating it into an effective development process, that can quickly iterate and efficiently deliver solutions and updates to your users. There’s no point in getting feedback unless you can demonstrate to your users that you’re actioning their feedback\n3. Finally, Tarun talked to you about how Mutual Mobile uses a combination of Atlassian and HockeyApp tools in their mobile development process of over 50 apps simultaneoulsy. He also introduced Replay, which is a killer app to have in your dev cycle for beta and usability testing.\n
Wow.. I’ve been using Replay for the past few weeks, and it’s ability to record the users touch, including multi-touches is great. Put this alongside what screens the user is looking at on a timeline, and you’ve got yourself a killer development tool!\n\nTarun and I have talked to you today about three key ideas:\n1. Firstly, listening to your users is critical in the mobile world. Switching costs are so low that you must keep your users happy, and listen to their feedback. Without this you are almost certain to lose users rapidly.\n2. Secondly, taking this feedback that you have received and incorporating it into an effective development process, that can quickly iterate and efficiently deliver solutions and updates to your users. There’s no point in getting feedback unless you can demonstrate to your users that you’re actioning their feedback\n3. Finally, Tarun talked to you about how Mutual Mobile uses a combination of Atlassian and HockeyApp tools in their mobile development process of over 50 apps simultaneoulsy. He also introduced Replay, which is a killer app to have in your dev cycle for beta and usability testing.\n
If you’ve liked today’s talk, feel free to tweet about it!\n“Build quality mobile apps by increasing your productivity with @Atlassian and @MutualMobile tools.”\n\n\n\n
