How to make an app for a local election campaign

A ward campaign is run by a few dozen volunteers over a few weeks: who covers which lane today, which colonies are still left, what residents raised at the last meeting, what was spent on chairs and the sound system. An app keeps the campaign office's lists in one place.

Updated 2026-11-09

Who uses the app

The campaign office and volunteers. For volunteers to see their own lanes and mark visits on their phones, connect the campaign's own Supabase database with sign-in, so only your team opens the app.

The screens a local election campaign app needs

Volunteers: Name, phone, colony they know, days they are free and the team leader
Visit plan: Colonies and lanes with the volunteer assigned, date planned and done or not
Meetings: Public meetings and society meetings with date, place, permissions taken and arrangements
Issues: Problems residents raised, such as a broken street light, the lane and who will follow up
Expenses: Each spend with date, item, amount, paid to and a photo of the bill
Today: Today's visits, meetings and which volunteers are on duty

Features worth asking for

Lane-wise visit plan so no colony is missed and none is visited twice
A WhatsApp button to send each volunteer their lanes for the day
Issues logged by lane; a resident's name and phone saved only if they agree
A permission checklist on each meeting, as your election agent sets it
Expense register with bill photos and a running total for the campaign's accounts
Sign-in so volunteers see the campaign's lists and the public doesn't

Where the data lives

Volunteers on their own phones need the campaign's own Supabase database, with sign-in so only the team sees it. The data is in the campaign's account, and it should be deleted once the election work is done.

How to make it with AppCub, step by step

Decide what the app does. List the screens you need, for example: Volunteers, Visit plan, Meetings, Issues, Expenses.
Describe it to AppCub. Paste the request below, changed to your own business and details.
Check the plan. AppCub shows the screens and features it will build. Change them in the chat until they are right; seeing the plan is free.
Try it on your phone. The app runs live next to the chat. Scan the QR code to install it, and ask for changes.
Share it. Share it as a web link, an APK file, or publish it on Google Play from your own developer account.

Copy this request, change the details to match your local election campaign, and paste it into AppCub:

Make an app for Meena Kulkarni's campaign office, Ward 14, Kothrud, Pune. Screens: volunteers, visit plan, meetings, issues, expenses and today. Volunteers: name, phone, colony, free days, team leader. Visit plan: colony, lane, volunteer, date, done or not, with a WhatsApp button to send a volunteer their lanes. Meetings with date, place and a permission checklist. Issues: lane, problem, follow-up person; resident's name and phone only with a consent tick. Expenses with date, item, amount, paid to and bill photo, with a total. Volunteers sign in. Blue and white colours.

Tips for a local election campaign app

Don't copy voter lists or residents' personal details into the app; save a resident's name or phone only when they agree, for the issue they raised.
Follow the Election Commission's rules on campaigning and spending, and keep the expenses screen as the election agent asks, with every bill photo.
Give each volunteer only the lanes they cover; the team leader sees the full plan.
Mark visits done the same evening, or the plan stops being true by the second week.
Decide before polling day who will close the app and delete residents' details after the result.

What it costs

Describing your app and seeing AppCub’s plan for it is free.
A new app usually takes 60 to 110 credits. Start with the 2-day trial for ₹99 (150 credits, enough for one app and a few changes) or the one-time App Pack for ₹499. Starter is ₹1,599 a month for 700 credits.
Google Play needs a paid plan (it includes the Play Store bundle and your app’s signing key) and your own Google Play developer account, a one-time US$25 fee to Google.
Work that fails or is rolled back costs no credits.

See all plans

Good to know

The app doesn't send bulk SMS or WhatsApp messages to voters, and it shouldn't hold voter-roll data. It is a register for the campaign team; messages to volunteers go when someone taps the WhatsApp button.
AppCub builds Android apps. You can also share the app as a web link that opens on any phone; for the iPhone App Store, AppCub’s team can do it for you.

Questions

Can we load the voter list into the campaign app?

We don't suggest it. Keep only your team's plans and, with their consent, the details of residents who asked you to follow up on an issue.

Can the app send messages to all voters in the ward?

No. AppCub apps don't send bulk messages. A WhatsApp button opens a ready message to one person at a time, such as a volunteer.

Can volunteers mark which lanes they have covered?

Yes, with the campaign's Supabase database. Each volunteer marks a lane done, and the office sees what is left.

Can the app help keep campaign expense records?

Yes. Each spend is saved with a bill photo and the total updates. How to file those accounts is for your election agent and the election rules.

Can the app show a map of the ward?

It can show a map with pins for meeting places and the campaign office. It doesn't track volunteers' locations live.

What should we do with the app after the election?

Keep a PDF of the expenses you need for your accounts, then delete residents' details. You can keep the issues list if the candidate wins and will follow up.

Make your local election campaign app

Seeing the plan is free. Building starts with a 2-day trial for ₹99.

Start building