iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Building a small AI tool is not just a matter of sending a prompt to an API. In a first-person account on DEV Community, creator wertsdfgwerg describes making AI Toolbox, a browser-based collection of writing and productivity tools, and learning that a successful API response can still lead to a frustrating user experience.
What the AI Toolbox includes
The creator describes AI Toolbox as a collection of lightweight tools that people can use in a browser without an account, complicated setup, or much technical knowledge. The listed features cover prompt generation; resume creation and improvement; title and Xiaohongshu title generation; email writing; article polishing and summarization; reply writing; and social media post creation. The site is described as supporting Chinese and English.
These are the creator’s descriptions of the project, not an independent assessment of current feature availability. The post does not report user numbers, adoption, revenue, or measured user satisfaction.
Where the build became difficult
The author expected the interface to be the hard part, but says the real challenges emerged while connecting the website to an AI API. They describe working through API requests, POST requests, CORS, API keys, Cloudflare Workers, and getting results to display correctly in the page.
#1 Best Overall
The author profile lists HTML, CSS, JavaScript, GitHub Pages, Cloudflare Workers, and AI APIs among the creator’s skills or current learning areas. The post does not identify the API provider, model, framework, or full architecture, so it does not establish a specific stack that readers can reproduce step by step.
Why a working request can still produce a poor tool
The author reports several different failure points: an API can work while the frontend does not; a request can appear correct while its response disappoints; and a technically functioning tool can still feel poor when the output is badly formatted. These are distinct problems. Debugging the connection does not, by itself, fix an unclear interface or an unhelpful result.
As the author puts it, “Making something work and making something usable are two different problems.” The distinction is the central lesson of the project account: an API response is one part of the experience, not the finish line.
Recommended Free Tools
What to consider after the API responds
The author points to the details that shape whether a small AI feature is understandable and useful. A builder should consider the complete path from a person’s request to the next action:
- Input: Make clear what the user should enter and how to describe the task.
- Errors: Decide how the interface responds when a request fails, rather than leaving the user with a blank or confusing result.
- Formatting: Present the response in a form that is readable and useful for the task.
- Language: Ensure the output matches the language the user selected or expects.
- Next step: Help the user understand what to do with the result or how to continue.
These are the author’s reported usability considerations, not a claim that the project implements each one in a particular way. The post’s broader point is that input design, error handling, output presentation, and language behavior all influence the experience beyond the API call itself.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.A personal project still in progress
The creator presents AI Toolbox as an ongoing personal project, with the goal of making the tools feel more natural and useful rather than simply placing an AI API behind a button. The account does not provide cost figures, usage limits, performance tests, error rates, time savings, or evidence of user adoption. It is a project retrospective, not a comparative product review or quantified results report.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
