Skip to content

Office Hours #20 · Session recap

The operations rack.

A wide-ranging Wednesday Open Q&A covering custom login progress, Super Agent reliability and end-to-end app testing, Stripe vs RevenueCat, role-based access and RLS, CRM integrations, SEO/GEO, white labelling, NPM packages, admin control panels, rate limits, project recovery, and multiple feature teases including multi-user editor collaboration.

Date
Wednesday 29th April 2026
Time
5:00 PM UTC
Host
Sam
Format
Open Mic · 50+ attendees
Watch the recording

Announcements

The status column.

Eleven indicator lights from the session — what shipped, what is scheduled, and what Sam could only tease.

Key teaching points

Eight units, labelled and switched.

Every recurring theme from the open mic, mounted as its own rack unit. Flip a switch to open the faceplate.

Community Q&A

The channel log.

All 51 questions answered during the live session, logged in original order. Search the log or patch into a single channel.

Showing 51 of 51 questions

  1. There is a feature directly related to this coming out very, very soon. As a workaround today, append preview- to a URL to use the preview window in the browser.

  2. Sam's experience is hit-or-miss at build time. If a Super Agent comes out broken, do not fix that context window — start a brand new agent from scratch. Once built cleanly, some agents run reliably for months.

  3. If integrating an external CRM, the best practice in Base44 is often to build your own. If you already have an external CRM on supported platforms, use migrate-from-platform from the homepage plus icon.

  4. Build an end-to-end Super Agent tester. Have it use your app daily as a user and email or PDF you a report of what broke.

  5. Yes — use the same end-to-end Super Agent testing pattern.

  6. Close, close, close. This week or next week is the aim. Sam is pushing for Discord/community feature flag access first.

  7. Yes. Builder Plus or higher gives Git sync and full export. Pages and functions export, but the SDK does not.

  8. Use an AI to explain it to the AI. Ramble in another model, ask it to create a clean prompt, then paste that into Base44.

  9. Watch the RLS / Security session VODs. Run security scans, audit tables, and use the new RLS properly.

  10. They are different. Super Agents primarily use message credits; standard agents primarily use integration credits. Automations are often better for high-frequency scheduled tasks.

  11. Sam said it is almost always layout.js or duplicate layout files, not platform scripts. Screenshot, draw arrows, prompt across models, revert if needed, retry.

  12. Press downgrade. Annual-to-monthly controls are in billing; if stuck, raise a support ticket.

  13. Currently it is random. A partner programme overhaul is coming with ratings, reviews, and comments.

  14. Build something and prompt-engineer it until it looks good. NPM packages do not make things beautiful by themselves — you use them well.

  15. Log a ticket on the Base44 website. It will route to the mobile team.

  16. Set the app public with no login required, then gate signups behind admin approval.

  17. User types and permissions are whatever you define. There is no preset list.

  18. Apple bans Stripe. Use RevenueCat for App Store and Google Play subscriptions.

  19. Not really. You do not need SSR for SEO. Native SEO/GEO plus thoughtful SEO work handles most cases.

  20. Dashboard → API → scroll down to Functions. Same keys, new location.

  21. Yes. Use the top-left rewind clock for version control or the Revert button on any chat message.

  22. Just websockets. Use React Chess Tools NPM library and prompt a websocket-based chess.com replacement.

  23. Yes. Ask your AI to improve SEO beyond the defaults.

  24. Images at scale depend on model choice and architecture. Multi-stage pipelines are possible with Super Agents. Rate limits: 5,000 data pulls, 150 req/min per user, 150 service-role req/min globally. SDK internals are abstracted; external APIs are controllable.

  25. App video generation is coming soon — Sam has seen it. Voiceover APIs are unclear; Sam uses ElevenLabs and OpenAI today.

  26. No — that is a JavaScript / React limitation more than Base44. But game-dev tooling is moving fast.

  27. You can use Stripe directly on Google Play, but RevenueCat is the cleanest path covering both stores.

  28. Paystack works broadly for African users, and Payfast is South Africa specific. Both have APIs.

  29. Only if you allow it. Rate-limit your app and monetise usage, e.g. two free generations weekly, then paid packs.

  30. Sam saw something internally but could not share. New collaboration features are coming.

  31. Watch Session #18. Sam shared the Neon Pay demo from the reveal session.

  32. It is bespoke per agent. A dedicated Super Agents session will happen when the feature stabilises.

  33. Yes — GDPR compliant and SOC 2. Lily linked the full compliance page.

  34. Anything with an API is implementable. Do not worry if it is not in the connectors directory.

  35. AJ's archive site and a Discord thread aggregating VODs.

  36. It can suggest prompts but cannot build for you and cannot really see rendered visuals. Use screenshots, ask it for a fix prompt, then run that prompt yourself.

  37. No. One agent with multiple skills, rules, and automations is fine.

  38. Sam tested it and login worked. The issue was that the chat ability had not been built yet, so there was nothing to use after login.

  39. Yes — likely a session next week. Sam would not elaborate yet.

  40. No native one — build it yourself in your admin control panel.

  41. Do not say “only available to me.” Say “build me an admin control panel” and admin-gate it once.

  42. “Build me an admin panel” works. Even “build me an ACP” works because AI fills it from app context.

  43. Yes. Prompt “build me user-to-user messaging” or “build me a live chat system using websockets.”

  44. Yes. Generate a PDF in the app and let a button download it on the phone.

  45. Yes if generated via Base44 AI. If using a third-party PDF API, it uses your provider balance instead.

  46. Good topic and highly requested. It needs its own session.

  47. Dashboard manages the Base44 project. Your admin CP is bespoke and manages your app behaviour from inside the app.

  48. You are always logged into Base44 in preview and recognised as admin. The admin CP button is conditionally rendered for admins only.

  49. Tuesday, Wednesday, Thursday at 5:00 PM UTC every week: Beginner, Open Mic, Advanced.

  50. AJ helped with the NPM package solution for full-app i18n.

  51. Sam cannot answer compliance specifics. Open a ticket. Current status: SOC 2, ISO 27001, GDPR; HIPAA may be enterprise tier.

