Rise team, I have few suggestions
1) Prevent sending clear password to dapp owner to make some transaction. This clearly violates user password policy. Dapp is hosted by third party vendors. How do they can be trusted by users to send clear passwords. I have been thinking few solutions to address this problem.
2) Force dapp owners to host them on ssl to prevent man in the middle attacks.
3) I would suggest to provide some space for proof of existence like factom. The advantage of Lisk and Rise are sidechains. I have few ideas, It can be big and widely accepted.
4) I would suggest to push dapp ui builder on priority. I have been working on this for lisk (refactored lisk-cli). still it depends on node platform. My idea is to create dapps in the browser without any direct dependence on the node.js (should execute in the browser or some remote api). Thinking of some browser hosted apps such as chrome app. Its really painful to developers to go linux and generate a dapp there. Most of the users like me using windows.
5) Give priority to clients for all os including mobile(With lisk , So many users have no idea on windows,). User experience is the first target. It should be easy to use.
I'm silently working on some dapps in my free time, (I think not much difference , only UI framework changes between Lisk and Rise). If time permits, hopefully I can finish them by launch date. Also windows 10, and 8 client.
Hope everyone had a good weekend! I'll be responding to the above in our Daily Dev update later today.