I also agree with you and really appreciated to have it shared.
It is amazing that our community is caring what is missing for new users. We had a previous UX discussion here just for reference. Thanks @tksarah for your suggestions too but we may not allocate resource for big changes. Thank you also @Matt for your suggestions too.
The core team is small and the portal development is not the main scope, while I totally understand that Astar interoperable solution we made 2 years ago was too early to the market to adopt. We have XCM as transfer, rather than bridge since it was the way we wanted to push the feature that is more than bridge. However I would not mind moving XCM to bridge section now when we have time. Confusingly we have two VMs and have transfer interoperable. Technically, this is not a bridge and is correct to be where it is now.
With limited time we can allocate to portal development, as I promised to previous discussion, we will change the placeholder message as below so users can understand they can put EVM address/Astar Native address in the field.
Destination Address ----> 0x...(EVM) or Astar Native addresses
We are not going to remove Bridge option from left sidebar, since this is more for users to bring assets to Astar, it is important actions we must be offering them at first view. We could add one banner for EVM <> Native in the bridge page, this will avoid a UX dead-end who wanted to find how to bring ASTR to EVM from Native, but came to bridge page. Thank you for noticing, actually this will make a smooth experience.
So to conclude, I promise to update the portal
- Change the message for input field placeholder
- Add ASTR transfer EVM<> Native on bridge page
Apologies not fully being aligned with your suggestion but those small kaizen will indeed make UX better.
Please feel free to share what you think, we can add small kaizens for better UX but big contractual change is not planned unless it impacts on TVL. Thanks a lot for great contributions!