Operator guide

Branding and customization

Replace the reference identity with your own business across the platform.

Change portal identity in the panel

The Branding area lets the operator select the administrative panel, web application, agency portal, Pay or Studio and change the displayed name, logo and favicon. Preview the selected image and save the intended change. The current image form supports PNG, JPEG or WebP within its displayed 1 MB limit.

Use a clear logo with adequate empty space around it and a legible small favicon. Review both a narrow phone layout and a desktop layout; a wide logo that looks good at full size may become unreadable in a small header.

What requires a build

SurfaceCustomization boundary
Android and iOSLauncher name/icon, splash screen, app identity and native provider configuration are build-time work. Portal branding does not rename an installed package.
Flutter webUse the documented web assets, configuration and build process for the deployed client. Review its base path and browser title.
Windows StudioUpdate the desktop identity and packaging assets through the buyer Windows guide, then build and verify the installer.
Web portalsUse the panel’s surface-specific name/logo/favicon controls for supported runtime branding.

A practical review

  1. Choose a consistent product name, icon, logo and splash artwork.
  2. Apply the portal settings and the corresponding build-time client assets.
  3. Check launcher, sign-in, header, dialogs, browser tab and installer presentation.
  4. Review translated labels and longer names on small screens.
  5. Use your own provider accounts and app-store metadata; reference-brand settings are not your business credentials.

Brand and delivery

Astra is the seller’s reference name and is not included as a licensed business identity. The source package is intended for your own brand. Follow the buyer manual’s asset paths, recommended sizes and toolchain versions for the exact release you purchased.

Contact the seller through the product’s Codester support channel for product-specific questions. Optional custom development is not an included feature or a promised future release.

Image sizes and source locations

Recommended portal artwork is 512 × 512 pixels for a logo and 256 × 256 pixels for a favicon. Keep images within the form’s file limit and inspect the result. These recommendations do not replace the multiple sizes required by native app icons.

The paths below are relative to the extracted buyer ZIP. They identify presentation assets only; signing and provider credentials are covered privately.

PresentationSource location
Android display namesource/app/android/app/src/main/AndroidManifest.xml — application label.
Android launcher iconssource/app/android/app/src/main/res/mipmap-*/ic_launcher.png — mdpi/hdpi/xhdpi/xxhdpi/xxxhdpi use 48/72/96/144/192 px.
Android adaptive icon and splashUnder source/app/android/app/src/main/res/: drawable/astra_launcher.png, values/astra_colors.xml and drawable/astra_splash_neutral.xml.
iOS display namesource/app/ios/Runner/Info.plist — CFBundleDisplayName and CFBundleName.
iOS icon and launch artworkUnder source/app/ios/Runner/Assets.xcassets/: AppIcon.appiconset and LaunchImage.imageset. Respect each Contents.json mapping, including the 1024 × 1024 store icon.
Flutter colors and opening animationsource/app/lib/astra/theme.dart; source/app/assets/astra/astra-icon.png, launch-orbit.mp4 and launch-orbit-poster.jpg; source/app/lib/astra/widgets/launch_splash.dart.
Web title, icon and install metadatasource/app/web/index.html, manifest.json, favicon.png and icons/. Update the corresponding web launch artwork too.
Portal defaultssource/platform/portals/assets/astra-icon.png and portal.css. Prefer the panel’s supported runtime branding controls for routine identity changes.

Rebuild native clients after changing launcher or splash resources; hot reload does not replace them. Avoid a global replacement of every “astra” occurrence, because internal identifiers and communication channels are not display labels.