Channel, title & description

Status	Current
Owner	Aparat Product Team
Last verified	2026-08-02 — Figma "AWD - Video Single", the single-video API mapping, and the live product

Part of the Video Single page. UI labels are given as an English gloss followed by the Persian string in quotes; the quoted Persian is authoritative — except for the word video, which this documentation always spells «ویدئو» even where the screen shows «ویدیو» (see the language note).

Introduction & Purpose

Directly under the player, the page identifies what the viewer is watching (title, views, publish date, tags) and who made it (the channel), and lets the viewer follow that channel, turn on notifications for it, and read the video's description. This is where a viewer decides whether to keep following the creator and where the creator's context, links, hashtags and section list live.

Business goal: turn a one-off view into a lasting relationship with the channel (follows, then notifications) and give the creator space to describe and cross-link their content.

Scope

The title and meta row, the tag/hashtag chips, the channel row (name, avatar, follower count, verified badge), the Follow control and the notification bell, and the expandable description. The paid channel-subscription/gift flow is out of scope (see the hub).

Audiences & Roles

Reading the title, meta, and description is the same for everyone. Follow and the notification bell require an account — a signed-out visitor is routed to sign-in. See the hub roles.

Business Rules

• BR-1 — Title placement. The video title is the page's main heading (rendered as the top-level heading on desktop and a lower-level heading on mobile).
• BR-2 — Meta row. Below the title: the view count («N بازدید», e.g. «۵,۰۷۴ بازدید» or the rounded «۷.۵ هزار بازدید») and the relative publish date («N ماه پیش»). The exact publish date and time is also available and shown where there is room, in the Persian calendar (e.g. «08 تیر 1405 13:04»). A HD quality badge appears where applicable.
• BR-3 — Tags. Hashtag chips (e.g. «#آنباکسینگ», «#معرفی محصول», «#تکنولوژی») link to Aparat search for that tag. The chips show the creator's Persian tags; a transliterated variant of the same tags also exists in the data but is not displayed.
• BR-4 — Channel identity. The channel row shows the channel avatar and display name (e.g. «آشپزی باغ گیلاس»), the follower count («N دنبال‌کننده», e.g. «14.1 هزار»), and a verified badge when the channel is verified. The name shown is the channel's display name; its @username is what the channel URL uses.
• BR-5 — Follow states. The subscribe control has two states — Follow («دنبال کردن») when not following and Followed («دنبال شده») when following. Following requires sign-in, and the control resolves to the sign-in modal for a signed-out visitor.
• BR-6 — Description expand/collapse. The description is truncated with Show more («نمایش بیشتر»); once expanded it can be collapsed with Close description («بستن توضیحات...»). On mobile the expand label is «بیشتر...». The video's section list is rendered from this same description text and appears directly beneath it — see Playback & the player BR-12.
• BR-7 — Notifications are a second, separate opt-in. Following the channel and asking to be notified about it are two different states: the bell is toggled independently of the follow control, and turning follow off does not implicitly manage it. A viewer can therefore follow without notifications.
• BR-8 — Following is counted from this page. The follower count shown next to the channel updates as the viewer follows or unfollows, and the same count is what the channel's own surfaces show.
• BR-9 — Saved live streams are marked in the title row. A video that is the saved recording of a live broadcast is watched exactly like any other video, but carries a Saved live stream badge («پخش زنده ذخیره شده») beside its title. The badge is part of the title/meta block — it is not the Live badge («زنده») that marks a currently-broadcasting stream on a recommendation card (see Recommendations & playlists BR-4).

Scenarios

Scenario 1: Read the title, meta, and tags

Purpose — the viewer orients to what the video is and when it was published.

Roles Involved — all viewers.

Preconditions — the viewer is on the watch page.

Main Flow

1. The viewer reads the title at the top of the details area (BR-1). → Alongside it, the meta row shows the view count and relative publish date (BR-2), with an HD badge where applicable.
2. The viewer clicks a tag chip (e.g. «#شربت»). → Aparat search opens for that tag (BR-3).

Extensions — Alternative & Exception Flows

• 1a. The video is still processing:
  • 1a1. The meta shows «۰ بازدید» and a fresh time (see Playback & the player, Scenario 6).
• 1b. The viewer wants the exact publish moment rather than “6 months ago”:
  • 1b1. The exact date and time is shown under «تاریخ انتشار», on desktop inline and on mobile in the details sheet (BR-2).
• 1c. The video carries no tags:
  • 1c1. The chip row is omitted; nothing takes its place.

Postconditions — the viewer understands the video's identity and can pivot to a tag search.

Scenario 2: Follow (subscribe to) the channel

Purpose — the viewer follows the channel to see its future videos.

Roles Involved — signed-in viewers (a signed-out visitor is prompted to sign in).

Preconditions — the viewer is on the watch page and not already following.

Main Flow

1. The viewer clicks Follow («دنبال کردن») in the channel row. → The control switches to Followed («دنبال شده») and the follower count updates (BR-5, BR-8).
2. The viewer opts into notifications for the channel with the bell control. → The bell switches to its on state (BR-7).

Extensions — Alternative & Exception Flows

• 1a. The viewer is signed out:
  • 1a1. The sign-in modal opens instead of following. After signing in the viewer returns to this video with the follow applied.
• 1b. The viewer clicks Followed to unfollow:
  • 1b1. The control returns to Follow and the count decreases.
• 1c. The channel is verified:
  • 1c1. A verification badge is shown next to the channel name (BR-4).
• 2a. The viewer follows but leaves the bell off:
  • 2a1. The channel appears in the viewer's followed channels without sending notifications — the two states are independent (BR-7).
• 2b. The viewer is the channel owner:
  • 2b1. No follow control is offered on one's own video.

Postconditions — the viewer's follow state, notification state, and the channel's follower count are updated.

Scenario 3: Read the full description

Purpose — the viewer reads the creator's description and any links, hashtags or sections in it.

Roles Involved — all viewers.

Preconditions — the viewer is on the watch page and the description is truncated.

Main Flow

1. The viewer clicks Show more («نمایش بیشتر») on the description. → The full text expands inline, including any hashtags and links (BR-6).
2. The viewer reads the section list rendered beneath the description, if the creator wrote one.
3. The viewer clicks Close description («بستن توضیحات...») (on mobile «بیشتر...» toggles it). → The description collapses back to its truncated form.

Extensions — Alternative & Exception Flows

• 1a. The description is short enough to fit:
  • 1a1. No “show more” control is shown.
• 2a. The description contains no section lines:
  • 2a1. No section list is rendered; the description behaves as ordinary text (see Playback & the player, Scenario 4).

Postconditions — the viewer has read as much of the description as they want.

Mobile & Tablet View

Only the differences from desktop (see the hub Mobile & Tablet View):

• The title renders as a lower-level heading; the meta and description move into the single column.
• A details sheet surfaces the meta as a bottom sheet: Like («پسند»), publish date («تاریخ انتشار»), views («بازدید»), Description («توضیحات»), Report («گزارش»), and More («بیشتر...»).
• The Follow control appears in the channel row and, on the mobile playlist/open-app surfaces, as Follow («دنبال کردن»).

Open Questions

• 2026-08-02 — Verified vs brand. The channel carries both a verification flag and a priority/brand marker. Which drives the badge, and whether “brand” changes anything else on this page, is not recorded. — waiting on Product.
• 2026-08-02 — Bell placement on mobile. The notification opt-in is a distinct state (BR-7), but the mobile design does not clearly show where it sits when the channel row is compressed. — waiting on Design.

Changelog

Date	Change	Source
2026-08-02	Rewritten. Added the notification bell as a separate opt-in from following (previously undocumented), the exact publish date alongside the relative one, the display-name/username distinction, the tag-data note, the link from the description to the section list, and the saved-live-stream badge (BR-9), relocated here from the recommendations page because the design places it beside the title. Added a machine-readable endpoint-context block to the page's front matter, for developers who read this repository rather than the site.	Design contracts + Figma + live product
2026-07-21	Initial version.	Figma "AWD - Video Single" + live product