Arena mobile (official and unofficial)

Dear OF team, dear Rajkumar, I thought I could comment on this discussion since I have some related suggestions that came out of trying and testing these two versions of the mobile Arena. I understood (I read it in another post I think) that the unofficial version has as purpose to test functionalities or interface features, for eventual integration into the official app. So in that context, I am listing below some features that I have particularly liked in the unofficial version (MAM) and that I personally would like to see implemented in the "Arena Mobile" official version (AM). I also comment on some other features. -First just to mention features that I do like in the official version: Generally, I like the look, and especially the way the attributes are displayed all with the attribute name, followed by a box that always fills the full width of the screen. The 'description' is not visible for the attributes, and the screen has a nice symmetry. When the user taps on an attribute, this opens in a full screen where we now can see the attribute description, and the elements of a list, also with their description, with nice coloring and nice symmetry. I also very much like the option to set up the "Images quality and sizes", although so far I could not make it work. But it is nevertheless a well needed option considering that most smartphones now easily take photos with far too high resolution for what is needed within an Open Foris use. -My main issue (so far, with what I tested), in the official AM, is about the 'bottom information box', specifically, and the navigation between records and within the hierarchy, in general. I copy paste some screen shot below to explain. In AM, the bottom box (with 'current page', 'delete this item', 'Show as form', 'New row', 'Back to previous entity', 'Go to next entity') is far too big. It occupies more than 35% of my screen height. Firstly, I think that this height is unnecessary since navigation works very well and is very intuitive with the MAM solution (which has just one row of height for the bottom box/line). The top button 'New rows' works fine in MAM, and then the back button allows to quickly get back to a table view. Long tap on a records allows to view the 'delete' option. This all works very intuitively and also corresponds closely with the interface of Open Foris Collect (to which users are already familiar). Secondly, in AM, the oversized and overloaded bottom box may (and does) confuse or distract some users from the most important, which is the list of attributes in the code of the screen. Thirdly, the oversized bottom box becomes very problematic if users turn their phone horizontally, which I believe is an important feature. For example, users will sometimes want to see the entity as a table ('Show as table'), and then they would like to turn the phone horizontally to see as many columns as possible, and at the same time see as many rows as possible. But this does work because in that case the bottom box occupies almost ¾ of the screen height! This function worked so nicely in Open Foris Collect (with the third button to the top right corner of the screen). Having the bottom box reduced to one row, would provide the same advantage in Arena. -In MAM, everything is very clearly readable, while in AM (in both the light and dark themes), I cannot really read 'read only' attributes and the top green line (because of the color contrast of the text). I have seen a couple of posts by others describing the same issue. Read only attributes need to be readable. -Read only attributes should also be 'selectable'. Users may need to copy the read-only code attribute in order to paste it later elsewhere. But this is not possible in AM (it works in MAM). The users should be able to tap the read-only attribute and be able to long-tap and select the text string or part or it. -In both AM and MAM, there is an important feature that was added in Open Foris Collect but is lacking here. For, list attributes, after having selected an element of the list, users should be able to 'unselect' it (in case they change their mind, and actually do not want to pick anything from the list).

I hope that this is helpfull. I am available if there are clarifications needed. And I thank you for your help with Open Foris tools. Bruno