Epplof Events
Discover events happening in Uyo, Akwa Ibom

About the Project
Epplof Events is a web-based event discovery, creation, and management platform built to solve one simple but painful problem in Nigeria and across many growing communities: finding out about events is hard, and organizing them is even harder.
The project lives at epplofevents.infinityfreeapp.com and it is designed for three main groups of people. The first group is everyday event lovers — students, young professionals, church members, party lovers, and community members in places like Uyo, Warri, Asaba, Lagos, and beyond who want to know what is happening around them this weekend without having to scroll through hundreds of WhatsApp statuses, Instagram stories, or flyers that get lost in group chats. The second group is event organizers — DJs, promoters, church media teams, school fellowship leaders, small business owners, wedding planners, and party organizers who need a simple, free, and reliable place to publish their event, collect interest, and manage their audience without paying expensive platform fees or learning how to code. The third group is vendors and community builders who want visibility — photographers, MCs, caterers, decorators, and ushers who can discover events where their services are needed.
What does it do? At its core, Epplof Events allows any user to browse upcoming events by category, date, and location. A user can open the homepage, see a clean list of featured events with images, dates, venues, and ticket or entry information, click into an event to read full details, and then take action — RSVP, register, save the event, or share the link with friends. For organizers, the platform provides a dashboard where they can create a new event in minutes, upload a banner or flyer, add a description, set the date, time, venue, category, and capacity, and publish it instantly. Once published, the event becomes discoverable to everyone visiting the site. The organizer can then edit the event if details change, monitor how many people are interested, and manage the event from one place.
The platform was built with accessibility in mind. It works on low-end Android phones, loads fast on 4G and even on slow 3G networks.
Beyond discovery, Epplof Events is also a learning and portfolio project that demonstrates real-world full-stack web development. It shows how a simple idea — “let people find events near them” — can be turned into a working product with user accounts, database storage, form validation, image uploads, search, and admin controls. It matters because events are not just entertainment in Nigeria — they are how communities connect, how small businesses get customers, how churches grow, how artists get discovered, and how young people build networks. By making event discovery easier, the platform helps organizers reach more people, helps attendees waste less time searching, and helps local economies grow because more people show up to local events.
In short, Epplof Events is not just a website. It is a community tool, a business tool, and a technical proof that a single developer with limited resources can build a product that solves a real local problem and can scale to serve a wider audience if given the right support and infrastructure.
The Challenge
The problem that led to Eppl of Events came from personal frustration and observation of how events are currently shared and managed in Nigeria, especially outside Lagos and Abuja.
Before this project, if you wanted to know what events were happening in your town, you had to rely on fragmented, unreliable channels. The most common method is WhatsApp. Someone posts a flyer in a group, it gets buried under 200 other messages within an hour, and by the time you see it, the event has already passed. The second method is Instagram or Facebook stories — they disappear in 24 hours, and if you do not follow the right person at the right time, you miss it. The third method is physical flyers and word of mouth — someone tells you “there is a party on Saturday” but you do not know the exact venue, time, or whether you need to pay. The fourth method is church announcements or school notice boards, which only reach people who are already inside that community.
For organizers, the problem is even worse. A small organizer in Ughelli who wants to host a concert, a birthday party, a church program, a tech meetup, or a graduation party has no affordable platform to promote it. Eventbrite and other international platforms are expensive, require dollar payments, and are not designed for local Nigerian events. Creating a poster and posting it on WhatsApp is free, but it is not searchable, it cannot be updated easily, and there is no central place where interested people can register or ask questions. If the venue changes or the time shifts, the organizer has to send the update to 10 different groups and hope everyone sees it. There is also no way to track who is coming, so organizers either over-prepare and waste money on food and drinks, or under-prepare and run out.
Another challenge is trust and information. Many people have been scammed by fake event flyers or have gone to a venue only to discover the event was cancelled. There is no single source of truth. Attendees also struggle with planning — they want to know if an event is free or paid, if it is family-friendly, if it is for students or for adults, and what to expect. Without structured information, they have to message the organizer one by one, which wastes time for both sides.
From a technical and academic perspective, the challenge was also about building something real with limited resources. The project had to be built on free hosting (InfinityFree), with no budget for paid APIs, no team, and no access to premium tools. It had to work on slow internet, handle image uploads safely, prevent broken links, and still look professional. The assignment required not just a static landing page, but a functional application where users could actually interact — create accounts, create events, view events, and manage data. That meant solving database design, session management, form validation, security basics like password handling, and responsive design all at once.
Finally, there was the challenge of user adoption. People in Nigeria are used to WhatsApp and Instagram. Convincing them to try a new website required making the site feel familiar, simple, and fast. If it took more than 3 clicks to find an event, users would leave. If the design looked like a school project, organizers would not trust it. So the challenge was not just technical — it was about designing for real human behaviour, local context, and low-data environments.
Epplof Events was created to solve all of these problems in one place: one link, one search, one dashboard, one source of truth for events.
The Solution
To solve the problem, I approached Epplof Events as a product, not just as a school project. I started by asking: “If I was an organizer in Uyo, what would I need in 2 minutes?” and “If I was an attendee, what would make me stay on the site for more than 10 seconds?” The answers shaped every decision.
First, I mapped out the user journey. An attendee should land on the homepage, immediately see upcoming events with pictures, dates, and locations, and be able to click into any event without needing to create an account first. An organizer should be able to sign up, log in, and create an event in under 5 minutes without reading a manual. An admin should be able to manage users and events, remove spam, and keep the platform clean. This journey became the blueprint for the site structure.
Second, I chose a stack that was free, reliable, and easy to deploy for a Nigerian context. The frontend uses HTML, CSS, and JavaScript with a mobile-first responsive layout so it works on phones, tablets, and desktops. The backend uses PHP and MySQL, which are supported by InfinityFree hosting and are widely used for real-world small-to-medium web applications. This choice meant I could build, test, and deploy without paying for hosting, while still learning industry-standard concepts like CRUD operations, sessions, and database relationships.
Third, I designed the database to reflect real events. I created tables for users, events, and categories. Each event stores the title, description, banner image, date, time, venue, location, category, organizer ID, creation date, and status. Each user stores the name, email, hashed password, role (user, organizer, admin), and registration date. This structure allows the site to show events in order of date, filter by category, and show “My Events” for each organizer without mixing data.
Fourth, I built the core pages step by step. The homepage is the discovery hub — it shows featured and upcoming events in cards, with a search bar and category filters. The event details page shows the full flyer, description, venue, map link, date, and organizer info, plus an RSVP or interest button. The authentication pages handle user registration and login with validation and error messages. The organizer dashboard allows users to create, edit, and delete their own events, upload images, and see their events in one place. The admin area allows moderation.
Fifth, I focused on user experience details that many student projects ignore. I added form validation so users cannot submit an event without a date or venue. I added image upload handling with size checks and fallback images if an upload fails. I added responsive navigation with a hamburger menu for mobile, so users do not have to pinch and zoom. I added clear success and error messages — for example, “Event created successfully” — so users know what happened. I added a simple, clean colour scheme that feels like an event brand, not a plain template.
Finally, I tested the solution in real conditions. I tested it on my phone with mobile data, on a laptop with WiFi, and I asked friends to try creating an event and finding it. Their feedback led to improvements: I made the “Create Event” button bigger and more visible, I simplified the form from 12 fields to the most important ones, and I added clearer category labels like “Party, Church, Concert, Tech, School, Wedding” instead of generic labels.
The result is a working, deployable platform that an organizer can actually use today. It is not a mockup or a Figma design — it is a live site at epplofevents.infinityfreeapp.com where data is stored, users can log in, and events can be created and discovered. That is the solution: one central, free, mobile-friendly place for events.
Key Features
- User can place an order.
- User can drop a review.
- User can view gallery and check out for beautiful setups
Student Contribution
I was the sole designer, developer, and tester for Epplof Events, which means I personally handled every stage of the project from idea to deployment. There was no team to split the work with, so my contribution covers product thinking, design, coding, database management, testing, and deployment.
My first contribution was product research and planning. Before writing any code, I interviewed friends, church members, and small organizers in my community to understand how they currently share events. I asked them what frustrates them about WhatsApp flyers, what they wish existed, and what would make them use a new platform. Those conversations shaped the features — for example, people told me they wanted to see the date and venue without clicking too much, so I made sure event cards show date, venue, and category upfront. I also created wireframes on paper and then in my editor, mapping out the homepage, event details page, login page, and dashboard before I built them.
My second contribution was frontend design and development. I designed the entire user interface using HTML, CSS, and JavaScript. I chose the colour palette, typography, and layout to make the site feel like a modern event brand — bold, energetic, but still readable. I built the responsive navigation, the event cards, the search bar, the category filters, and the forms. I made sure the site works on mobile first, because I knew most users in Nigeria would access it from phones. I tested the design on different screen sizes and fixed issues like text overlapping, images stretching, and buttons being too small to tap.
My third contribution was backend development and database design. I wrote the PHP code that powers user registration, login, logout, event creation, event editing, event deletion, and event listing. I designed the MySQL database schema, created the tables, and wrote the queries that connect the frontend to the data. I implemented session management so that only logged-in users can create events, and only the owner of an event can edit or delete it. I also added basic security measures — input validation, sanitization, and password hashing — to protect user data and prevent common attacks like broken forms or SQL injection attempts.
My fourth contribution was content, testing, and deployment. I created sample events to test the platform, uploaded test images, and tried to break the site on purpose to find bugs — for example, submitting an event without a date, uploading a very large image, or trying to access the dashboard without logging in. I fixed each bug I found. I then deployed the project to InfinityFree, configured the database on the live server, uploaded the files, and tested the live URL at epplofevents.infinityfreeapp.com to make sure it worked outside my laptop. I also wrote the copy for the homepage, the about text, and the help messages.
My final contribution was documentation and iteration. I documented the project structure, explained how each feature works, and prepared this case study to explain the project to others. I also collected feedback from early users and made improvements based on it — simplifying the create-event form, making the create button more visible, and improving the mobile layout.
In summary, my contribution was not just “I coded it.” I thought about the problem, designed for real users, built the full product, tested it, deployed it, and improved it. That end-to-end ownership is what I am most proud of, and it is the skill I want to carry into future projects, internships, and client work.




