Application Web - TACO
At the beginning of 2026, I started developing a website focused on nutrition and health, built on top of the Brazilian Food Composition Table (TACO). A few months ago, I made another post about the project, where I described the main idea and gave an overview of the application — essentially a showcase of the software, its purposes, and who it is recommended for. Today, I’ll write about the next steps I’m considering to continue scaling this application, especially since in recent days I’ve noticed an increase in traffic and API key generation. At the moment, there are around 30 API keys already created and more than 4,000 requests being handled.
Scalability Prologue
The first idea I had was to create something more focused on healthcare professionals — a separate system that would communicate with this application through microservices, making it possible to integrate with other systems. While this current application was developed with a more general-purpose approach, the new system would include access control, user accounts, nutritional tracking, and so on.
Personally, I’ve always had an interest in nutrition, and at certain points in my life I found myself counting macros, hitting protein targets, and weighing rice in almost every meal 😄
For personal use, I’ve been using the app to plan my meals, and a few months ago I gathered feedback from some nutritionists to whom I presented the project.
Below are the main suggestions they gave:
- Household measurements
- Food-related informational content
- Meal plans
- Various calculators
Updates
The day after this post (04/25), I added some new features to the application, which I believe have increased the value of the website even further.
Some improvements were also made regarding the API, with normalized data.
That’s all for today.
