When introducing the 'Display Name' field name is only used for versioning purposes. The word 'name' does not reflect its true purpose. IMO that field should be auto generated (may be based on the display name) and it should not include spaces, and other special characters and it should act as a unique id. So we can discourage users to enter values to that field.
Also note that the number of screenshots will be increased in AppM 2.0, it could be at most 20 and be vary based on the screen sizes. We need to figure out storing all them in the registry is a good concern. On Tue, Jun 9, 2015 at 1:53 AM, Sajith Ariyarathna <[email protected]> wrote: > Hi All, > > Mobile apps versioning support in the current release of App Manager is > somewhat limited. We are hoping to improve this in the next release. > Recently, we have improved the web app versioning support in App Manager > [1]. By following a similar manner, we are hoping to implement this feature > for mobile apps. > > *Feature Requirements* > > - End-user should not see different versions of the same mobile app in > the store. > - End-user should be allowed to access only one version of a mobile > app in the store and that version is determined by the Publisher. > - When there are multiple versions of a mobile app, only one version > should be in the ‘Published’ status at a given time. > - Publisher should be able to publish a particular version of a mobile > app at any time and previously published version of that mobile app will be > unpublished automatically. > > The current mobile app versioning implementation needs be revamped to > assist the implementation of this feature. To do that, following tasks must > be carried out before implementing this feature. > > *1. Fine-tuning mobile app life cycle* > > In web apps, life cycle action to publish an unpublished web app is > "Re-Publish". However in mobile apps, equivalent life cycle action is > "Publish". This needs to be altered to "Re-Publish" in order to be > consistent with web apps. (see below diagram) > > > *2. Implement "Create New Version" functionality for mobile apps* > > In web apps, publisher can create a new version form an existing web app > by clicking on a web app and then clicking on "Create New Version" button. > Similar functionality should be implemented for mobile apps. > > > *3. Moving attached images of mobile apps to the registry* > > Maximum 05 images can be attached to a mobile app (01 banner, 03 > screenshots & 01 icon). Currently these images are stored in the file > system. However, these images should be stored in the registry. In the > current release, images attached to a web app (maximum 02) are stored in > the registry. > > > *4. Add "Display Name" attribute for mobile apps* > > The "Name" attribute of an app acts as a unique identifier. Therefore it > cannot be changed overtime. To overcome this limitation, "Display Name" > attribute was added for web apps; but not for mobile apps. Therefore > "Display Name" attribute should be added for mobile apps to be consistent > with web apps. > > > > Any feedback is appreciated. > > Thanks & Regards > > [1] [Architecture] Improving app versioning support in App Manager - (Next > release) > > -- > Sajith Ariyarathna > Software Engineer; WSO2, Inc.; http://wso2.com/ > mobile: +94 77 6602284, +94 71 3951048 > -- Regards, Chatura Dilan Perera *(Senior Software Engineer** - WSO2 Inc.**)* www.dilan.me
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
