Web and backend contribution
- Worked on responsive interfaces using HTML, CSS, and Bootstrap.
- Built interactive behavior using JavaScript and jQuery.
- Worked with PHP CodeIgniter and MySQL around backend/data handling.
Arawinz / Early Product Foundation
I contributed to Engineering Sources Around You, a construction-industry platform for service providers, suppliers, engineers, workforce contacts, engineering information, trends, conversions, and careers.
Public
iOS/Android app
Construction
industry platform
Early
full-stack foundation
Mobile
app exposure
Context
This is the product and technical situation I was responding to, not just a list of tools.
ESAY serves the construction and engineering sector, where users need fast access to services, suppliers, engineers, workforce contacts, information, tools, and career resources.
This project matters in my story because it gave me early exposure to shipped software, domain-specific workflows, and the difference between making a page and contributing to a product.
System Map
I want each project page to show the system, not only describe it.
ESAY exists as a public construction and engineering app across mobile platforms, with Arawinz as the organization and ESAY as the product.
My Ownership
These are grouped by responsibility so the case study reads like real product ownership, not scattered bullet points.
Key Modules
Each module is a concrete proof point: product surface, backend, integration, workflow, or leadership responsibility.
ESAY gave users a practical way to find construction and engineering resources, contacts, information, trends, conversions, and career-related material.
I worked on UI implementation using HTML, CSS, Bootstrap, JavaScript, and jQuery, learning how product screens need structure, responsiveness, and clarity.
I worked with PHP CodeIgniter and MySQL, which helped me understand how frontend behavior depends on backend structure and data quality.
My involvement with the Dart/Flutter mobile app became an early bridge into cross-platform product thinking.
Hard Problems
This is where the case study becomes credible: what was difficult, and how I responded.
I focused on implementation discipline: responsive UI, interactive behavior, backend/data handling, and understanding the construction-industry context.
I learned to pay attention to domain workflows, terminology, and practical utility rather than just visual presentation.
Leadership
ESAY is not a leadership case study; it is an honest foundation case study. It shows where I started and how early shipped-product exposure shaped my later product ownership.
Lessons
Real products teach faster than isolated exercises.
Good engineering starts with understanding the domain and the user.
My later full-stack and AI work stands on this early foundation.
Stack
Next
My strongest work happens when I can move across product, engineering, integrations, and AI workflows with real responsibility.