as introduced a few weeks back we started work on the governance aepp to implement a polling system via smart contract as described here: Governance Polling System Aepp Introduction
Yes, that’s the issue. As written in the initial post version 0.9.0 or greater is required. Version 0.8.11 shipped with a sdk that included a bug and earlier versions are incompatible with the sdk the aepp uses.
Re: iOS version: we are currently held back by the iOS App Store review on releasing version 0.9.0. We are working with them to resolve the concerns the reviewers have. I will post here when we have released a version newer than 0.8.11 in iOS.
I tested the governance aepp. It worked well for me!
Comments:
We really need an aepp icon…
There was a slight lag after authorizing my account, when I was not sure if the aepp will ever load. It did eventually. So I succeeded. But if the lag/wait time was significant enough I would have assumed it will not work and left.
The loading indicator was over the message saying I should switch to the Testnet. I read the message anyway… but somebody else might not.
I think it’s a bit tricky to ask the user to input block height for the closing without them having any context for when a certain block height would take place without entering it. To resolve this “chicken or the egg (which comes first)” puzzle, I recommend a few placeholder values are added for selection… which correspond to say 1 week, 1 month, 1 year… so that the user has something to relate to… once they select one of the placeholder values they will see the calculation of the estimate below the input field (and could more easily navigate things from there).
I was slightly lost in the UI at first. Because there are quite a few elements. The bottom row of icons was harder for me to interpret than the top menu items. Since we are in the testing phase this works. But it’s also a good idea to do some user tests on alternative UI/UX options… to get to a more elegant solution.
Do you notice this behavior every time you open the aepp? During the first load we do a rather extensive wallet search to offer you a choice if we detect more than one wallet. This is why it might take some time initially.
Good catch! We will address this.
I will experiment a little with this. It is rather tricky as we do not want to suggest we could predict the time a block height is reached but we know its basically impossible to estimate a date in block height without technical knowledge. What would you think if we prefill the input with a block height roughly a month or two in the future which would also provide the user with an idea on how long a poll should be open?
Yes I agree. We still have the problem that we don’t want to double up on the base aepps top navigation which is why we opted for the bottom approach. We will continue to gather user feedback on this topic and might update the ui if we see the need for it.
Yes, without balance the transaction fee for creating a poll or participating in votes can not be covered, nonetheless we should improve the error message. Thank you for the feedback
