homigo

I built the consumer request experience from the initial ZIP-code entry through service selection, job details, location, and scheduling. I organized these inputs into separate, focused screens, followed by an account step, submission, and confirmation.

I implemented validation and controlled navigation between steps so required information was collected before users continued. I also built a dedicated screen for ZIP codes outside the service area, making that limitation visible during the request journey.

This structure gave homeowners a clear sequence for describing a job. Each screen focused on the information needed at that point, while the confirmation screen marked the end of the submission process.

I built provider registration, guided business-information forms, service selection, and provider portal UI. The forms collected what a provider offers and where they work, using service categories, ZIP codes, and travel radius to describe their coverage.

I connected the frontend steps to backend APIs for account, verification, and payout services. I built English/Spanish interfaces for the onboarding experience, which included 20 service categories.

These forms established the provider information a local marketplace needs: the business, the services available, and the area it serves. My work connected that setup process to the provider’s account experience.

I implemented the backend contact-form API and its SendGrid email integration. Visitors could enter their contact details and message on the website, and my integration connected that submission to email delivery.

The form sent the submitted information to the backend. The contact-form API processed the request and passed the message to SendGrid for delivery. I built the connection between the user-facing form and the email service, carrying the inquiry through the application beyond the submit button.

This gave visitors a direct way to ask questions or raise an issue through the website. Their contact information and message provided the context needed for a response, making the contact page a functioning communication channel for the marketplace.

I implemented uploaded-image moderation using Google Cloud Vision. I connected the image-handling workflow to content analysis so the application could identify potentially inappropriate imagery in user uploads.

Photos are useful in a home-services request: a homeowner can show the condition of a space, an item that needs repair, or the scope of a job. A provider can use that visual context to understand the request. That makes uploaded images part of the interaction between consumers and providers.

My integration introduced a content-screening step into that workflow. An uploaded image could be analyzed through Google Cloud Vision, and the resulting assessment provided information for moderation. This gave the application a way to identify content concerns as part of handling an upload.

The goal was to prevent inappropriate imagery from reaching other users while retaining the value of job-related photos. For a marketplace connecting people who may not know each other, screening shared content is part of maintaining a professional environment and trust in the service.

I also implemented a profanity filter to screen user-entered text for offensive language. This addressed the written content users submitted alongside the image-moderation functionality.

Written information needs to communicate a service need clearly and respectfully. The filter added a check for inappropriate wording, with the goal of keeping offensive language out of the content shared through the marketplace. Together, text filtering and image moderation addressed both forms of user-submitted content.

I built responsive layouts and English/Spanish interfaces across consumer requests and provider onboarding. My work covered the forms, navigation, and page layouts users interacted with while setting up an account or describing a service request.

These workflows required users to enter several kinds of information. I organized the layouts around those tasks so the steps remained readable and usable on phones, tablets, and desktops.