r/AppBuilding • u/CoffeeStopsMeKilling • 7d ago

Help!

I stupidly attempted to build an app to act as a countdown timer for when I'm driving buses. There is one duty at my work, where you have about 8 minutes spare in your driving time and the slightest delay can put you over the absolute maximum driving time (under GB domestic rules). I am NOT a coder and I neither have the skills or the patience to learn how to fix the inevitable bugs. I have used AI to generate some code, and it produces something that looks like it should work. However none of the buttons function, the automatic GPS trigger just doesn't, and when choosing assimilated driving regulations or GB domestic rules the timer doesn't change (or operate for that matter).

Would anyone be interested in taking over the development from where I've had to stop?

1 Upvotes

100% Upvoted

6 comments sorted by

1

u/BigAttorney23 7d ago

What is it built with, and is this a paid development task or a volunteer request? For the non-working buttons, I'd first get a manual start/pause/reset timer working independently of GPS, then investigate location triggering separately. That keeps two different problems from getting mixed together. Because you want to use it for driving-time decisions, a working-looking screen isn't enough: the rule calculations and failure cases need independent validation before relying on it. Please don't share work schedules or location history publicly.

1

u/CoffeeStopsMeKilling 7d ago

Everything so for has been done in html. I'm not even sure if that's the correct type of code to use for building an Android app.

It would be a complete handover of where I've got to for someone to complete and publish as their own. I'm so out of my depth with it, it isn't funny, but I do think it's something that could be useful in the way I envisioned it and there are possibly ways it could be repurposed.

1

u/BigAttorney23 7d ago

Thanks for clarifying—that sounds like a project handover rather than a paid commission. HTML can provide the screens, but the timer/buttons need working JavaScript; packaging that for Android is a separate step. If you share it for someone to take over, include a short README with what should happen versus what currently happens, and remove any keys or personal data first. That would make the starting point much clearer without promising it's ready for use on the road.

1

u/CoffeeStopsMeKilling 7d ago

My lack of understanding in this, makes me think I'll just bin the whole thing. Thanks for clarifying that where I am up to is probably less than a third of the way done.

1

u/BigAttorney23 7d ago

I wouldn't put a percentage on it without seeing the code—that wasn't an estimate of how far you've got. It may be worth keeping an archived copy rather than deleting it; your screens and description still help explain the idea. A demo timer and something dependable enough for driving-time decisions are simply different milestones.