Deployment - lesson 6 | HackIndia Skills

Key point

One final check

A live URL is not enough. Your project should open cleanly from a custom domain if you use one, and it must work on a phone.

Recruiters and judges may open your link on mobile data between meetings. Make the first screen load, fit, and explain the project fast.

Domain basics

A custom domain is optional for many hackathon submissions, but it looks cleaner than a long platform URL. You can use your host URL if you do not own a domain.

If you use a domain, connect it from your hosting dashboard first. Then update DNS records in your domain provider. DNS changes can take time, so do this before the deadline day.

Your to-do

Connect the domain

Do each one yourself, then tap it to tick it off. The ticks are only a checklist for you: they are not marked or scored.

Open your hosting project dashboard and find Domains or Custom Domains.
Add your domain, such as yourproject.in or app.yourdomain.com.
Copy the DNS record values shown by the host.
Open your domain provider DNS settings and add the required records.
Wait for the host to show Verified, then open the domain in a private browser tab.

0 of 5 done

Example

DNS record example

Your host will give the exact values. Do not guess them. The pattern often looks like this.

Type: CNAME
Name: www
Value: your-project.vercel.app

Type: A
Name: @
Value: 76.76.21.21

Common mistake

Common DNS mistake

Do not add random DNS records from a tutorial for a different host. Netlify, Vercel, Render, Railway, and other hosts may ask for different records.

Also avoid changing nameservers unless your host or domain provider specifically tells you to. Wrong nameserver changes can break email or other subdomains.

Your to-do

Check on phone

Do each one yourself, then tap it to tick it off. The ticks are only a checklist for you: they are not marked or scored.

Open the live URL on your own phone using mobile data, not college Wi-Fi only.
Test the main user flow, such as login, search, upload, checkout, or form submit.
Rotate the phone once and check that the layout does not break.
Tap every button on the first screen and check that touch targets are easy to hit.
Share the URL with one friend on Android and ask them to send a screenshot.

0 of 5 done

Tip

Use AI for review

Take two screenshots: desktop and phone. Ask an AI tool to review layout, clarity, and mobile usability. Treat the answer as a checklist, not truth.

Check what it suggests. AI may miss broken buttons, slow loading, auth issues, or database errors. You still need to test the real app yourself.

Prompt:
Review these screenshots of my deployed project.
Tell me only the mobile issues that could hurt a hackathon submission.
Check: first-screen clarity, text size, button size, overflow, and confusing navigation.

Your to-do

Do this now

Do each one yourself, then tap it to tick it off. The ticks are only a checklist for you: they are not marked or scored.

Decide whether you will submit a custom domain or your host URL.
If using a domain, add it in your host and update DNS records from the host instructions.
Open the final URL on your phone using mobile data.
Run the main user flow and fix any broken layout or button.
Save one phone screenshot for your README or final submission notes.

0 of 5 done

Add domain and phone checks

One final check

Domain basics

Connect the domain

DNS record example

Common DNS mistake

Check on phone

Use AI for review

Do this now

Quick check