NEURALNG
MEDIABETA

Avatar

Accessible identities with responsive images, deterministic fallbacks, shared Badge composition and overflow-aware groups.

Native image pipelineSSR safeHeadless ready

GET STARTED

Import

Import only the identity primitives you render from the granular entry point.

app.ts TypeScript
import {
  NeuralAvatar,
  NeuralAvatarGroup,
} from '@neural-ng/core/avatar';

@Component({ imports: [NeuralAvatar, NeuralAvatarGroup] })

Deterministic fallback priority

A valid image wins, followed by explicit or name-derived initials, an icon class, then projected content. A failed image never remains broken.

Ada Lovelace

Sizes, shapes and image fit

Five size presets combine with circle, rounded or square geometry. Image fit remains independently configurable as cover or contain.

Responsive native image pipeline

srcSet, sizes, loading, decoding, fetch priority and referrer policy map directly to the native image. The root exposes data-image-state as loading, loaded, error or fallback.

Ada Lovelace

Image error and retry

The native error event remains observable while the visual switches to fallback. Changing src resets failure state and retries the new image.

Radia PerlmanWaiting for the native image error event.

Status and notification Badges

Avatar owns identity; the reusable Badge directive owns dots, counts, severity, logical placement and announcement. No Avatar-only badge API is duplicated.

AvatarGroup and localized overflow

max keeps useful identities visible and replaces the remainder with an accessible +N. The source projection is preserved and reacts when children or max change.

Ada Lovelace +3

Unstyled and typed class slots

Headless mode retains fixed identity structure, error fallback, semantics, group visibility and logical direction while consumer classes own every visual surface.

+1

Beta boundaries

Included

Images, initials, icons, projected fallback, native loading hints, error retry, sizes, shapes, badges, groups, overflow and headless ownership.

Application-owned

Upload, cropping, presence transport, profile fetching, interactive user menus and tooltip behavior remain separate components or application concerns.