Inspiration

Nepali dates in Bikram Sambat (BS) are used in daily life, government work, and culture, while most international systems use Gregorian (AD). That split creates constant friction for students, travelers, form-fillers, and families. Digital Patro’s date converter targets that gap by making BS↔AD translation immediate and reliable.

What it does

  • Converts Nepali Bikram Sambat (B.S.) dates to Gregorian (A.D.) and vice versa.
  • Supports conversions across roughly 2000 B.S. to 2089 B.S.
  • Simple input flow: choose year, month, day, then convert and see the result in the other calendar.
  • Useful for birth dates, historical dates, paperwork, and document translation.
  • Integrated into the broader Digital Patro calendar app with a speed-and-clarity focus.

How I built it

  • Accounted for structural differences between BS and AD: BS starts 57 BCE and runs about 56–57 years ahead of AD depending on the month.
  • Used reference-date plus day-offset arithmetic, applying Gregorian leap-year rules and BS month-length variability (including Adhik Maas).
  • Designed the UI as a linear funnel (year → month → day → result) to reduce ambiguity and errors.

Challenges I ran into

  • Adhik Maas and BS month-length variability make naïve “year minus 57” logic wrong.
  • Boundary cases near month transitions can produce ±1 day drift if offsets or tables are inconsistent.
  • Older / pre-1900 B.S. dates are historically inconsistent, so firm supported limits were needed.

Accomplishments that I'm proud of

  • High accuracy within the supported BS range.
  • Clear explanation layer showing the 56–57 year difference and range limits so users trust results.
  • Smooth, ad-free, Nepali-first experience inside the app.

What I learned

  • Correct conversion depends on trustworthy date tables and careful offset logic before UI polish matters.
  • Stating limits up front increases trust more than hiding edge cases.
  • Small UX constraints (forced input order, instant result visibility) cut error rates sharply.

What's next for Digital Patro

  • Expand the reliable BS coverage range without sacrificing correctness.
  • Tighten edge-case handling around Adhik Maas and boundary days, with explicit warnings when confidence drops.
  • Add richer post-conversion context like weekday and festival/panchang hooks while keeping the flow lightweight.
Share this project:

Updates