Studying User-Developer Interactions Through the Updating and Reviewing Mechanisms of the Google Play Store
| dc.contributor.author | Hassan, Safwat | en |
| dc.contributor.department | Computing | en |
| dc.contributor.supervisor | Hassan, Ahmed E. | en |
| dc.date.accessioned | 2018-10-01T20:35:07Z | |
| dc.date.available | 2018-10-01T20:35:07Z | |
| dc.degree.grantor | Queen's University at Kingston | en |
| dc.description.abstract | Mobile app stores (such as the Apple App Store and the Google Play Store) provide a unique updating mechanism that helps app developers to distribute their updates efficiently. In addition, after downloading a new update, users are able to review the latest update so other users could benefit from the posted reviews. Such unique reviewing and updating mechanisms enable users and developers to interact with each other through the store. In this thesis, we study user-developer interactions through the updating and reviewing mechanisms of app stores. Our studies can help store owners to acquire a global view about user-developer interactions. Such a global view about user-developer interactions can help store owners to improve the quality of the offered apps in their stores. For example, store owners can leverage our findings to identify the common release mistakes that are made by app developers and improve the app updating mechanism to prevent developers from making such mistakes in their updates. In particular, we study the user-developer interactions along three perspectives: (1) study the common developer mistakes that lead to emergency updates, (2) study how the reviewing mechanism can help spot good and bad updates, and (3) study the dialogue between users and developers to help design next-generation app reviewing mechanisms. In this thesis, we identify eight patterns of emergency updates in two categories "Updates due to deployment issues" and "Updates due to source code changes". Our studies show that it can be worthwhile for app owners to respond to reviews, as responding may lead to an increase in the given rating. In addition, we identify four patterns of developer responses. Our work demonstrates the necessity of an update-level analysis of reviews to capture the impressions of an app's user-base about a particular update. An app-level analysis is not sufficient to capture these transient impressions. | en |
| dc.description.degree | PhD | en |
| dc.identifier.uri | http://hdl.handle.net/1974/24927 | |
| dc.language.iso | eng | en |
| dc.relation.ispartofseries | Canadian theses | en |
| dc.rights | Attribution 3.0 United States | en |
| dc.rights.uri | http://creativecommons.org/licenses/by/3.0/us/ | |
| dc.subject | Android mobile apps | en |
| dc.subject | Google Play Store | en |
| dc.subject | Mobile app reviews | en |
| dc.subject | Updating Mechanism | en |
| dc.subject | Reviewing Mechanism | en |
| dc.subject | User-Developer Interactions | en |
| dc.subject | Emergency updates | en |
| dc.subject | Bad updates | en |
| dc.subject | User-developer dialogue | en |
| dc.subject | Mixed-effect model | en |
| dc.subject | Developer response | en |
| dc.subject | Developer reply | en |
| dc.title | Studying User-Developer Interactions Through the Updating and Reviewing Mechanisms of the Google Play Store | en |
| dc.type | thesis | en |