Office Hours #62 · Meet Basecamp.
Basecamp launches live: discover events, RSVP from the builder, find local communities, and help shape what comes next.
Learn, ask, and build together.
Find the people building near you.
Illustrative directory preview — use the session resources for the real community destination.
A directory, not a replacement
Basecamp was presented as a home for discovering events and communities. It does not mean every existing Discord, WhatsApp or local community disappears into one new chat system.
Session #62 / The recap
Sam and community programs manager Monica introduced Basecamp, an in-product home for Base44 events and communities. Born from a 48-hour internal hackathon with Tiffany, the project reached its first public phase during the session: an events directory and a reviewed directory of official and independent communities.
The walkthrough covered RSVPs, calendar links, in-app and email notifications, community submissions, and language channels. The audience then supplied live UX feedback. Sam carefully separated the launched directories from possible future forums, guides, profile discovery, and gamification; Basecamp was not intended to replace Discord.
From the session
These updates reflect what was said on 25 August 2026, not a promise of current availability.
Initially shown from a staff account, Basecamp was confirmed live during the session and checked from Sam's personal account. It sits under Community alongside Launchpad. A broader social-media announcement was planned for the next day.
Basecamp brings event discovery, RSVP, Google Calendar links, sharing, and in-app/email reminders into the builder. Community, education, enterprise, partner, online, and in-person events can be surfaced together, including externally hosted Luma events.
Users can submit independent communities for staff review. External listings explicitly warn that Base44 does not own or moderate those groups; Base44 can remove a listing if necessary.
Spanish, Portuguese, and Japanese Discord channels were highlighted. Monica also sought two Lisbon-based people for an upcoming event. The Discord community was described as 55,000 members.
Monica said the next ambassador cohort would open applications in the next couple of weeks, with an application and vetting process. This was a recruitment teaser, not an open application shown live.
Sam said events.base44.com would eventually redirect to Basecamp once remaining RSVP lists and other dependencies were no longer needed. The old site was not declared fully retired during the call.
A mobile-team AMA on Reddit was promoted as the place to ask questions such as custom WhatsApp number support. Its event listing contained the time and joining information.
Forums, community guides, profile integration, attendance badges, owner profile links, an event-submission flow, and an official archive entry point were discussed as directions. A games week and Friday Twitch buildathon were explicitly unconfirmed.
What was taught
6 teaching points, with the practical details and limits preserved.
Open Community, then Basecamp. The Events tab helps users discover sessions; the Communities tab points to official Base44 spaces and reviewed independent groups. Launchpad remains a separate item under Community.
Open an event, RSVP, add it to Google Calendar if useful, and use its join or share link. Sam demonstrated the intended loop from RSVP to a live notification inside the builder and by email, helping users join without remembering an external schedule.
Use Submit your community and provide its name, platform, region/location, member size, interests, language, destination link, and description. Staff review it before listing. A multi-platform hub should use its primary destination and explain the other channels in its description.
The listing is reviewed and can be removed, but external group moderation belongs to its owners. A directory entry is not a transfer of ownership to Base44 or a guarantee about everything that happens there.
Existing members use Channels and Roles and select Español, Português, or Nihongo. New-member onboarding also surfaces these choices. Keep discussion in the channel's language and respect its community language moderators.
The launch has two directories. Profile discovery, user guides, forum-style help, richer badges, and preferences were examples of future possibilities. Sam asked for feedback to guide development rather than presenting the hackathon prototype as already shipped.
Every substantive question
Search all 35 answers, or filter by topic. Open a question for the full response.
35 of 35 answers
Yes. Community, enterprise, and education teams work on in-person events, including events with partners. Basecamp is intended to make relevant local and online events easier to find.
Monica described a future event-submission flow and support for prospective hosts. It was a next-stage plan; the community-directory submission form was the feature demonstrated as available.
No. Sam explicitly rejected replacing Discord, voice chat, or the existing communities. Basecamp is a discovery and connection layer inside the product.
Sam doubted unrestricted advertising would be manageable. Connecting partners and builders safely was relevant, but no advertising feature was announced.
No. Create a useful group with other builders, then submit it for review when it offers value. Staff can check its legitimacy and relevance before listing it.
Many builders do not use Discord. A product-level entry point makes peer support, education, events, and local or language-based communities discoverable without requiring prior knowledge of all the external channels.
Sam said this was intentional because the listing needs a clear destination. Choose the most relevant platform; if the community spans several services, link its hub and explain the structure in the description for review.
No. Sam said signed-in users can access Basecamp and a useful community is eligible for review regardless of whether its owner has a paid plan.
Through the partner directory, Discord profiles, links shared by the person, and Launchpad submissions. Better discovery and links from community ownership were future goals.
The ambassador program is a recruited cohort with application and vetting, separate from simply starting a community. The next cohort's link was expected in announcements when ready.
Open Community → Basecamp and select Submit your community. Sam showed entry points on the Basecamp screens, including the community page, that open the form.
Sam had no confirmed change. He brainstormed expanded requirements or a prestige-style number or symbol system, while making clear it was not his team's announced roadmap.
Sam explained that the directories serve different needs and could both become large. Separation helps avoid a single unwieldy scrolling list.
Sam wanted local and worldwide results with toggles for other regions. He described this as desired work subject to implementation, not a feature to rely on at launch.
Try a hard refresh or sign out and back in. Sam said the rollout was reaching users in batches and a refreshed session could update access; he had confirmed it on his personal account.
Listings were meant to be real, but Sam acknowledged test entries might have leaked into a release and asked users to report them. Language-channel counts could show a 500 minimum rather than an exact membership count.
Sam checked during the session and did not see Basecamp on mobile, although a nested Community item was present. The mobile experience was therefore not confirmed working in that live check.
Sam acknowledged the problem and said compacting an earlier larger map appeared to have shifted pins without correct adjustment. He also wanted clearer colours and placement; no fix was verified during the call.
Sam liked the idea and had logged it, but noted that global communities need a sensible selection model. It was feedback, not an interaction already shipped.
Sam agreed the toggle could be clearer and asked for user preferences on the default view. Remembering a user's chosen view was suggested, not confirmed as implemented.
Sam thought the initial two-tab product was simple enough not to need a full tour. He was open to location, interests, and view preferences, potentially inferred or offered with a small prompt.
Yes, Sam said event RSVPs were connected to email and in-app notifications. A user could follow the notification from the builder to the live event.
The audience discussed expanding a day's events. During the exchange Sam discovered that clicking the date number already exposed functionality he had not noticed; broader tile-click behaviour was still feedback.
Yes, eventually. Sam expected a transition period for old RSVP lists and remaining uses, followed by a redirect when the legacy site was fully redundant.
Sam welcomed feedback directly and pointed to the overhauled feedback.base44.com. An in-product feedback modal was proposed, not shown as a new feature.
Sam did not promise an extension and said Arcade was owned by another team. He described experiments with short games inside the builder, using a game during a security scan as an explicitly invented example.
Sam praised the unofficial archive and said an official entry point within Basecamp was on the wishlist and in the original pitch. It was not announced as a completed integration.
No confirmed date. Sam had pitched a games week ending in a Friday-night Twitch buildathon and still needed approval.
Sam said teams explore LLMs internally but gave no model announcement or availability commitment.
Sam had nothing new to report and recommended asking the mobile team in the upcoming Reddit AMA.
Use the event listing and its Reddit destination. It was not a Discord-hosted AMA; the listing showed the schedule.
Yes. Sam said Office Hours already welcomes such discussions, and a community-run B2B session was another option. He was open to targeted sessions if there was demand, but did not announce one.
Sam acknowledged limits to his expertise. Specific regulatory or enterprise questions may need the relevant specialist team; a future targeted Office Hours was possible, not legal guidance or a confirmed session.
Sam pointed to Launchpad under Community. He also discussed richer project and profile sharing as possible Basecamp evolution, not a separate new channel already created.
Sam pointed to the unofficial Office Hours archive and its Gingy assistant for exploring past sessions. The live discussion did not demonstrate a successful search for the specific regional payments question.
Keep these close
Continue from here
Named resources are retained without inventing missing links.
Basecamp — open Community in the Base44 product
Mobile team AMA — Reddit destination available through the event listing
The original recording
Watch the demonstrations, questions and in-the-moment decisions in full.