AWS Wickr was not embedded directly into the mobile app; instead, it was used as a secure internal collaboration layer for the development and operation teams, which supported secure coordination around mobile development, testing, and releases.
Senior Software Engineer at a computer software company with 201-500 employees
Real User
Top 10
Feb 4, 2026
In my experience with AWS Wickr, the most noticeable pain point is usability. While the security model is strong, the user interface feels dated compared to modern collaboration tools, and non-technical users often need onboarding and guidance, which slows adoption. Improving the UI and UX and simplifying common actions would make a significant difference. Regarding the mobile experience with AWS Wickr, while the apps are secure, they feel less polished than mainstream messaging apps. Navigation is unintuitive and actions require more steps than necessary, along with notification reliability issues. There is limited flexibility for short-term users. Several additional improvements for AWS Wickr could enhance the platform, such as guest or external user management, analytics and reporting, change management and release communication, disaster recovery transparency, policy simulation or testing, and better documentation for advanced scenarios, which are major areas that could see improvement.
AWS Wickr is in a great direction and I feel that if they have to improve on something, then definitely in the future, they can improve on AI and ML features which will be helpful. Apart from that, I do not feel that they need improvement because they are doing really well. As per our needs, it has given us a good return on investment and so far, I did not face any challenges. However, if there is something which can be improved, the adoption and the network effects can be improved. The user base is much smaller than the mainstream chat apps, so they can definitely work upon that.
AWS Wickr was not embedded directly into the mobile app; instead, it was used as a secure internal collaboration layer for the development and operation teams, which supported secure coordination around mobile development, testing, and releases.
In my experience with AWS Wickr, the most noticeable pain point is usability. While the security model is strong, the user interface feels dated compared to modern collaboration tools, and non-technical users often need onboarding and guidance, which slows adoption. Improving the UI and UX and simplifying common actions would make a significant difference. Regarding the mobile experience with AWS Wickr, while the apps are secure, they feel less polished than mainstream messaging apps. Navigation is unintuitive and actions require more steps than necessary, along with notification reliability issues. There is limited flexibility for short-term users. Several additional improvements for AWS Wickr could enhance the platform, such as guest or external user management, analytics and reporting, change management and release communication, disaster recovery transparency, policy simulation or testing, and better documentation for advanced scenarios, which are major areas that could see improvement.
AWS Wickr is in a great direction and I feel that if they have to improve on something, then definitely in the future, they can improve on AI and ML features which will be helpful. Apart from that, I do not feel that they need improvement because they are doing really well. As per our needs, it has given us a good return on investment and so far, I did not face any challenges. However, if there is something which can be improved, the adoption and the network effects can be improved. The user base is much smaller than the mainstream chat apps, so they can definitely work upon that.