Frontend to database
Flutter interface, Laravel API and PostgreSQL schema designed together, not handed between teams.
RGOpen to software development opportunities
Namaste, I am
Flutter & Full-Stack Developer
I build modern mobile, web and desktop applications using Flutter, Dart, Laravel and PostgreSQL, with a focus on practical solutions for education, business and everyday workflows.
Flutter interface, Laravel API and PostgreSQL schema designed together, not handed between teams.
Authentication, roles, admin panels, reports, exports and printing — the parts that decide whether software is usable at work.
Fingerprint attendance hardware, receipt printers and third-party integrations handled as part of the build.
01 — About
I build complete applications — interface, API, database and deployment — rather than isolated screens.
RGI am a BSc.CSIT graduate who builds complete applications — the mobile or web interface, the Laravel API behind it, the PostgreSQL schema underneath, and the deployment that puts it live. Working across the whole stack is not a side note for me; it is the job.
Most of my work sits where software has to fit a real organisation: school management platforms, an election system that replaced spreadsheet workflows, restaurant POS tooling, and a devotional and learning application for children. Each one asks for authentication, roles, reporting, exports and hardware or printing integration — not just screens.
I have taught Grade 11 and Grade 12 at Hetauda City College for around two years, which sharpened how I explain technical ideas to people who are not developers. That instinct carries into how I design software: clear flows, understandable language, and interfaces that a non-technical user can use without help.
Flutter interface, Laravel API and PostgreSQL schema designed together, not handed between teams.
Authentication, roles, admin panels, reports, exports and printing — the parts that decide whether software is usable at work.
Fingerprint attendance hardware, receipt printers and third-party integrations handled as part of the build.
Selected work
Real applications — Flutter interfaces, Laravel APIs, PostgreSQL databases — shipped end to end.
A school-focused digital platform that pulls timetable, bell, attendance, ID cards, exam seating and elections into one multi-module application.
A centralised digital election platform that replaces spreadsheet-based school elections, with multi-school administration, audit logs and a login-free student voting interface.
A devotional and educational application for children, combining bhajan and story content with Gita shlokas, a Rashifal calendar, and a set of playable games behind a parent gate.
A restaurant POS application covering tenant setup, order and item management, takeaway orders, and batched receipt printing with multiple copies.
A digital learning platform concept for Class 9 and 10 students, with subject-based notes and past questions served as backend-uploaded images.
By the numbers
Real facts, no padding — what I have actually built and shipped.
Flutter, Dart, Laravel and PostgreSQL since student days.
School management, election systems, restaurant POS, devotional apps.
02 — Skills
The technologies I use to build, and what each one is actually used for in the work.
One Flutter codebase serving mobile, web and desktop.
Primary framework for the applications in this portfolio, used across Android, web and desktop.
The language behind every Flutter application I build.
Web targets for admin panels and public-facing interfaces, such as the election voting flow.
Android-first application delivery with a consistent navigation structure.
Desktop builds for tools used in a fixed working environment.
Riverpod for application state and clear data flow between UI and API.
Layouts designed from mobile upward, with breakpoints at tablet and desktop.
Typed client layers, loading and error states, and offline-tolerant screens.
APIs, access control and the business rules underneath them.
Backend framework for the API layer behind these applications, including multi-school scoping.
Server-side language used with Laravel for API and administration work.
Structured, versioned endpoints with consistent response shapes.
Login flows, sessions and tokens, including no-login flows designed deliberately.
Super Admin, School Admin and staff roles enforced on the server, not just hidden in the UI.
Back-office interfaces for configuration, records, reporting and elections.
Module boundaries, data flow between Flutter, Laravel and PostgreSQL, and integration points.
Relational design that survives real data volumes and rules.
Primary database for these systems, including the hosted Supabase migration.
Used during local development on XAMPP environments before PostgreSQL adoption.
Modelling shared entities once — a student or restaurant defined a single time and reused.
Version-controlled schema changes so deployments are repeatable.
Normalised structures for attendance, votes, orders and elections, with integrity rules enforced in the database.
The day-to-day engineering work around features.
Branching and history for work shared between client and server.
Repository hosting and code review workflow.
API payload handling and content exchange between layers.
Tracing problems across the stack — device behaviour, API responses and database state.
Choosing module boundaries and deciding where logic belongs before writing features.
Wiring external services into an application without letting them leak into the UI.
Getting the finished system running on a real domain.
Shipping applications and this portfolio to production hosting.
Hosting environments configured for a PHP and Laravel backend.
Hosted PostgreSQL for moving projects off a local development machine.
Configuration kept outside the codebase, so the same build runs in development and production.
Pointing a custom domain at the deployed application.
Standalone deployment of the API layer the applications depend on.
Diagnosing issues that only appear once real devices, data volumes and networks are involved.
03 — Projects
Real applications built end to end — interface, API, database and deployment. Each case study explains the problem, the architecture and what I actually built.
School / Education Management Platform
A school-focused digital platform that pulls timetable, bell, attendance, ID cards, exam seating and elections into one multi-module application.
Education Technology / Voting System
A centralised digital election platform that replaces spreadsheet-based school elections, with multi-school administration, audit logs and a login-free student voting interface.
Kids / Devotional / Content Application
A devotional and educational application for children, combining bhajan and story content with Gita shlokas, a Rashifal calendar, and a set of playable games behind a parent gate.
Restaurant POS / Business Software
A restaurant POS application covering tenant setup, order and item management, takeaway orders, and batched receipt printing with multiple copies.
Education / Digital Learning
A digital learning platform concept for Class 9 and 10 students, with subject-based notes and past questions served as backend-uploaded images.
04 — Experience
A path from school-time teaching and an internship, through Flutter application development across education, restaurant and devotional domains, into full-stack work I ship and support.
Virtual Tribes
Worked as a Flutter Developer Intern, building client-side applications and integrations in Dart. Part of this work involved a Nepali Calendar application, which required careful handling of date logic and localisation rather than relying on defaults.
Hetauda City College
Hetauda, Nepal
Taught Grade 11 and Grade 12 for around two years. Teaching computer science to senior students meant breaking down programming and technical concepts until they were genuinely understandable, which changed how I design software for non-technical users.
Bal Jagriti English Secondary School
Hetauda-2, Basudev Marga, Nepal
A foundational part of my professional journey, grounded in working directly with a school community and real-world school operations — exposure to education systems, technology and practical problem solving.
Sarbatra Inc.
Professional software development across mobile, desktop and web from a single Flutter/Dart codebase, backed by a Laravel API and PostgreSQL database. I build API-driven applications, integrate hardware and external services, implement UI/UX, and handle debugging, maintenance and production deployment.
KutumbaTech
Interned as a Flutter developer, building mobile features against an existing production codebase and API layer. Worked with the KutumbaTech restaurant API and Swagger-based API documentation.
05 — Education
Computer Science and Information Technology
Undergraduate studies covering programming, databases, software engineering and web technologies — the foundation behind the application and backend work in this portfolio.
06 — Services
Seven areas of work, all covering the full path from interface to deployed system.
Modern Android, iOS, Web and Desktop applications from a single Flutter codebase.
Flutter frontend, Laravel backend and PostgreSQL database, built as one system.
Secure and structured API development and integration.
POS, management systems, dashboards and workflow applications.
School management, attendance, election, learning and administrative systems.
Database design, migrations, authentication and backend architecture.
Fixing, improving and extending existing Flutter and Laravel applications.
Most real projects combine several of these. Describe the problem you are trying to solve and I will tell you how I would approach it.
07 — How I Work
The same sequence on every project, from the first conversation through to a maintained deployment.
Start with what the business or school actually needs to happen, not with a feature list. Most of the difficult requirements in education and POS software come from how an organisation really operates.
Decide module boundaries, where logic belongs and how data flows between the client, the API and the database — before writing features, so the structure is not retrofitted later.
Design the screens a non-technical user will actually touch: clear flows, plain language, and the shortest sensible path through each task.
Build the Flutter application with deliberate state management, responsive layout and honest loading, empty and error states.
Implement the Laravel API with authentication, role-based access and business rules enforced on the server rather than trusted to the client.
Design the PostgreSQL schema, write migrations, and keep integrity rules in the database rather than relying on the application to behave.
Test across the whole path — UI, API and database — and trace failures to their actual layer instead of patching the symptom.
Configure the environment, deploy, connect the domain and handle the production issues that only appear with real users and devices.
08 — Architecture
Frontend work is only one layer. This is the path a feature travels from a Flutter widget down to a running server — and the hardware and third-party services it may touch on the way.
The stack
Flutter
Application UI across mobile, web and desktop
State Management / UI
Riverpod state, navigation and interaction logic
REST API
Typed requests, response handling and error states
Laravel
Business rules, authentication, roles and modules
PostgreSQL
Schema, migrations, integrity and reporting queries
Deployment
Environment configuration, hosting, domain and HTTPS
Fingerprint attendance devices on real school hardware
Receipt batches and ID card output
Password, token and Google sign-in flows
Hosted PostgreSQL through Supabase
Content delivery, sign-in and advertising services
One codebase, several targets
When one person owns the whole path, there is no gap between what the database can express and what the interface can show. Data constraints, permission rules and validation get decided once and applied everywhere, instead of being rediscovered at every layer.
My repositories cover the Flutter work I am proud to publish, along with the Laravel and database work behind it.
10 — FAQ
Straight answers about how I work and what I build.
I personally architect and build every project I take on. I work across the full stack — Flutter interface, Laravel API, PostgreSQL schema and deployment — so there is no gap between what the database can express and what the interface can show.
Yes. I integrate LLMs into existing workflows: WhatsApp assistants, document processing, lead qualification and AI-assisted QA — with guardrails, cost tracking and a human fallback where it matters.
Yes. I work in your timezone for calls and ship in two-week increments with staging links, so you see progress instead of promises.
Flutter and Dart for mobile, web and desktop; Laravel and PHP for APIs; PostgreSQL for data; plus REST APIs, Firebase, Supabase, GitHub and local-payment integrations where relevant.
Every quote comes from a written scope after we agree on the goal. I do not publish price lists because school management software, a restaurant POS and an election platform are different jobs — I will tell you how I would approach yours once we talk.
Both. Flutter lets me ship one codebase to Android, iOS, web and desktop, so the same application runs wherever your users are.
Website, software, mobile app or AI automation — tell me the goal and I will bring the plan, timeline and team.
09 — Contact
I'm open to software development opportunities, freelance projects, collaborations and meaningful technology work.
Tell me what you are building and I will reply with how I would approach it.
No contact email is configured yet. Set NEXT_PUBLIC_EMAIL in .env.local to enable direct contact — see README.md.