You are browsing as a guest. Sign up (or log in) to start making projects!

ItaloJDev

@ItaloJDev

Joined June 11th, 2026

  • 25Devlogs
  • 7Projects
  • 4Ships
  • 45Votes
14 y/o maker from Brazil 🇧🇷

Learning to build robots, code and create things
Open comments for this post

17m 2s logged

Devlog #5 Today I worked on the firmware for the desk clock.I started developing the software that controls the display and manages the clock functions. The display is now able to show information correctly, and I began testing different layouts for the user interface.I also performed some basic power tests to make sure the system remains stable while running on battery power.The next goal is to refine the interface and prepare for final testing.

0
0
5
Open comments for this post

28m logged

Devlog #4 Today I focused on designing the enclosure for the desk clock.I created the initial 3D model and began adding features such as display cutouts, mounting points, and openings for the charging port and power switch.The challenge was finding a balance between a clean appearance and enough internal space for all the electronics.Next, I plan to print a prototype and verify the fit of the components.

0
0
3
Open comments for this post

35m 2s logged

Devlog #3 Today I started working on the PCB layout.I placed the major components on the board and began routing the connections between them. My goal was to keep the design compact while still leaving enough space for assembly and wiring.This stage required several adjustments because I wanted the board to fit properly inside the future enclosure.The board is starting to take shape, and I am getting closer to ordering the first prototype.

0
0
4
Open comments for this post

54m 1s logged

Devlog #2 Today I finished the schematic for the desk clock.I connected the Wemos D1 Mini, SPI display, battery charging module, power switch, and battery connector. I also reviewed the power distribution to make sure every component would receive the correct voltage.While working on the schematic, I spent some time double-checking pin assignments and making sure the display connections matched the documentation.Now that the schematic is complete, I can move on to designing the PCB layout.

0
0
7
Open comments for this post

3h 29m 5s logged

Devlog #1I decided to change the direction of my previous project and start working on a custom desk clock instead.Today, I focused on designing the electronics for the new project. After researching different options, I selected the main components: a Wemos D1 Mini (ESP8266), a Gc9a01 display, a rechargeable Li-ion battery, and a charging module with integrated protection and 5V boost conversion.Most of my time was spent planning how everything would connect together and making sure the power system would work reliably. Instead of using a standard TP4056 charger, I chose a charging module with a built-in boost converter so the Wemos can receive a stable 5V supply even as the battery discharges.I also started organizing the component placement for the custom PCB and thinking about how the electronics will fit inside the enclosure.Next, I will finish the schematic and begin routing the PCB.

0
0
2
Ship Changes requested

I just shipped my personal workspace portfolio! This project was a deep dive into building a clean, functional digital home for my work. It features my recent projects and acts as a hub for my development journey. I used an AI-assisted workflow to speed up the coding and UI refinement process, ensuring that the final structure is solid and well-documented.

AI Transparency:
This project was developed with the assistance of AI tools to accelerate the workflow and refine technical implementation. While AI supported the brainstorming and coding processes, all logic was reviewed, tested, and integrated manually to ensure quality and maintain full project ownership

Try project → See source code →
Open comments for this post

37m 45s logged

Finally wrapped up the core development of my portfolio site. Spent the last session refining the layout and ensuring everything is responsive. It is officially live, and I am really happy with how it turned out. Onto the next challenge!

0
0
5
Ship

What I built

DevLaunch is a modern full-stack SaaS platform built to help developers, students, makers, and startup founders transform ideas into finished products.

Many people start projects with excitement but lose momentum due to poor organization, scattered tools, and unclear next steps. DevLaunch solves this by providing a centralized workspace where users can plan, manage, track, and launch their projects from a single dashboard.

The platform includes:

Secure user authentication
Project creation and management
Task organization and progress tracking
Project roadmaps and milestones
Modern responsive user interface
Scalable full-stack architecture

My goal was to create a tool that reduces the friction between having an idea and successfully launching a product.

What was challenging

