How I Built a Lost and Found Website for a Final Year Project (Without Prior Experience)

In 2022, one of the most valuable projects I’ve worked on was a Lost and Found platform built for a student’s final year project.

Not because it was flashy.
But because I had never built anything like it before.

This project reinforced a lesson I keep relearning:
real growth happens when you build things you don’t already know how to build.

The Starting Point: No Template, No Blueprint

My first instinct was simple—look for an existing template.

I searched ThemeForest for a ready-made Lost and Found solution.
Nothing fit the exact use case.

There were generic listing themes, but nothing tailored to how a proper Lost and Found system should work.

So instead of forcing a template, I did something more important:

I studied existing Lost and Found listing websites.

Not to copy design—but to understand how the system works.

Step One: Understand the Problem Before the Tools

Before touching WordPress, I broke the idea down into simple logic.

Here’s how the platform needed to work:

1. A user creates an account on the website
2. The user can submit:
   • a lost item
   • or a found item
3. Each submission includes:
   • item description
   • location
   • contact details
4. All submitted items are listed publicly on the platform
5. Other users can browse the listings and reach out using the provided contact details

Once I understood this flow, the build stopped feeling complex.

It became a set of small, solvable problems.

Figuring It Out with WordPress (Learning as I Built)

I already knew WordPress—but this project pushed me beyond basic site building.

To make it work, I had to learn:

• how to handle user accounts properly
• how users can submit content from the frontend
• how to structure listings in a clean, logical way

I relied heavily on YouTube tutorials to learn some custom WordPress development concepts while building.

Not watching everything first.
Learning exactly what I needed, when I needed it.

This wasn’t about becoming a WordPress expert overnight.
It was about learning just enough to move forward.

From Website to Mobile App

The original plan was always bigger than just a website.

At the end of the project, I converted the platform into a mobile app.

Instead of rebuilding everything natively, I used a service that wraps a website into an Android application.

This allowed the student to:

• present both a web platform and a mobile app
• meet project requirements without overengineering

It wasn’t perfect—but it was practical, functional, and deliverable.

And that mattered more.

Key Takeaways from This Project

This project reminded me of a few important truths:

1. You don’t need to have built it before to build it well:
   You need the willingness to figure it out.
2. Understanding the problem comes before choosing tools:
   Once the logic is clear, the technical decisions become easier.
3. Learning while building is a real skill:
   YouTube wasn’t a shortcut—it was a tool used intentionally.
4. Practical solutions beat perfect ones:
   Converting the website to a mobile app was simple, but effective.

Final Thoughts

This wasn’t my most complex project.
But it was one of the most formative.

It taught me that confidence in building doesn’t come from knowing everything—it comes from trusting your ability to learn, adapt, and execute.

And that mindset has shaped how I approach every product since.

I think in systems, trade-offs, and execution.
Building digital products in public.