Over the past six months we&#x27;ve been writing an Android framework with two uses.  One use is to spin apps off of the framework.  The other use for the framework would be for the ultimate goal of publishing a spreadsheet app for Android from it.<p>We just published our first app based off the framework yesterday (linked in parent post). The framework work we have done so far was put into yesterday&#x27;s app (a browsable, searchable spreadsheet-like front end to the Android device&#x27;s call log, text messages, calendar etc.)<p>Our next step will be to implement in the framework the feature to save and share a document.  The spreadsheet ultimately can use that, but it can also be used in the nearer term for spinning off an app to save an Android phone&#x27;s text message history.<p>We also plan to have an app using this framework which can handle Microsoft Access databases.  The features needed to do that will help in the ultimate goal of a spreadsheet.<p>The main prioritization conflict for us is how much work to do on these cast-off apps, versus how much to do on our ultimate long-term goal of a spreadsheet.  Especially work which can&#x27;t be rolled back into the longer term goal.<p>So the question is if the game plan of writing a framework with an ultimate goal of a spreadsheet, casting off apps from the framework on the way to that ultimate goal - does that sound like a decent game plan?