Thank you very much for detailed statement and I m glad to see our voices are reaching out to you and your team to make our platform better.
From my point of view, “UI” is far most important element to run such application among others. As it is quite easily noticiable by anyone who interact with the app. Just a app users (no app creator) will see and evaluate our app once they get onboard. So it is quite important how it LOOK like and visually appealing.
After google get to you and us, it is quite understandable that Google will steer the hundle to guide the company where we go. It is no-doubt that new features such as Apigee, Automation stuffs which is in pipeline will be adding fuel to appsheet to get more functional, but from my prospective as Appsheet creator, there are other functions and features which could be prioritilized rather than those new features. “UI” improvement is one of them.
New expression, New style of UI and new logic etc, those are immidiately affects to all the app creator, meaning those will get the interest swiftly. Such a basic new new features and function will also drive us, appsheet creator, to come up with new idea and usage which would be de-most important for majority of community members.
Yes, decision to draw the picture of the new feature road map is absolutely upto Appsheet team as platform operators, but I hope there should be determinting factors, such as how much majority of the app creator are awaited and in need. For instance, once Apigee stuffs are in full swing, I dont thing majority of app creators will start to use it. (dont take me wrong, I m not saying we dont need such a feature).
For instance, it looks tiny stuffs, but if we could display value of YES/No type column as arbitrary text value rather than Y/N, I would say 100% users would welcome that.
Appsheet is growing, naturally team is getting sizable, and team management should altered to fit with it, but i wish to hope the distance between App creators and your team member will get closer like we were so before Google. We can get knowledge, why this new feature is difficult and take time throughout the converasation with Appsheet folks, and there should be benefit to appsheet forks to get the direct feedback from the app users… Should be win/win relationship.
Off course, there is technical feasibilities and difficulties that should be taken as factors to decide which one will be prioritize or not.
Bring the subject back to UI stuffs. I dont think we are in a rush, although we need improvement in a first place, as it will broadly affect almost everything in appsheet. These days, the topics thrown into this community is largely UI related or related bug report etc, which make me frastrated to access to the community thread. (so i get lessers posts these days, as I honestly fed up)
I appreciate Appsheet approach which others do not take. New feature is ready, then deploy immediately rather than waiting for major release and version changes.
However, in terms of UI changes, I think we should take the normal development approach for this occassion. Just test the new UI under the test account, before deploying. I think we can get bunch of volunteer to be a tester and provide the useful feedback. Once the test goes well, then release major ones.
New UI come up, which makes old UI broken. People get complaining. Revert it back.
Push new UI, and repeat the same process. It is absolutely not a good idea and just killing time and effort of everyone, it could dangrously spoil all the effort made by Appsheet forks who are tirelessly work on new code to make the platform better.
To close, thanks again, and I m glad to be a member of Appsheet team!