The most challenging part was designing a platform that feels simple to use while remaining scalable behind the scenes.

I had to think carefully about application architecture, user experience, database structure, authentication flows, and how future features could be integrated without requiring major rewrites.

Balancing usability, performance, and maintainability was a significant part of the development process.

What I’m proud of

I’m proud of building something that solves a problem I’ve personally experienced.

As someone interested in technology and product development, I’ve seen how easy it is for projects to become disorganized and eventually abandoned. DevLaunch was created to address that challenge directly.

I’m also proud that the project was built with a long-term vision rather than as a simple prototype. The architecture is designed to support future features such as AI-assisted planning, intelligent task generation, team collaboration, and external integrations.

How to test
Create an account or log in.
Access the dashboard.
Create a new project.
Add tasks and milestones.
Track progress through the project workflow.
Explore how DevLaunch helps organize the journey from idea to launch.

DevLaunch is actively evolving and represents the foundation of a larger vision: making it easier for builders to create, manage, and launch meaningful products.

Try project → See source code →
Open comments for this post

15m 30s logged

[FINAL SHIPPED] DevLaunch - Fullstack SaaS Template Generator Hey everyone! 👋 DevLaunch is officially LIVE and shipped to production! 🌌DevLaunch fixes the frustration every developer faces: losing time setting up standard project boilerplates (folders, dependencies, routing) every time you start a new idea. It lets users configure, preview, and download ready-to-go, production-grade project baselines instantly in .zip format.Here is a quick breakdown of the architecture, hurdles, and the final results.🛠️ Tech Stack & ArchitectureI built a modular Monorepo with decoupled Frontend and Backend services integrated with a cloud database:Frontend: Built with React.js (Vite). Features a responsive UI with side-navigation, route guarding to prevent unauthenticated access, and a Theme Engine that transitions instantly between Dark and Light Mode.Backend: A Node.js & Express API server handling secure registration, authentication flows, and profile updates (like reactive live database password changes).Database: Hosted entirely on Supabase (PostgreSQL), storing user profiles and tracking real-time project generation logs.⚡ Key Features ShippedDynamic ZIP Generation: The backend doesn’t just store old static zip files. When a user inputs a name and clicks download, the server dynamically aggregates raw code templates, compresses them on-the-fly using binary archivers, and pipes the .zip stream straight back over HTTP.Code Preview Subsystem: Built an interactive visual editor UI that mimics VS Code. Users can click through code tabs (e.g., App.jsx, server.js) to inspect the boilerplate files before generating.Account Management & Caching Fix: Shipped a clean visual update to the account settings. Fixed a critical state persistence bug where newly registered users would fallback to placeholder metadata, ensuring emails and IDs map accurately from localStorage.Free-Tier Cloud Deployment: Frontend is live on Vercel, Backend is on Render, and Database is on Supabase.🧠 Technical Hurdles & Learnings1. Node.js Memory Stream PipelineInstead of saving files locally on the server disk first, zipping them, and deleting them (which is highly inefficient and risks disk bloat), I utilized Node.js Streams. By integrating archiver, the app pipes raw data buffers directly into the Express network response stream (res). The file is compressed directly inside RAM and pushed out instantly.2. State Syncing & Visual BugsDuring staging, user data looked like it was missing. I discovered a funny bug: the user’s email was rendering perfectly from database storage, but as pure black text on an ultra-dark background! Additionally, the signup flow wasn’t caching the newly registered email address into client session storage. I rewrote the Cadastro.jsx logic to properly cache metadata upon creation and injected high-contrast styles (#38bdf8).🎯 Verification & Links[x] Registrations write to PostgreSQL flawlessly.[x] Route guards instantly eject unauthorized visitors back to /login.[x] ZIP generator pipes compressed streams immediately.Huge thanks to the Hack Club Stardance community for the fuel to push through the roadblocks! Check out the live build and let me know your thoughts!On to the next ship! 🛸✨

0
0
2
Loading more…

Followers

Loading…