Read KORVYN details
Implemented React and TypeScript concept: detailing services, three real concept packaging renders and service/product enquiry flows. No sales or booking integration.
SOFTWARE ENGINEERING DESIGN-LED DEVELOPMENT
From standout landing pages to reliable digital systems. I blend considered visual design with practical engineering to turn ideas into experiences worth using.
A DIFFERENT APPROACH
I bring visual direction and software thinking into the same process — because a memorable experience should also be useful, responsive and built to last.
SELECTED WORK
Different challenges. One standard: intentional design, functional experiences and engineering decisions that make sense.
Implemented React and TypeScript concept: detailing services, three real concept packaging renders and service/product enquiry flows. No sales or booking integration.
A fictional barbershop website with a step-by-step booking experience and WhatsApp handoff. This is a personal demonstration project, not a commissioned client site.
A work-in-progress Linux diagnostics and monitoring project combining .NET and real system data with a React interface.
Independent operational software in development. This cover is the official public project illustration, not confidential dashboard data.
Independent projects and fictional-brand studies, not commissioned client work. Cover illustrations are visual concepts; real interfaces appear inside the project breakdowns.
MORE ON GITHUBEXPERTISE
A / FIRST IMPRESSION
Distinctive, responsive pages with clear messaging, strong visual hierarchy and intentional paths to action.
B / EXPERIENCE
Tools, dashboards and connected applications designed for real usage — not merely to look good in a screenshot.
C / THE FOUNDATION
Services, integrations and software architecture with attention to reliability, maintainability and practical complexity.
HOW I THINK
Every project starts with the problem worth solving. Then come the right structure, the right visual language, and the code that turns it into something people can actually use.
Goals, audience and constraints.
Direction, experience and architecture.
Implement, test and refine.
THE PERSON BEHIND THE WORK
My name is João Victor. I'm a software engineering student and independent developer based in Brazil, building everything from expressive websites to the systems behind complex products.
I care about clarity, details and useful engineering. The goal isn't to add complexity — it's to make each experience feel deliberate and each solution dependable.
Have a landing page, web application or more ambitious system in mind? Tell me what you want it to do.

AUTOMOTIVE DETAILING / LANDING PAGE & PRODUCTS
A complete automotive-care concept combining service discovery and three interactive product presentations.
An accurate look at the interface decisions, engineering work and current limits.
KORVYN Auto Lab is a fictional automotive detailing studio and aftercare brand. The challenge was to explain both detailing services and three product concepts while keeping one recognizable identity.
FOCUS / SERVICES + PRODUCT ENQUIRIESA mineral-white and charcoal editorial system, consistent Manrope typography and genuine licensed illustrative detailing imagery build hierarchy. Product colors appear inside the collection, not across unrelated sections.
DIRECTION / REFINED AND COHERENTThe React and TypeScript site uses GSAP for directional product transitions, responsive layouts, keyboard and swipe controls. The collection displays Exterior Coating, Wheel & Tire Cleaner and Interior Cleaner using the actual concept packaging renders.
STACK / REACT · TYPESCRIPT · GSAPVisitors can explore detailing services or the product collection and prepare an enquiry. The prototype has no checkout, server-side lead capture or confirmed bookings; there is no evidence for a conversion-rate claim.
JOURNEY / SERVICE OR PRODUCT → ENQUIRYThe page, product interactions and responsive layouts are implemented and documented. The brand and formulas are fictional, imagery is illustrative and real commercial effectiveness has not been validated.
STATUS / FUNCTIONAL CONCEPTA working React/TypeScript prototype with a connected detailing-services journey, interactive GSAP product collection and enquiry handoff. No checkout, booking system or verified sales claims.
Three distinct fictional products, shown using the actual packaging artwork from the project—not substitute mockups.




KORVYN is a fictional brand. The product artwork and screenshots are from the authentic development project. Formula performance, sales, confirmed orders, paid commissions and service results are not claimed.

