Project

General

Profile

Specification #451

Updated by Benoit Duffez over 8 years ago

h1. Features sets

h2. Free features
* #272
* #360
* #394
* #399
* #422
* #423

h2. Not sure yet
* #241 - Textile macros

h3. Paid features

Features locked with the full version (must haves / very nice features are detailed in this list):
* #246 - Share intent
* #324 - Issue attachments
* #417
* #435 - Project 'activity' redmine (web version) tab
* #439 - Text editor
* #444
* #221
* #249 - App widgets

h1. Development

* 0.11 is kept as is
* 0.12 is used as development of free features
* 1.0 will be published with all features, including IAB

h2. Branching

<pre>
name last 0.11 0.12.0 .1 .2 .3 .4 1.0

master _____x_______________x_____x____x____x_______x__________________________x

develop \______________/_____/___/____/_______/ \______________/_____/_____/____/_______/ /

IAB \___ ? /
paid \_________________________________________________________/

</pre>

* @master@: used for google play releases
* @develop@: used for free features pushed to 0.12 branch
* @IAB@: used to put IAB APIs available, maybe with donate (hence the "?")
* @paid@: used for
paid features pushed to 1.0 branch

\____________________________________________________________/

h2. ideas
* Make a lot of features only for the paid version => branch apps?
* Subscription or single-time payment?
* 5€? 10€?
* separate users and companies?
* free for OSS contributors?

publishing:
* publish a version with donate only, then another version with free/paid, and allow donators to get the full version for free
* publish the IAB as a beta/alpha version with testers, who will get the full version for free afterwards

building:
* http://stackoverflow.com/questions/19296068/build-android-with-gradle-replace-string-each-product-flavor

Back