The explosive growth of the mobile application market in recent years has led to a large concomitant mobile software industry whose components are, in many cases, startups and small-size software providers. The success of these applications and the firms behind them depends on a subtle balance between different dimensions mainly affected by their architectural design, such as user satisfaction, resource consumption, operating costs, and timing. The present communication describes a framework with a specific set of practices for identifying the boundaries of different architectural designs —in this paper we apply it to estimate both the smartphone’s resource consumption and the operating costs in the cloud— and thus help in the architectural decision-making process. This will enable mobile software developers to predict at early stages which architectural design best suits their business model in accordance with the number of users and the expected use of the application and even provide an advance alert of when architectural choices will need to be reviewed, obviating the need for costly architectural re-design in further phases.