The debrief

Power-down checklist.

Ten takeaways

  1. Custom login is “this week or next week.” Sam is pushing for Discord-first feature flag access and the team is working on final details like password reset forms.

  2. Build an admin control panel in every Base44 app. Prompt “build me an admin CP” and put analytics, SEO, schema views, Super Agent chats, complaints, and controls inside it.

  3. Build an end-to-end Super Agent for testing. Daily run, exercises every workflow, emails or PDFs a report, and helps stop feature-update breakage loops.

  4. Stripe is banned on Apple App Store. Even references to Stripe in code can fail review. Use RevenueCat for both stores.

  5. You do not need SSR for SEO. The native SEO/GEO feature plus good prompting covers most cases. SSR is only for specialist dynamic-loading and AdSense scenarios.

  6. API page is redesigned. Stripe webhook secrets are now at Dashboard → API → Functions.

  7. Rate limits confirmed: 150 req/min per user, 150 req/min service role globally, 5,000 data query pull cap.

  8. Super Agents primarily use message credits. Standard in-app agents primarily use integration credits.

  9. Project recovery: use the rewind clock and revert-on-message buttons instead of fighting broken states.

  10. Multi-user collaboration on the editor is being worked on. Sam saw new internal material but could not share details.

Heard on the mic

“Build me an admin control panel.”

— Sam's must-use prompt for every app

“Every single app you build, anywhere in the world, should have one.”

— Sam, on admin control panels

“Close, close, close.”

— AJ / Sam, on custom login progress

“I'd prefer not to lose my job.”

— Sam, teasing multi-user editor collaboration

Patch points