Blog / Design · 7 min read ·
UI/UX basics every capstone system needs
Usability heuristics, accessibility, consistency, form design, mobile-first layout and five-user testing, applied to real Filipino capstone systems.
Panelists rarely fail a capstone because the colours are plain. They do mark teams down when the registrar cannot find the enrolment button, when a form loses everything after one wrong field, or when a barangay secretary needs help to finish a simple task. This guide covers the UI/UX basics that make a system usable, and how to show evidence of usability in your manuscript.
UI versus UX in a capstone
UI (user interface) is what users see and touch: layout, buttons, typography, form fields. UX (user experience) is whether they can finish their task quickly, correctly and without frustration. A polished screen with a confusing flow is good UI and poor UX. For a capstone, UX is what you must defend, because it ties directly to your objectives: faster processing, fewer errors, easier record retrieval.
Usability heuristics you can apply today
Jakob Nielsen's ten usability heuristics are a widely used checklist for reviewing interfaces. You do not need to memorise all ten to benefit. The table below shows six that matter most in records-heavy capstone systems, with concrete examples.
| Heuristic | What it means | Capstone example |
|---|---|---|
| Visibility of system status | Users always know what is happening | After a clinic patient is queued, show their number and how many are ahead of them |
| Match with the real world | Use the users' own words and order | Label it Cedula or Barangay clearance, not Document type 3 |
| User control and freedom | Easy undo and cancel | Let the cashier void a water bill payment entered in error, with a reason and an audit trail |
| Consistency and standards | Same action, same look, same place | The Save button sits at the bottom right of every form |
| Error prevention | Stop mistakes before they happen | Disable enrolment in a section that has reached capacity instead of showing an error afterwards |
| Recognition rather than recall | Show options instead of making users remember | A searchable dropdown of residents instead of typing a resident ID from memory |
A practical exercise: open each main screen of your prototype, go through the table, and write down every violation you find. Fix the cheap ones immediately. That list also becomes evidence for your design chapter.
Accessibility basics
Accessibility is not an extra feature. Government offices, health units and cooperatives serve senior citizens and persons with disabilities, and staff often work on old monitors in bright rooms. The Web Content Accessibility Guidelines (WCAG) give you concrete targets.
- Contrast. Body text needs a contrast ratio of at least 4.5:1 against its background; large text and interface components such as input borders need at least 3:1. Light grey text on white usually fails. Use a free contrast checker to confirm.
- Labels. Every input needs a visible label, not just placeholder text that disappears once the user starts typing. In HTML, connect each label to its field so screen readers announce it.
- Never colour alone. A red border is not enough to show an error. Add an icon or text such as
Requiredso users with colour vision deficiency can tell. - Keyboard access. Staff entering many records prefer the keyboard. Check that Tab moves through fields in a logical order and the focus outline is visible.
- Readable size. Use a base font size large enough for older users to read comfortably, and avoid long lines of text that stretch across a wide monitor.
- Touch targets. On mobile, make buttons large enough to tap reliably; the stricter WCAG guideline is at least 44 by 44 CSS pixels.
Consistency across screens
Capstone systems are often built by three or four people working on separate modules, and it shows: one module uses blue buttons, another uses green, a third puts Cancel on the right. Agree on a small set of rules before you build.
- One primary button style per screen, used for the main action only.
- The same date format everywhere, for example
2026-10-17or17 Oct 2026, never both. - The same words for the same thing: pick
ResidentorConstituent, not both. - A shared layout for list pages: search and filters at the top, table in the middle, pagination at the bottom.
- Shared components or a shared stylesheet, so a change happens in one place.
Designing forms that do not frustrate
Most capstone systems are mostly forms: enrolment, patient intake, loan application, meter reading entry. Good forms reduce encoding errors, which is often one of your stated objectives.
- 01
Ask only what you need
Every field costs time and is more personal data to protect. If a cooperative loan form does not use the applicant's religion, remove the field.
- 02
Group related fields
Split a long patient intake form into sections such as personal details, contact, and visit reason, or into short steps.
- 03
Use the right input type
Date pickers for dates, numeric keyboards for amounts and meter readings, dropdowns for fixed lists such as barangays or year levels.
- 04
Validate inline and kindly
Show the error next to the field as soon as the user leaves it, in plain words: "Enter an 11-digit mobile number starting with 09."
- 05
Never lose input
If saving fails, keep everything the user typed and highlight only the problem fields.
- 06
Confirm the result
After saving, show what happened and what to do next, such as printing the assessment form or returning to the list.
Designing mobile-first
Many of your end users, such as residents requesting a barangay certificate, students checking their schedule or concessionaires viewing a water bill, will open the system on a phone. Mobile-first means you design the smallest screen first, then expand the layout for tablets and desktops. It forces you to decide what matters on each screen.
- Put the main action within easy reach and keep secondary actions in a menu.
- Turn wide tables into stacked cards on small screens; a ten-column billing table cannot be read on a phone.
- Keep pages light. Compress images and avoid large libraries you do not need, since many users rely on prepaid mobile data.
- Test on a real low- to mid-range Android phone, not only in a desktop browser's device mode.
Staff-facing modules, such as a registrar's dashboard or a cashier's posting screen, may reasonably be desktop-first. State that decision and the reason in your design chapter.
Usability testing with five users
You do not need a large sample to find usability problems. A common recommendation from usability research is to test with about five representative users per round, fix what you learn, then test again. Small, repeated rounds find more problems than one large test at the end.
- 01
Pick real tasks
Write three to five tasks tied to your objectives, for example: "Register a walk-in patient and issue a queue number."
- 02
Recruit representative users
Test with actual intended users, such as health workers, registrar staff or cashiers, not your classmates.
- 03
Observe without helping
Ask users to think aloud. Note where they hesitate, make errors or ask for help. Do not explain the interface.
- 04
Measure three things
Record task completion, time on task and number of errors. A standard questionnaire such as the System Usability Scale can complement your observations.
- 05
Fix and repeat
Rank problems by severity, fix the worst, then run another round with new users.
Next step
Run a usability test with five users this week. Give each one a real task, watch without helping and note where they stop or ask for help. Map those stops back to the steps in your user journey map.