BUSINESS WEBSITE / GUIDED BOOKING UX
A barbershop concept where choosing a service leads naturally to requesting an appointment.
A transparent view of the decisions, process and current state behind this work.
The fictional barbershop needed more than an attractive introduction. A visitor should understand what the studio offers and move toward requesting a preferred time without losing context.
GOAL / REQUEST A BOOKINGEditorial photography and a quiet typographic system present the brand. The booking interaction becomes a focused, staged interface rather than a long list of selections buried on the page.
DIRECTION / CALM & FOCUSEDThe local prototype uses HTML, CSS and JavaScript for service and add-on selection, preferred date and time inputs, and a WhatsApp message handoff. Local contact configuration stays outside this portfolio.
STACK / HTML · CSS · JAVASCRIPTThe sequence guides visitors through service, options, timing and confirmation. It is designed to make the booking request clearer; completed appointments or conversion uplift have not been measured.
JOURNEY / CHOOSE → CONFIRM → CONTACTThe service site and staged appointment-request flow exist as a personal project for a fictional business. The design can be adapted for a real business only with real information and authorized imagery.
STATUS / LOCAL WORKING DEMOA functioning staged booking interface and an editorial service website. No confirmed bookings or real business metrics are asserted.

Personal demonstration for a fictional business. The local booking configuration and personal contact number are not included in this portfolio. The website itself uses illustrative photography licensed through Pexels.

SOFTWARE ENGINEERING / LINUX DIAGNOSTICS
System visibility through real diagnostics, not decorative numbers.
A transparent view of the decisions, process and current state behind this work.
Linux diagnostics generate useful numbers, but raw telemetry alone rarely helps explain system health. The goal is to make local machine state easier to understand and investigate.
GOAL / DIAGNOSTIC VISIBILITYMetrics, processes and service states need clear hierarchy, consistent labels and recognizable missing-data states. Readability matters more than displaying as many charts as possible.
DIRECTION / SIGNAL OVER DECORATIONC# and .NET diagnostics collect local Linux information, with an API and React interface to present supported measurements. Probes and permissions must remain explicit about what they can observe.
STACK / C# · .NET · LINUX · REACTThe interface should help someone locate a problem, inspect relevant evidence and distinguish unavailable telemetry from a healthy reading. This is a usability and reliability objective, not a commercial conversion funnel.
JOURNEY / OBSERVE → INVESTIGATEA local diagnostics prototype and genuine telemetry capture exist. Broader reliability, permission handling and future alerts are ongoing work rather than finished product claims.
STATUS / IN DEVELOPMENTWorking local telemetry and diagnostic screens. Explicitly distinguishing unavailable readings from valid measurements remains important.
Independent project in progress; not presented as a finished commercial monitoring service.
FIELD-SERVICE OPERATIONS / WEB APPLICATION
Coordinating service requests, work orders and field execution through a clearer operational workflow.
An accurate look at the interface decisions, engineering work and current limits.
AFServiceOPS addresses the operational gap between receiving a service request, organizing a work order and documenting field execution. The intent is a clearer journey for office teams and technicians.
FOCUS / FIELD OPERATIONSService requests, dispatch, technician activity and completion records need consistent states and practical, readable interfaces. The public product description emphasizes real operating conditions and the people doing the work.
DIRECTION / CLARITY OVER COMPLEXITYThe public project overview documents TypeScript/JavaScript-based workflows, web interfaces and SQL/PostgreSQL for structured operational data. It deliberately does not publish internal architecture or implementation details.
STACK / TYPESCRIPT · JAVASCRIPT · SQLThe proposed product journey is organized into four stages: prepare assignments, dispatch work, support field activity and collect completion evidence. Intermittent connectivity and traceable service completion are engineering goals, not guarantees.
JOURNEY / PLAN → DISPATCH → EXECUTE → COMPLETEAFServiceOPS is in development, and available features may change. The public cover used here comes from the official project overview; it is not a screenshot of a production deployment or real customer records.
STATUS / IN DEVELOPMENTA defined field-operations concept and its implementation direction: request intake, dispatch, technician work and service completion. Specific production readiness and feature availability are not guaranteed.
The visual above is the existing official public project cover—not a screenshot of customer data or a live deployment. No internal software files, addresses, credentials or sensitive operational information are shared.