maybe We Should Enable More Uncertain Mobile App Programming

Proceedings of the 16th Workshop on Hot Topics in Mobile Computing Systems and Applications (HotMobile'15). CORE 2014: C. Acceptance rate: 28%. 2/12/2015, Santa Fe, NM.


One of the reasons programming mobile systems is so hard is the wide variety of environments a typical app encounters at runtime. As a result, in many cases only post-deployment user testing can determine the right algorithm to use, the rate at which something should happen, or when an app should attempt to conserve energy. Programmers should not be forced to make these choices at development time. Unfortunately, languages leave no way for programmers to express and structure uncertainty about runtime conditions, forcing them to adopt ineffective or fragile ad-hoc solutions.

We introduce a new approach based on structured uncertainty through a new language construct: the maybe statement. maybe statements allow programmers to defer choices about app behavior that cannot be made at development time, while providing enough structure to allow a system to later adaptively choose from multiple alternatives. Eliminating the uncertainty introduced by maybe statements can be done in a large variety of ways: through simulation, split testing, user configuration, temporal adaptation, or machine learning techniques, depending on the type of adaptation appropriate for each situation. Our paper motivates the maybe statement, presents its syntax, and describes a complete system for testing and choosing from maybe alternatives.


Built by the metalsmith-blue Metalsmith pipeline.
Created 2/11/2016
Updated 2/28/2019
Commit 4a99ff2 // History // View
Built 2/11/2015 @ 19:00 EDT