Built to order

Daily Wage Job Finder Android App

This project is an Android app that connects daily-wage workers with nearby work — construction help, loading, painting, farm labour, shop help and security shifts posted by verified local contractors. Workers browse today's listings with daily wage, timing and distance on every card, filter by work type, open a detail page with requirements, and apply in one tap; a tracking screen shows application status from "applied" to "accepted". Suitable for B.E./B.Tech final-year projects in Computer Science, IT and mobile computing.

Daily Wage Job Finder Android App — project thumbnail preview
More project photos (2)

The problem

Millions of daily-wage workers find work through labor chowks and word of mouth — showing up at dawn hoping a contractor needs hands that day. No work means no pay, and there is no record of wages promised versus wages paid. General job portals ignore this segment entirely: they assume resumes, email IDs and English fluency. This project builds a job finder designed for how daily-wage work actually happens: hyperlocal listings (within a few km), daily wage stated upfront on every card, timing and distance visible before tapping, one-tap apply with no resume, and application tracking so the worker knows whether the contractor responded. Contractor verification badges and ratings add a layer of trust to an informal market. The demo ships with realistic listings across six work categories, a full job-detail flow with requirements, and an applications screen showing accepted and pending states.

How it works

  1. The home feed loads today's listings near the worker's location, each card showing work title, contractor, wage, timing and distance.
  2. Filter chips narrow the feed by work category; the list re-renders instantly.
  3. Tapping a card opens the detail screen: full requirements, contractor verification status and rating, wage, timing and distance.
  4. The Apply button sends the application to the contractor (demo: recorded locally with a pending status).
  5. The confirmation screen explains what happens next — contractor response within ~2 hours via SMS and app notification.
  6. The Applications tab lists every application with its current status, accepted ones showing start time.

Tech stack:

  • Android (Kotlin) — native app target
  • MVVM architecture
  • REST API design (listings, applications, contractors)
  • Location services (distance sorting)
  • Push notifications + SMS fallback (status updates)
Parameter Value
Screens 4 (feed, job detail, confirmation, applications)
Work categories 6 (Construction, Painting, Loading, Farm, Shop, Security)
Demo listings 6 realistic postings with wages ₹500–800/day
Apply flow One tap, no resume
Languages English + Hindi/Marathi cues (design target)
Target Android 8.0 (API 26) and above (design target)
Backend REST API design included; demo runs on local data

Project features

  • [Hyperlocal job feed] Listings sorted by distance with wage, timing and distance on every card — the three facts a worker needs before anything else.
  • [Work-type filters] One-tap chips for Construction, Painting, Loading, Farm, Shop and Security filter the feed instantly.
  • [Upfront daily wage] Every listing states the per-day wage prominently; no "salary discussed later" listings allowed by design.
  • [Job detail pages] Requirements list, contractor name with verification badge and rating, exact timing, and distance from the worker.
  • [One-tap apply] No resume, no cover letter — a single tap sends the application; the contractor typically responds within hours.
  • [Application tracking] Applied, accepted and pending states with plain-language status lines ("Accepted · starts tomorrow 5 PM").
  • [Multilingual cues] Hindi/Marathi labels alongside English ("रोज़गार · Rozgar") and large touch targets for first-time smartphone users.

What is included

  • Complete Android app source code (Kotlin)
  • REST API design document (listings, applications, contractor verification)
  • App icon and graphic assets
  • Project report PDF (background, inclusive UX design, matching flow, methodology)
  • PPT presentation for final review
  • Viva Q&A preparation document (Android, location services, multilingual UI, trust design)

Limitations & prerequisites

  • The demo runs on local data; live contractor postings and real applications need the backend, whose API is designed and documented but not hosted.
  • Contractor verification in production needs a real KYC process — the demo shows the badge UI, not a verification pipeline.
  • Wage-payment disputes and escrow are out of scope; the app connects worker and contractor but does not process payments in this version.
  • Location accuracy depends on the phone's GPS; distance figures in the demo are illustrative.
  • Chat between worker and contractor is designed but not implemented — status updates go via SMS/push in the current scope.

Frequently Asked Questions

Who is this app actually for?

Daily-wage workers — construction helpers, loaders, painters, farm labour — who today depend on labor chowks and middlemen. The whole UX (big buttons, upfront wages, Hindi/Marathi cues) is designed for first-time smartphone users.

How do workers apply without a resume?

They don't need one. Contractors hiring daily-wage help care about availability and proximity, not CVs — so applying is one tap, and the contractor sees the worker's profile with past ratings.

How is contractor fraud handled?

The design includes contractor verification badges, public ratings from workers, and wage-upfront rules. Real KYC integration is specified as the production step.

Does the app take a commission?

The project scope keeps the marketplace free for workers; the monetization model (contractor posting plans) is discussed in the report's future-scope section, not implemented.

What about workers without smartphones?

The design includes SMS fallback for application status, so a worker with a feature phone still gets "accepted" messages. Full app features need Android.

Is this project suitable for a final-year project?

Yes — for Computer Science, IT and mobile-development programs. It demonstrates inclusive UX design, location-based listing, application state tracking and a socially meaningful problem. Suitable for B.E./B.Tech final-year projects in Computer Science, Information Technology and Mobile Application Development.

Components & software requirements
  • Android (Kotlin) — native app target
  • MVVM architecture
  • REST API design (listings, applications, contractors)
  • Location services (distance sorting)
  • Push notifications + SMS fallback (status updates)
Delivery information

Built-to-order project. Delivery timeline is shared after order confirmation based on current queue.

Support terms

Complete documentation, setup guide, and viva preparation included. Support for setup and explanation provided.

Download abstract (PDF)

Related guides

All guides
Blueprint-style technical illustration of a smartphone with a shield badge, surrounded by camera, photo and location icons connected by circuit traces.Android development students whose apps use the camera, photos, location or notifications and who need their projects to work correctly on current Android versions.

Android Runtime Permissions in 2026: Photo Picker, Partial Access and Foreground Services

Android's permission model has changed in nearly every recent release, and old tutorials now fail silently on modern phones. This guide covers the current model: runtime request flow, the no-permission photo picker, Android 14 partial media access, notification permission, and foreground-service types — with a migration checklist for older student apps.

Read guide
Illustration of an Android phone with background task scheduling diagram showing workers, constraints, and periodic sync arrows.B.E./B.Tech Computer Science and IT students building Android apps that need reliable background work for academic and final-year projects

WorkManager for Background Tasks

Background sync that dies overnight? Learn WorkManager: the right API for guaranteed background work on modern Android. Covers one-time and periodic requests, constraints, chaining, retry/backoff, passing data, observing from UI, and debugging workers delayed by Doze or OEM battery optimizers.

Read guide
Illustration of a smartphone showing a Jetpack Compose UI with composable function blocks and state flow arrows connecting them.B.E./B.Tech Computer Science and IT students building Android apps for academic and final-year projects

Jetpack Compose Basics for Students

Learn Jetpack Compose from zero: the declarative UI mental model (UI as a function of state), composable function rules, state management with remember and hoisting, Column/Row/Box/LazyColumn layouts, Material 3 theming, navigation, and the mistakes every beginner makes.

Read guide
Get a quotation