[Help Needed] Basketball 100 Squares Offline Betting App – Almost Complete! Fix Looping on Bettor Input + Add Team Names/Scores + Optional Fixed Bet Amount Post Body:

Work for Hire
1

Hello MIT App Inventor community!

I'm developing an offline 100 Squares betting board app for basketball (similar to football squares/pool).

  • 2 teams.

  • Winning square = last digit of Team A's final score (row) + last digit of Team B's final score (column), e.g., 112–89 → 2–9 wins.

  • Fully offline, manual admin/user input.

What's already working perfectly:

  • 10x10 grid (00 to 99 squares) auto-generated with numbers 0-9 on axes

  • Bettor selection/assignment to squares

  • Pot total calculation

  • Payout display logic

  • "Declare Winner" / enter winning digits → highlights winning square

  • Disables the winning square after declaration

  • Shows the winning bettor's name

Remaining issues / what I need help with (priority order):

  1. Infinite looping or repeating prompt after bettor input After the user/admin enters a bettor name and bet amount (probably in TextBoxes + Button to "Add Bet" or assign square), the app keeps looping/asking for input again and again without stopping or moving forward. It doesn't crash but won't proceed to the next step or let me select squares normally. I suspect a loop in the button .Click event or a Clock/Timer that's not stopping, or maybe an event firing repeatedly.

  2. Add manual input for Team Names and Final Scores

    • 2 TextBoxes or Labels + TextBoxes for Team A Name and Team B Name (e.g., "Lakers" vs "Celtics")

    • 2 numeric TextBoxes for Final Score Team A and Final Score Team B

    • Button like "Set Winner" or "Calculate Winner" that takes the last digits (e.g., scoreA mod 10, scoreB mod 10), finds/highlights the matching square, shows the owner, updates payout, etc. (I already have winning square highlight/disable logic – just need to connect it to these inputs instead of manual digit entry.)

  3. Optional nice-to-have: Fixed bet amount mode Add a global fixed amount (e.g., ₱100 or $10 per square) that the admin sets once via a TextBox + "Set Fixed Bet" button. Then, when adding bettors, skip individual amount input – every square just uses this fixed value. This way all bets are equal (common in some pools), and pot = fixed_amount × number_of_bets. Maybe a CheckBox "Use Fixed Bets?" to toggle between per-bettor amounts and fixed.

The app is very close – these are the last blockers!
I've attached my current .aia file + screenshots of:

  • The squares board

  • Bettor input section (where the loop happens)

  • Winner declaration area

If anyone can open the .aia and suggest/fix the blocks for these (especially the looping issue and connecting scores → winner), or even upload a corrected version, I would be extremely grateful. Happy to credit you or share the final app!

Thanks so much in advance – really appreciate any help from the community! :folded_hands::basketball:

Best,
Karl

3

Where are they?

You posted in the Work for Hire category. If someone can help what are you willing to pay?

4

ENDINGBOARD (7).aia (35.7 KB)

5

sorry i forget to attached it sorry my bad thank you so much kind sir

6

Screenshots ?
Budget ?

1 Like
7

you checked how much would it take my budget is just under 50 dollars to 100 dollars

9

Here’s a freebie:

blocks
blocks1462×2436 549 KB

You overloaded this Notifier with asking for different inputs.

If you must use Notifiers for this, pull in more Notifiers from the Designer and name them appropriately for their contexts. That would allow you to add events for each Notifier separately.

I see you have no data structures to match score pairs to bettor names and amounts, and no persistent storage (TinyDB) for your bets.

If i were the bookie, I would keep TinyDB entries for the game bets, one per game, with the bets stored as an AI2 table (list of lists) under the game tag (‘2026-03-15 Lakers vs Celtics)

  • bettor name (Gambino)
  • combo (3-2)
  • bet (1000)

That's a three column table.
You could use a spreadsheet for this

This would work well with the AI2 advanced list blocks.