BR / IDENTITY
Baishalya Roul profile photo
BR brand mark

Independent software builder

Baishalya Roul

Android · Windows · Web · Local-first systems
Official email
baishalya1999@gmail.com
Website
baisalya.com
GitHub
@Baisalya ↗
Current focus
Practical software products and dependable releases

BR is the personal mark for Baishalya Roul. Click it anytime to return home and reopen this card.

Independent software builder

Building software that stays useful after the demo.

I’m Baishalya Roul. I design and build practical software for Android, Windows, and the web — with a focus on local-first workflows, clear product experiences, and tools that solve real operational problems.

Flutter Android Windows Local-first systems
baisalya.com / build

$ current-work --show

developer_toolsDevDesk
business_opsShopPilot
field_systemsConstruction ERP
android_utilityNotiVault
teacher_toolsEduSheet
Shipping practical products, one system at a time.
About

Software engineering with a product mindset.

My work sits between product design and implementation: understand the workflow, reduce unnecessary complexity, then build the software so it remains dependable in everyday use.

I work primarily with Flutter and Android, and I also build Windows and web experiences around the products I ship. The current software in this repository spans developer tooling, shop operations, construction workflows, teacher tools, notification history, and field documentation.

A recurring theme across these products is ownership: ordinary files where possible, offline or local-first workflows where they matter, and product surfaces that explain what the software actually does rather than hiding behind feature lists.

01

Practical first

Start from the real workflow and build around the job the software needs to finish.

02

Local where it matters

Use offline and local-first patterns when reliability, ownership, or field use makes them the better fit.

03

Release-minded

Treat documentation, validation, platform behavior, and recovery as part of the product — not cleanup after coding.

2021 — 2023Master of Computer ApplicationsCenturion University
2017 — 2020Bachelor of Computer ApplicationsUtkal University
Software

Products built around real work.

Each product has its own dedicated website or release surface. This page is the professional index; the software sites themselves remain independent.

ShopPilot application logo Private Preview
Shop operationsOffline-first

ShopPilot

Billing and operations for repair shops, bakeries, grocery and retail stores, restaurants, tailors, and garages — with stock, staff, branches, reports, and recovery.

Construction ERP application logo Coming Soon
Construction operationsOffline-first

Construction ERP

Connects tender value, project budgets, daily work, stock, labour, machinery, approvals, and reports for site and office teams.

NotiVault private notification history app preview Coming Soon
Android utilityPrivate + local-first

NotiVault

Preserves selected chat notification previews before they disappear, with voice notes and media saved when the notification exposes them.

No public installer is offered yet.

EduSheet brand mark Teacher tool
EducationQuestion papers

EduSheet

A math-first question paper maker for teachers, designed to make equations and structured paper creation faster to work with.

SurveyCam application logo Published
Field documentationAndroid

SurveyCam - Location & Geo Tag

A published Android field-proof camera for GPS and timestamped photos/videos, project folders, field notes, custom overlays, and PDF proof reports.

Engineering

Engineering choices shaped by the work, not a technology checklist.

I work across product structure, application behavior, local data, platform delivery, and release hardening. The emphasis changes by product, but the goal stays the same: software that is understandable, recoverable, and dependable in everyday use.

01

Application engineering

Cross-platform product delivery

Flutter-based applications for Android and Windows, with platform behavior treated as part of the product rather than as a final packaging step.

  • Flutter & Dart application architecture
  • Android interaction and release surfaces
  • Windows desktop workflows and distribution
02

Data & resilience

Offline and local-first systems

Products such as DevDesk, ShopPilot, Construction ERP, and NotiVault are designed around local ownership, offline continuity, recovery, or device-first storage where the workflow calls for it.

  • SQLite and device-local persistence
  • Backup, restore, recovery, and migration thinking
  • Ordinary-file workflows where appropriate
03

Workflow design

Operational software, not isolated screens

I structure interfaces around the work that has to move through them: billing, inventory, project operations, field evidence, teaching tools, API workspaces, and documentation.

  • Task and information-flow modelling
  • Dense desktop and touch-first mobile surfaces
  • Clear states, actions, and recovery paths
04

Release engineering

Shipping includes the reliability work.

Validation scripts, documentation, privacy/support surfaces, platform-specific release checks, and regression protection are treated as engineering deliverables.

  • Automated release-content validation
  • Regression and reference-integrity checks
  • Manuals, support, privacy, and release surfaces
Working stack

Tools are selected around the product boundary.

No percentage bars or arbitrary proficiency scores — these are the technologies and engineering areas visible in the software being built here.

Applications
FlutterDartAndroidWindows
Local systems
SQLiteLocal-firstOffline workflowsRecovery
Developer tooling
APIsOpenAPIGit workflowsJSON tooling
Product delivery
Responsive webValidationDocumentationRelease hardening
01Understand

Start with the job, constraints, platform, and failure cases.

02Structure

Define product boundaries, data ownership, states, and navigation.

03Build

Implement the smallest coherent architecture that supports the real workflow.

04Harden

Exercise recovery, regressions, accessibility, responsiveness, and edge cases.

05Ship

Package documentation, release surfaces, and validation with the product.

Contact

Start with the problem the software needs to solve.

For a product question, choose the product below. For a new build, share the target platform, the workflow that matters, and the constraint that cannot be ignored.

Product question Ask about existing software

Use the product selector so the message arrives with the right context.

New software requirement Describe the workflow first

What should become faster, clearer, safer, or easier to recover?

Software inquiry Give the message enough context to be useful.
Useful details

Current workflow · target platform · offline or sync needs · release status · recovery or privacy constraints

The form sends your message by email. Please do not send passwords, OTPs, payment details, recovery keys, or other secrets.