Dự án thậtWeb AppNext.jseFootball

How I Built the eFootball Vietnam Ranking and Tournament System

November 12, 2026 4 min read 49 views
How I Built the eFootball Vietnam Ranking and Tournament System

efootball.com.vn is the national ranking of Vietnam's eFootball Mobile community, together with the whole tournament workflow. Here is how I built it.

#Start by listening

Before writing code I asked the admins to walk me through what they did by hand: how players signed up, who collected fees and how they were reconciled, where results were recorded and how ranking points were calculated. The most painful part turned out not to be the ranking but fees and results.

#Three design decisions

#1. Points expire

Points from a tournament count for 365 days after an admin approves the results, so the ranking reflects current form and newcomers can climb. Each tournament stores a snapshot of its point table, so later rule changes never disturb old results.

#2. A unique transfer code per player

On registration the site generates a VietQR code with the exact amount and a unique transfer note. Organizers search their bank statement for that note and confirm. No bank integration, no fees, and reconciliation is far quicker than reading a statement line by line. After a real tournament where someone paid during the semi-finals, I added a rule: when registration closes, unconfirmed entries are removed automatically.

#3. Players report, the site referees

After a match one side reports the score with a screenshot; the other confirms or disputes. Overdue matches are approved automatically, so organizers only handle disputes.

#Engineering

  • Front end: Next.js 15 and Tailwind, with public pages pre-rendered and refreshed when data changes.

  • Back end: Express and MongoDB; the ranking is one cached aggregation, invalidated the moment results are approved.

  • No overbooking: registration counts are incremented atomically.

  • Vietnamese–English, Google sign-in, Excel exports.
  • #Testing

    Screens were captured automatically on 21 device sizes, from a 320px Android phone to a 2K monitor. Every feature touching money or points has its own test scenario.

    #Lessons

  • Ask about the process before the features.

  • Anything involving money needs an audit log.

  • Automation needs a manual way out.

  • Ship early and fix from real feedback.
  • More on the eFootball Vietnam project page. Need a similar system for tournaments, memberships or bookings? Get in touch.

    Share: