Commit f3091f38e824e08b806d7b612897ed893a7ee6c1
1 parent
f672f896
Done.
Showing
3 changed files
with
34 additions
and
33 deletions
metric.tex
| @@ -48,16 +48,16 @@ app value. | @@ -48,16 +48,16 @@ app value. | ||
| 48 | 48 | ||
| 49 | Notification view and click-through rates also help put into context the | 49 | Notification view and click-through rates also help put into context the |
| 50 | energy used by apps when they are running in the background. Legitimate | 50 | energy used by apps when they are running in the background. Legitimate |
| 51 | -background energy consumption should be for one of two purposes: to prepare | ||
| 52 | -the app to deliver more value the next time it is foregrounded, as is the | ||
| 53 | -case when music players download songs and store them locally to reduce their | ||
| 54 | -runtime networking usage; or to deliver realtime notifications to the user. | ||
| 55 | -The effectiveness of background energy consumption to fill caches will be | ||
| 56 | -reflected in the apps overall energy usage, since retrieving local content is | ||
| 57 | -more energy efficient than using the network. Effectiveness of background | ||
| 58 | -consumption to deliver notifications may be reflected in the rate at which | ||
| 59 | -notifications are viewed or clicked, since a notification that is not | ||
| 60 | -consumed did not need to be retrieved. | 51 | +background energy consumption should be for one of two purposes: (1) to |
| 52 | +prepare the app to deliver more value the next time it is foregrounded, as is | ||
| 53 | +the case when music players download songs and store them locally to reduce | ||
| 54 | +their runtime networking usage; or (2) to deliver realtime notifications to | ||
| 55 | +the user. The effectiveness of background energy consumption to fill caches | ||
| 56 | +will be reflected in the apps overall energy usage, since retrieving local | ||
| 57 | +content is more energy efficient than using the network. Effectiveness of | ||
| 58 | +background consumption to deliver notifications may be reflected in the rate | ||
| 59 | +at which notifications are viewed or clicked, since a notification that is | ||
| 60 | +not consumed did not need to be retrieved. | ||
| 61 | 61 | ||
| 62 | However, in some cases apps may do an effective job at summarizing the event | 62 | However, in some cases apps may do an effective job at summarizing the event |
| 63 | within the notification itself, providing no need for the user to bring the | 63 | within the notification itself, providing no need for the user to bring the |
| @@ -79,10 +79,10 @@ messages as replies. Value is measured by the content of the messages. | @@ -79,10 +79,10 @@ messages as replies. Value is measured by the content of the messages. | ||
| 79 | Efficient chat clients exchange many messages per joule. | 79 | Efficient chat clients exchange many messages per joule. |
| 80 | 80 | ||
| 81 | \item \textbf{Video player:} the content is the video delivered to the user | 81 | \item \textbf{Video player:} the content is the video delivered to the user |
| 82 | -and efficiency is determined by the amount of network bandwidth and processing | ||
| 83 | -needed to render the video. Value is measured by the information delivered by | ||
| 84 | -the videos and efficient video players present a large amount of video | ||
| 85 | -content to their users per joule. | 82 | +and efficiency is determined by the amount of network bandwidth and |
| 83 | +processing needed to retrieve and render the video. Value is measured by the | ||
| 84 | +information delivered by the videos and efficient video players present a | ||
| 85 | +large amount of video content to their users per joule. | ||
| 86 | 86 | ||
| 87 | \item \textbf{Pedometer:} the content is the count of the number of steps | 87 | \item \textbf{Pedometer:} the content is the count of the number of steps |
| 88 | presented to the user and efficiency is determined by the accelerometer rate | 88 | presented to the user and efficiency is determined by the accelerometer rate |
results.tex
| @@ -109,7 +109,7 @@ YouTube and Candy Crush Saga both earn high marks, which is encouraging given | @@ -109,7 +109,7 @@ YouTube and Candy Crush Saga both earn high marks, which is encouraging given | ||
| 109 | that they are very different apps but also might be a result of overweighting | 109 | that they are very different apps but also might be a result of overweighting |
| 110 | screen refreshes. The Android Clock is also an unsurprising result, as it | 110 | screen refreshes. The Android Clock is also an unsurprising result, as it |
| 111 | requires almost no energy to generate a relatively-large number of screen | 111 | requires almost no energy to generate a relatively-large number of screen |
| 112 | -redraws. | 112 | +redraws in timer and stopwatch mode. |
| 113 | 113 | ||
| 114 | \subsection{Survey Results and Discussion} | 114 | \subsection{Survey Results and Discussion} |
| 115 | 115 | ||
| @@ -148,8 +148,8 @@ Overall the results are inconclusive, with the content-delivery measure not | @@ -148,8 +148,8 @@ Overall the results are inconclusive, with the content-delivery measure not | ||
| 148 | clearly outperforming the straw-man usage measure at predicting which apps | 148 | clearly outperforming the straw-man usage measure at predicting which apps |
| 149 | each user would be willing to remove to save battery life. Given the crude | 149 | each user would be willing to remove to save battery life. Given the crude |
| 150 | nature of our metric, this is not particularly surprising, and can be | 150 | nature of our metric, this is not particularly surprising, and can be |
| 151 | -interpreted as a clear sign that we need a more sophisticated value measure | ||
| 152 | -incorporating several of the potential inputs we have previously discussed. | 151 | +interpreted as a sign that we need a more sophisticated value measure |
| 152 | +incorporating more of the potential inputs we have previously discussed. | ||
| 153 | However, on one level the results are very encouraging: most users were | 153 | However, on one level the results are very encouraging: most users were |
| 154 | willing to consider removing one or more apps if that app would improve their | 154 | willing to consider removing one or more apps if that app would improve their |
| 155 | battery lifetime. Clearly users are making this decision based on some idea | 155 | battery lifetime. Clearly users are making this decision based on some idea |
usage.tex
| @@ -31,17 +31,18 @@ battery percentages to each app you use. | @@ -31,17 +31,18 @@ battery percentages to each app you use. | ||
| 31 | % | 31 | % |
| 32 | We plan to engage smartphone users in studies to explore in more detail which | 32 | We plan to engage smartphone users in studies to explore in more detail which |
| 33 | of these approaches is more effective, comparing them by comparing users' | 33 | of these approaches is more effective, comparing them by comparing users' |
| 34 | -levels of satisfaction under each scenario. In the first experiment we ask users | ||
| 35 | -to uninstall apps because often apps have a background component that keeps consuming | ||
| 36 | -energy even when not used by users any more. For our value measure we are | ||
| 37 | -hopeful that users will prove capable of assigning cardinal utilities to | ||
| 38 | -apps---as in the second experiment---since this matches most directly with | ||
| 39 | -our proposed value measure and could provide ground truth for a value measure | ||
| 40 | -computed automatically. The second experiment also engages users directly in | ||
| 41 | -the task of allocating energy, which is one way that a value measure could be | ||
| 42 | -used. However, if ordinal utilities prove more intuitive we can still compare | ||
| 43 | -the ordering generated by our measure with the ordering generated by users, | ||
| 44 | -although the values of the measure will still require justification. | 34 | +levels of satisfaction under each scenario. In the first experiment we ask |
| 35 | +users to uninstall apps because often apps have a background component that | ||
| 36 | +keeps consuming energy even when the app is no longer being used. For our | ||
| 37 | +value measure we are hopeful that users will prove capable of assigning | ||
| 38 | +cardinal utilities to apps---as in the second experiment---since this matches | ||
| 39 | +most directly with our proposed value measure and could provide ground truth | ||
| 40 | +for a value measure computed automatically. The second experiment also | ||
| 41 | +engages users directly in the task of allocating energy, which is one way | ||
| 42 | +that a value measure could be used. However, if ordinal utilities prove more | ||
| 43 | +intuitive we can still compare the ordering generated by our measure with the | ||
| 44 | +ordering generated by users, although the values of the measure will still | ||
| 45 | +require justification. | ||
| 45 | 46 | ||
| 46 | In either case, we believe that these experiments do suggest the existence of | 47 | In either case, we believe that these experiments do suggest the existence of |
| 47 | quantifiable value for smartphone apps. We are not claiming, however, that | 48 | quantifiable value for smartphone apps. We are not claiming, however, that |
| @@ -106,12 +107,12 @@ defer work on everything else. | @@ -106,12 +107,12 @@ defer work on everything else. | ||
| 106 | 107 | ||
| 107 | A measure of app value makes it possible to produce a rigorous definition of | 108 | A measure of app value makes it possible to produce a rigorous definition of |
| 108 | the term \textit{energy virus}: an app that produces little to no value per | 109 | the term \textit{energy virus}: an app that produces little to no value per |
| 109 | -joule. The choice of threshold will require some study, as it is unlikely and | 110 | +joule. The choice of threshold will require some study, as it is probably |
| 110 | impossible to produce a single efficiency cutoff that cleanly separates | 111 | impossible to produce a single efficiency cutoff that cleanly separates |
| 111 | -malicious apps from ones that are merely poorly-written. This | ||
| 112 | -definition of energy virus can also be made on a per-user basis. This is important | ||
| 113 | -since a non-malicious but poorly-written app that continues to consume energy | ||
| 114 | -even long after the user has stopped using it---and it has stopped providing | 112 | +malicious apps from ones that are merely poorly-written. This definition of |
| 113 | +energy virus can also be made on a per-user basis. This is important since a | ||
| 114 | +non-malicious but poorly-written app that continues to consume energy even | ||
| 115 | +long after the user has stopped using it---and it has stopped providing | ||
| 115 | value---functions as an energy virus for that user, but may not for a user | 116 | value---functions as an energy virus for that user, but may not for a user |
| 116 | that interacts with it more frequently. | 117 | that interacts with it more frequently. |
| 117 | 118 |