Currently, there are many logging software options available. In this environment with so many choices, I highly recommend that everyone find a unique and differentiated feature to focus on and refine. This particular software has achieved this by specializing in the scenario of using a master console, and BG4QBF himself personally tested it on a network, achieving very high efficiency. This demonstrates that the software is not just theoretical but based on real-world experience.
However, in order to make this software even simpler and more accessible for a wider range of users, including those with no programming experience, the following critical feedback is necessary:
The reason why it "requires a certain amount of time to get used to" is that the software's interface design is too "programmer-centric," and it's designed for employees with less than three years of work experience, which doesn't align with the typical "intuitive" interaction logic of most software. For example
- After clicking to start, it's a black window that's incomprehensible to non-computer professionals. Besides "业余无线电通联记录助手" (amateur radio communication record assistant), there are no other Chinese prompts. It looks like a landmine array and cannot be closed; you also need to open a browser and manually enter the URL. The interface could easily include prompts such as "Please do not close this window during use" and "Please enter localhost:5973 in your browser to access the system," and it could automatically pop up the browser window.
- I tried sending the frequency multiple times, but I kept getting an error message. To figure out the correct format, I had to read the README. Even when the difference between the upper and lower frequencies was an integer, I needed to include a leading zero. Also, for frequency values, I had to enter them as numbers.
+0.0In fact, it can fully use placeholders, relax the formatting slightly, and then automatically help users correct common input methods.
- The fields for "Device," "Power," "Antenna," and "QTH" should be left blank.
- Click on the template to submit, and then clear the contents of the dictionary below. Click on the dictionary to submit, and then clear the contents of the template above. In reality, users don't need to worry about the two files being different technically; they can simply click a "Save" button to save both at once.
- The text was filled with technical jargon that made it difficult for non-programmers to understand, for example:
- Instead of using templates (tmpl) and dictionaries (dict), it's more straightforward to use "Common Callsigns" and "Common Equipment/Antennas/Locations".
- Instead of submitting templates and dictionaries, it's more intuitive to use "Save".
- Marked for deletion – either allow restoration, or permanently delete it (first display a prompt asking if you want to delete it, but after clicking "delete", the item should no longer be visible and cannot be restored).
- Unparsable frequency – It should be communicated to the user what the correct format is, or consider implementing error handling to help the user correct it.
- Add new device entry / Add new completion entry – Place the new completion entry directly in the "Device Completion" box, so you don't need to write as much.
- The README contains a lot of content that is difficult for non-programmers to understand. It should be manually reviewed or processed using AI, and the content intended for general users should not include technical terms such as "API key," "0.0.0.0:5973," or instructions on opening the frontend page.
- The interface should be enhanced using a UI library (such as Bootstrap). For some buttons, such as "Delete this item," "Move this item up," and "Move this item down," use icons instead of text. Also, apply `border-collapse` to the table to avoid having double borders.
Regarding AI, if you're going to use it, especially for mundane tasks like error handling and data standardization through manual input, then do so. This type of code can be easily handled by AI, with additional human testing, rather than wasting your time and effort.
These changes generally don't involve logic (except for the frequency one, but AI can help write parsing programs), and simply adjusting the page layout can bring significant improvements to users who don't understand programming. If you want to promote these changes to a wide audience of radio enthusiasts, you should assume that you completely lack programming knowledge and feel intimidated by seeing code, then design and implement UI and interaction logic without "programmer thinking."
Finally, while the comments above may seem harsh, they are without malice. I hope you continue to refine this unique software and help more users achieve their goals. Good luck, 73!
闽ICP备2021006864号-7
闽公网安备35020602002794号
互联网举报中心