The common thread in my current work is not only education or transport. It is reliability under imperfect conditions.
When software assumes perfect connectivity, unlimited devices, low workload, and predictable users, it becomes fragile in the exact environments where it is supposed to help. That has shaped how I think about GotchaEducation and NavigoTransport.
Education Needs Context
GotchaEducation started from assessment integrity, but the stronger lesson was that education software has to respect the full learner and teacher workflow. Exams matter, but so do attendance, progress, parent reporting, service records, low-data access, support, and the amount of admin a teacher can realistically handle.
That is why the company direction is now broader than proctoring. The products are still technical, but the design target is practical institutional use.
Transport Needs Local Computation
NavigoTransport has the same engineering pattern in a different domain. Campus transit is only useful if the app still helps while a student is moving through buildings, underground spaces, weak signal zones, and changing schedules.
On-device journey planning, offline timetables, reminders, and simple safety flows are not decorative features. They are the product.
What I Want This Portfolio To Show
The portfolio should make claims easy to verify. Each item needs a date, a role, a short explanation, and proof when public proof exists. When proof is not public yet, the site should say that clearly instead of hiding the gap.
That is the same design principle I try to use in products: make the important state visible.