Date: 25th Sep. 2024, Wed
Time: 18:00 - 19:00
Time zone: Beijing Time (UTC+8)
Meeting Links: (#腾讯会议:637-557-338)
Test opinion feedback and stage summary
周会纪要
一、反馈问题分类
- 功能问题
- 创建计划后页面刷新慢,需手动跳转。
- 计划执行次数与预期不符,数据反馈慢(9月24日晚暂停网络造成)。
- 滑点暂时固定在 0.5%,但按键存在给用户造成错觉。
- 计划剩余资金为零时缺乏提示,希望增加提示功能,如界面提醒、信息或邮件通知等,同时可增加定投倒计时。
- 已完成计划的资金提取方式不明确。
- 界面设计问题
- 部分按钮颜色不符合习惯,如 switch 的 button 为黑色,希望换成更 active 的颜色(如绿色)。
- 部分按钮缺乏说明,用户不清楚其具体功能,如三个计划按钮和 switch 的 button。
- 页面抖动,可能是后台数据刷新问题,尤其是最上面绿色数据展示部分,建议固定高度或前端修改以解决抖动问题。
- 手机端响应式问题需处理。
- 易用性问题
- 功能易用性方面,希望显示当前购买货币的总数量及划减问题。
- 创建计划时,弹窗顺序不符合用户习惯,应先出现签名弹窗,确认后再跳转其他弹窗并消失。
- 产品缺乏新手指引,可考虑增加介绍视频或类似游戏新手指引的组件,帮助用户了解如何创建计划及填写弹窗内容。
二、问题优先级排序
- 高优先级
- 解决数据显示为零的问题,包括投入资产数量、返回的 wbtc 等数据应正确显示。
- 增加计划剩余资金为零时的提示功能及定投倒计时。
- 解决页面抖动问题,提升用户体验。
- 中优先级
- 调整界面设计,如按钮颜色、增加按钮说明等。
- 优化创建计划时的弹窗顺序,符合用户习惯。
- 增加产品新手指引,提高易用性。
- 低优先级
三、分析总结
- 功能方面,数据反馈的准确性和及时性是用户关注的重点。计划执行次数、资产数量等数据应准确显示,且在计划状态发生变化时(如剩余资金为零、计划完成等),应及时给予用户提示。资金提取方式也应明确告知用户,以增强用户对产品的信任。
- 界面设计上,颜色选择应符合用户习惯,按钮说明应清晰明了,以减少用户的困惑。同时,解决页面抖动问题可以提升产品的整体稳定性和用户体验。
- 易用性方面,新手指引的加入可以帮助用户更快地熟悉产品,提高用户的使用效率。弹窗顺序的调整也能让用户在操作过程中更加顺畅。
- 对于产品的未来发展,可以考虑开源代码,邀请社区成员进行 review,以提高产品的安全性和可信度。同时,与其他社区联合推广,扩大产品的影响力。
四、反馈给相关部门
将整理好的反馈意见及时反馈给产品、技术、设计等相关部门,以便他们采取相应的改进措施。具体如下:
- 合约和后端:
- 检查接口数据和前端计算问题,确保数据准确显示。
- 优化页面刷新机制,提高数据反馈速度。
- 解决计划执行次数与预期不符的问题。
- 实现计划剩余资金为零时的提示功能及定投倒计时。
- 处理手机端响应式问题。
- 设计和前端:
- 调整按钮颜色,使其更符合用户习惯。
- 为按钮添加说明,提高界面的易用性。
- 解决页面抖动问题,优化用户体验。
- 产品:
- 考虑增加产品新手指引,如介绍视频或组件。
- 推动开源代码,邀请社区成员 review,提高产品安全性。
- 探索与其他社区联合推广的机会。
I. Classification of feedback issues
-
Functional issues
- After creating a plan, the page refreshes slowly and requires manual redirection.
- The number of plan executions does not match expectations, and data feedback is slow.
- The slippage is temporarily fixed at 0.5%, but the existence of the button gives users an illusion.
- When the remaining funds of the plan are zero, there is a lack of prompts. It is hoped that prompt functions such as interface reminders, messages or email notifications can be added, and at the same time, a countdown for fixed investment can be added.
- The method for withdrawing funds from completed plans is not clear.
-
Interface design issues
- Some button colors do not conform to habits. For example, the switch button is black. It is hoped that a more active color (such as green) can be used.
- Some buttons lack descriptions, and users do not know their specific functions, such as the three plan buttons and the switch button.
- The page jitters, which may be due to background data refresh issues. Especially for the green data display part at the top, it is recommended to fix the height or make frontend modifications to solve the jitter problem.
- The responsive issue on mobile phones needs to be addressed.
-
Usability issues
- In terms of functional usability, it is hoped that the total quantity of currently purchased currency and the deduction issue will be displayed.
- When creating a plan, the pop-up window sequence does not conform to user habits. The signature pop-up window should appear first, and after confirmation, other pop-up windows should jump and disappear.
- The product lacks a new user guide. Consider adding an introduction video or a component similar to a game’s new user guide to help users understand how to create a plan and fill in the pop-up window content.
II. Priority ranking of issues
-
High priority
- Solve the problem of data showing zero, including the input asset quantity, returned wbtc and other data should be displayed correctly.
- Add prompt functions and countdown for fixed investment when the remaining funds of the plan are zero.
- Solve the page jitter problem and improve the user experience.
-
Medium priority
- Adjust the interface design, such as button colors and adding button descriptions.
- Optimize the pop-up window sequence when creating a plan to conform to user habits.
- Add a new user guide for the product to improve usability.
-
Low priority
- Deal with the responsive problem on mobile phones.
- Consider the display problem of the slippage button.
III. Analysis and summary
-
In terms of functionality, the accuracy and timeliness of data feedback are the focus of users’ attention. Data such as the number of plan executions and asset quantities should be displayed accurately, and when the plan status changes (such as when the remaining funds are zero or the plan is completed), users should be promptly notified. The method for withdrawing funds should also be clearly informed to users to enhance their trust in the product.
-
In interface design, color selection should conform to user habits, and button descriptions should be clear to reduce user confusion. At the same time, solving the page jitter problem can improve the overall stability and user experience of the product.
-
In terms of usability, the addition of a new user guide can help users become familiar with the product faster and improve their usage efficiency. Adjusting the pop-up window sequence can also make the user’s operation more smooth.
-
For the future development of the product, consider open-sourcing the code and inviting community members to review it to improve the product’s security and credibility. At the same time, explore opportunities for joint promotion with other communities to expand the product’s influence.
IV. Feedback to relevant departments
Timely feedback the sorted feedback opinions to relevant departments such as product, technology, and design so that they can take corresponding improvement measures. Specifically as follows:
-
Technology department:
- Check the interface data and frontend calculation issues to ensure accurate data display.
- Optimize the page refresh mechanism to improve data feedback speed.
- Solve the problem of inconsistent number of plan executions with expectations.
- Implement prompt functions and countdown for fixed investment when the remaining funds of the plan are zero.
- Deal with the responsive issue on mobile phones.
-
Design department:
- Adjust button colors to make them more in line with user habits.
- Add descriptions to buttons to improve the usability of the interface.
- Solve the page jitter problem and optimize the user experience.
-
Product department:
- Consider adding a new user guide for the product, such as an introduction video or component.
- Promote open-sourcing the code and invite community members to review to improve product security.
- Explore opportunities for joint promotion with other communities.