Development proposal: Support for customized brand identity (OAuth and email) on the BASE44 platform

Development proposal to improve personalization and brand identity on the BASE44 platform

Background:
While using the BASE44 system, I encountered two significant limitations that undermine the brand identity of end customers and damage the product's credibility and professionalism in the eyes of users:

1️⃣ Google OAuth – App name and domain cannot be customized

Current problem:
When logging in with Google OAuth, users are presented with the app name: BASE44.COM. It is not possible to set a different brand name or link to a unique domain.

Suggested improvement:
Allow developers/account owners to:

• Set a custom app name to be displayed in the Google permissions panel (e.g., QuanTerra instead of BASE44).

• Submit their own verified domain (e.g., quan-terra.com) through a simple interface within the platform.

• Upload a logo, email address, and app description, as defined in Google Cloud Console.

Advantages:

• Full branding for customers.

• Greater sense of trust from end users.

• Competitive advantage over competing platforms that provide customized OAuth.

2️⃣ Sending emails – cannot send from a private domain

Current issue:
All emails sent from the system (e.g., verifications, password resets, notifications) are sent from a default address: no-reply@base44-apps.com. There is no control over the sender name, reply address, or domain.

Suggested improvement:
Allow customers to:

• Set a custom sender address (for example: no-reply@quan-terra.com).

• Set Reply-To to a service address (e.g., support@quan-terra.com).

• Set the sender name that will appear in the email (e.g., QuanTerra System).

• Set DNS Entries such as SPF / DKIM for easy domain verification from the panel.

Advantages:

• Professional image and full control over communication with users.

• Prevent emails from being filtered as spam.

• Improved email open rates and compliance with modern security standards.

Implementation proposal:

Both capabilities (customized OAuth + private domain emails) can be included as part of advanced paid subscription plans, providing significant added value to customers who want full control and brand identity.

I would be happy to discuss or assist with the technical specifications of the features if you are interested.

Best regards,
Oshri Ben Yehuda
QuanTerra



Feature Proposal: Branded Identity Support for Google OAuth and Email System in BASE44

Background:
During my use of the BASE44 platform, I encountered two limitations that significantly affect brand identity and user trust. These limitations reduce the ability of developers to provide...