Programma: planning a meetup program app makers show up for

Ask a Dutch organizer for the programma and you get the running order of the evening: who speaks when, how long the break lasts, when the bar closes. The word simply means program. It is also the part of a meetup that decides whether people come back. A good venue and free pizza bring a crowd once. A program that respects people's evening brings them back the month after.

This guide is for anyone putting together a recurring evening for app developers, designers or product people: a city's iOS group, an Android and Kotlin night, a Flutter gathering at a coworking space. It covers formats and length, mixing levels, finding speakers, picking dates and making the room work for everyone who signs up.

Contains affiliate links.

Start from the evening, not the talks

Most first programs are built backward. The organizer finds two speakers and then works out what happens around them. Try it the other way: decide how long the evening is, then fit the content into it.

A weekday meetup has about two and a half hours of real attention, counted from the moment people arrive to the moment they start checking train times. In the Netherlands, where people tend to eat early, the evening usually has to make room for food before anything else. A shape that works for many groups:

1. Doors open, food and drinks, people find each other (30 to 45 minutes).
2. A short welcome: what tonight is, where the toilets are, the code of conduct in one sentence, the Wi-Fi (5 minutes).
3. First talk, with questions (25 to 30 minutes).
4. A break long enough for a refill and one conversation (15 minutes).
5. Second slot: a talk, a demo or a round of lightning talks (20 to 30 minutes).
6. Announcements and the date of the next edition (5 minutes).
7. Drinks, with a clear end time (45 to 60 minutes).

That adds up to about three hours with the social part included, and under an hour of stage time. The ratio is deliberate. People come to meetups for each other as much as for the content, and an evening of four back-to-back talks leaves no room for the conversations that make a local community useful.

Choosing formats

A meetup program doesn't have to be two long talks. Mixing formats keeps the evening moving and gives more people a turn on stage.

Two notes on formats. The PechaKucha style of 20 slides shown for 20 seconds each, and the faster five-minute variants, are a gentle way to get nervous speakers on stage, because the format does the pacing for them. Workshops, on the other hand, rarely fit inside a normal meetup evening. Give them their own date, cap the seats, and send setup instructions a week ahead so nobody spends the first half hour downloading an SDK over shared Wi-Fi.

Mixing levels without losing anyone

A meetup audience is mixed by nature: students next to people who have shipped apps for a decade. The program can serve both if each evening has one piece a beginner can follow from start to finish and one that experienced developers will learn something from.

Label the level in the listing ("no Compose experience needed", "assumes you have shipped a widget extension"). It costs one line and saves a lot of disappointment. Ask speakers to open with a minute of context before going deep, and to say plainly which slides people can safely tune out. Over a season, rotate the themes: design one month, testing the next, a business topic after that. Developers who only ever hear about architecture drift away, and so do designers who never see their work on the agenda.

Running a call for talks

Waiting for speakers to volunteer works for about three editions. After that you need an open call that stays open all year. Keep the form short:

• Name and a way to reach them.
• A working title and three or four sentences on what the audience will take home.
• Preferred format and length.
• Level: beginner, intermediate or advanced.
• Whether this is their first talk, and whether they would like help with it.
• Any access needs on stage: a seat, a handheld microphone, extra setup time.

The question about first talks matters more than any other. Offer a run-through on a video call a week before, help with slide structure, or a lightning slot as a first step. Many people who would give a good local talk have simply never been asked. A personal message to someone who wrote a useful blog post, or who answers questions well in a community chat, works better than any public call.

Reply to everyone who submits, including the proposals you turn down, and keep a list of ideas that suit a later theme. Announce speakers only once both have confirmed, and decide in advance what happens if one cancels: a backup lightning round, an open discussion, or an earlier finish.

Picking dates and times

Tuesday, Wednesday and Thursday evenings are the usual choice, because Monday is for catching up and Friday competes with everything else. Check the local calendar before you fix a date: university exam weeks, school holidays, other tech evenings in the same city. Check the global calendar too. An iOS meetup in the week of Apple's developer conference will either be empty or turn into a keynote discussion, which can be a fine format if you plan it that way. Our mobile event schedule shows when the big recurring events usually fall.

Keep the rhythm steady. A meetup on the second Wednesday of every other month is easier to remember than one that appears whenever a speaker turns up. Announce the next date at the end of each evening, and publish the program at least three weeks ahead so people can arrange childcare, travel and work.

Accessibility is part of the program

Access is not a separate list for the venue manager. It shapes the program itself, and most of it costs little:

• Put the start time, the end time and the time of the first talk in the listing, so people who can't stand around for an hour can arrive for the content.
• Describe the venue honestly: step-free entrance or not, lift, accessible toilet, distance from public transport, how loud the room gets.
• Use a microphone for every speaker and every audience question, even in a small room, and repeat questions from the floor before answering.
• Ask speakers for large type, strong contrast and no meaning carried by color alone, and share slides afterward for anyone who missed a detail.
• Offer food that covers common dietary needs, and label it.
• Keep a quieter corner or a second room free during the social part.
• Publish a code of conduct and name the person to talk to on the night.

If you record talks, add captions before publishing. Automatic captions are a start; a short correction pass on names and technical terms makes them usable.

For a wider picture of how app communities in the Netherlands run their evenings, see our feature on the Dutch app scene. And if you are sitting in the audience at a bigger event, picking sessions rather than booking speakers, start with the guide to reading a conference programme.

Questions

How many talks should one meetup evening have?

Two is the safe number for a weekday evening, or one talk followed by a round of lightning talks. Beyond that, attention drops and the social part shrinks, and that part is often what people came for.

What if a speaker cancels on the day?

Keep a fallback in your pocket for every edition: a lightning round with two or three regulars who agreed in advance, a short open discussion on the evening's theme, or a longer question session with the remaining speaker. Tell the room plainly and finish a little early rather than stretching.

What should a speaker get in return?

At the very least a clear brief, a run-through if they want one, a working setup on the night and a public thank-you. Recordings and photos they can reuse are appreciated. Some groups also cover travel for speakers from another city when the host company agrees to pay.

Can a meetup work online?

It can, especially for niche topics whose audience is spread over several cities. Online evenings need a shorter program, a moderator watching the chat and captions switched on from the start. The conversation after the talks is the hardest part to replace, so keep the call open for anyone who wants to stay.