Skip to content
AppDues
Log in
Contact salesSign up

App Promotion Summit New York: A Week of App Growth Events

This guide walks through a multi-day app-growth event week in New York City, held June 24–28, 2024, and anchored by the App Promotion Summit. It covers five distinct activities — a Times Square billboard showcase, a conference booth, a live podcast recording, an invite-only after-party, and local developer office visits — and explains how to decide which parts matter for your team. The announcement was published June 4, 2024; the page displays a June 7, 2024 update date, though the source's structured metadata records a later modification date, so treat the displayed update as the announcement's own label rather than a verified revision date.

What the week included

The event week ran from June 24 to June 28, 2024 in New York City. Rather than a single conference, it was a portfolio of activities with different audiences and different access rules. Five components stood out:

  • Times Square billboard showcase — animated ads from billboard-giveaway winners ran on a digital billboard in Times Square for the entire week.
  • App Promotion Summit New York — the team attended the APS conference on June 27, with a booth and swag.
  • Live Sub Club podcast recording — a live episode recorded during APS, 10:30–11:00 AM in the Main Conference Room.
  • Exclusive after-party at 701West — an invite-only networking event after the conference.
  • Local developer visits — office visits on June 25, 26, and 28, bookable via a scheduling link.

A useful way to read this list is by access model, not by chronology. Two components were open to anyone in the relevant audience (the conference booth and the podcast, whether live or in the feed). One was earned through a giveaway (the billboard). Two were gated (the after-party by invitation, the office visits by booking). That split matters more than the order of events, because gated components need lead time and open components need staffing.

Times Square billboard exposure for winning apps

The billboard component was tied to a giveaway: winning apps had their animated ads shown on a digital billboard in Times Square throughout the week. This is a reach play rather than a conversion play — the value is visibility in a high-traffic, iconic location, plus social clips of the apps appearing there. The team said clips would be shared on Twitter and LinkedIn during the week.

If you are evaluating a similar opportunity, treat it as brand exposure and social-content fuel. Two practical points: first, plan to capture footage yourself rather than relying solely on someone else's posts, since a third party's posting schedule is outside your control. Second, decide in advance what you want viewers to do after seeing the ad — a billboard impression has no click, so the follow-up has to come from your own channels.

Attending App Promotion Summit New York

The conference day was June 27, 2024. APS was framed as a way to connect with and learn from app developers, marketers, and industry leaders. The team planned a booth with swag, including a new plushie, and conversations about growing an app business.

For a team planning a similar presence, the practical questions are: what is the booth's purpose (recruiting, partnerships, product feedback, or brand awareness), who staffs it, and what follow-up happens after the event. A booth without a defined purpose tends to become a giveaway table; a booth with one produces a short list of conversations worth continuing.

Live Sub Club podcast recording

A live episode of the Sub Club podcast was recorded during APS, from 10:30 AM to 11:00 AM in the Main Conference Room. The host was joined by a senior growth executive from a language-learning app. The episode was also slated to appear in the podcast feed a few weeks later.

For attendees, the live recording offered a chance to hear growth strategy discussion in person; for everyone else, the feed version was the fallback. If you are planning a live recording at a conference, confirm room capacity, audio setup, and a release timeline before promoting it. The fixed 30-minute slot is itself a planning constraint: a live format leaves little room for overruns, so the conversation needs a structure before the room fills.

Exclusive after-party at 701West

The after-party was held at 701West, a venue with a view of the Times Square billboard. It was positioned as relaxed networking with industry peers and the team. Access was not open: interested attendees were asked to contact their existing contacts for an invite, and attendance was confirmed selectively because of limited availability.

This is the clearest example of a selective component in the week — public conference attendance did not automatically grant after-party access. If you are planning something similar, decide up front how invites are requested, who approves them, and how you communicate that capacity is limited without discouraging the broader audience. The invite-through-existing-contacts model keeps the guest list warm, but it also means anyone without a contact has no path in; say so plainly rather than leaving people to guess.

Visiting local developers

On June 25, 26, and 28, the team planned to visit local apps and app developers in New York City. The offer included swag, custom benchmarks, and tactical advice. The announcement described that advice as based on the team's experience working with over 30,000 apps — a first-party figure from the announcement that should be treated as the organizer's own claim rather than an independently verified count.

Visits were booked through a scheduling link. This is the most hands-on component of the week and the one most likely to produce specific, actionable takeaways for a participating team. If you are considering a similar program, prepare your own metrics and questions in advance so the session produces decisions rather than a general conversation.

Decision checklist: which parts to prioritize

Use this checklist to choose the right mix for your team:

  • Goal is reach or brand awareness → prioritize the billboard-style showcase and plan social capture.
  • Goal is learning and industry connection → prioritize the conference day and booth conversations.
  • Goal is content production → prioritize the live podcast recording and confirm release timing.
  • Goal is relationship-building with a smaller group → pursue the invite-only after-party, and accept that access is selective.
  • Goal is specific, tactical advice → book a developer office visit and bring your own metrics.
  • Goal is broad coverage → combine conference attendance with social clips and the podcast feed.

A useful rule: open components (conference, podcast feed) scale; gated components (after-party, office visits) require advance coordination and a named owner. Plan both tracks separately, and do not let the open track consume the lead time the gated track needs.

Field and control map for booking and invites

Two components required an action from interested attendees:

  • Developer office visit — a scheduling link was provided to book a time with the team. Inputs needed: your office location, preferred date among June 25, 26, or 28, and a contact. Output: a confirmed visit slot.
  • After-party at 701West — no public booking form. Input: a request through your existing contact. Output: a selective confirmation, subject to limited availability.

Everything else — the billboard showcase, the conference booth, and the live podcast — was open to the relevant audiences without a separate booking step. The distinction is worth keeping in mind when you design your own event week: a public booking form sets an expectation of confirmation, while an invite channel sets an expectation of discretion. Mixing the two in one component creates confusion.

Worked example: planning a similar week

Suppose a team wants to replicate this structure for a future event week. Using the captured 2024 evidence as a model:

  1. Pick a flagship conference day (here, June 27) and staff a booth with a clear purpose.
  2. Add a reach moment — a billboard or equivalent high-visibility placement — and assign someone to capture clips for social.
  3. Schedule a content recording during the conference, with a fixed time slot and a release plan for the feed.
  4. Host a smaller, selective networking event and decide the invite mechanism in advance.
  5. Reserve separate days for office visits and require bookings so the team can prepare benchmarks.

This sequence keeps open and gated activities distinct, which makes staffing and follow-up easier to manage. Note that the original week used three separate days for office visits (June 25, 26, and 28) around a single conference day — a reminder that the hands-on track needs more calendar space than the public track, even though it reaches fewer people.

Frequently asked questions

When did the New York event week take place?

June 24–28, 2024, with the App Promotion Summit conference on June 27.

Was the after-party open to all conference attendees?

No. It was invite-only and confirmed selectively because of limited availability; interested attendees were asked to reach out to their existing contacts.

How could a developer request an office visit?

Through the scheduling link provided in the announcement, choosing a time on June 25, 26, or 28.

Where could people watch the live podcast if they missed it?

The episode was expected to appear in the Sub Club podcast feed a few weeks after the live recording.