پرش به مطلب اصلی

Video actions

StatusCurrent
OwnerAparat Product Team
Last verified2026-08-02 — Figma "AWD - Video Single", the single-video API mapping, the live product, and the support-centre article on reporting videos

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). Where the current live product differs from the design, both are noted.

Introduction & Purpose

Below the video sits the action bar — the controls a viewer uses to react to and pass along a video. This page documents each action and its dialog: Like, Share (including Embed), Save to a playlist, Download, Report, and the more options menu that groups the less-frequent actions.

Business goal: convert watching into engagement and distribution — likes and comments signal quality, sharing/embedding spreads reach, saving builds return visits, and reporting keeps content safe.

Scope

The Like/Share/Save/Download/Report actions and the “more options” menu, with their modals, fields, and validation. Following the channel is covered in Channel, title & description; commenting is covered in Comments.

Out of scope: the owner-only management actions that also appear in the more-options menu — edit video («ویرایش ویدئو»), view statistics («آمار بازدید»), add to showcase («افزودن به ویترین»), add cards («افزودن کارت به ویدئو»), create an ad from the video («ایجاد تبلیغ با ویدئو»), and delete («حذف ویدئو», confirmed with «آیا می‌خواهید این ویدئو را حذف کنید؟»). Those belong to the creator dashboard's video management and are only listed here so the menu's full contents are on record.

Audiences & Roles

The action bar is the same for everyone, but several actions require an account for a signed-out visitor. See the gating in each scenario and the hub roles.

Business Rules

  • BR-1 — Like, no dislike. A video has a Like action showing a count as «N نفر پسندیدند» (“N people liked”); there is no dislike control. The like is a toggle — pressing it again removes it.
  • BR-2 — Sign-in gating comes from the page's own configuration. The page is told which actions require an account; on the live product Like and Save to playlist are both marked as requiring one, as are Follow, Download and commenting. Share and opening the Report form do not. For a signed-out visitor the gated control leads to the sign-in modal instead of performing the action.
  • BR-3 — Share options. The Share dialog offers copy-link, a share-with-exact-start-time option, an embed path, and social targets. The start-time field is presented first because it is what distinguishes this dialog's main variant.
  • BR-4 — Embed settings before code. In the embed dialog, the settings that change the generated code are shown before the code, since they alter it. Three code shapes are offered — Script, iFrame and AMP — and the video additionally exposes a standard oEmbed description for third-party sites that discover embeds automatically.
  • BR-5 — Save is a playlist toggle. Saving adds the video to one of the viewer's playlists; the default list is Watch Later («بعدا می‌بینم»), and a viewer can create a new list during save. Each list shows a Private («خصوصی») badge when it is private, against Public («عمومی») otherwise. Selecting an already-saved list removes the video from it — there is no separate “unsave”.
  • BR-6 — Report requires a reason and a violation moment. The report form requires a reason chosen from a fixed list of 22, at least one violation timestamp («لحظه اول»), and a description. The description field enforces a maximum length (counter «۰ از ۵۰»).
  • BR-7 — Up to three violation timestamps. A report can carry a maximum of 3 moments («لحظه اول/دوم/سوم»). The first is mandatory, and the support centre adds that filling this section is mandatory for operators. A time entered incorrectly means the report is not reviewed.
  • BR-8 — A false report counts against the reporter. Aparat records a violation against a viewer who files an incorrect report, so the form is not a low-cost action.
  • BR-9 — Download offers the video's own quality ladder. Download is available only when the video permits it, and the qualities offered are the same renditions the player has, each labelled with its file size (e.g. «با کیفیت 720p» ≈ ۲۵.۸۲ مگابایت).

Scenarios

Scenario 1: Like a video

Purpose — the viewer expresses that they liked the video.

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

Preconditions — the viewer is on the watch page.

Main Flow

  1. The viewer clicks Like (shown as the count «N نفر پسندیدند», e.g. «۱۵۱،۹۸۶»). → The count increments and the control shows an active state.

Extensions — Alternative & Exception Flows

  • 1a. The viewer is signed out:
    • 1a1. The page's configuration marks liking as an account action, so the control leads to the sign-in modal. A previous live check saw a like register visually without a prompt; that is a client-side effect and is flagged as an open question, not documented as a guest capability.
  • 1b. The viewer clicks Like again:
    • 1b1. The like is toggled off and the count returns to its previous value.

Postconditions — the viewer's like state and the count are updated.

Scenario 2: Share or embed a video

Purpose — the viewer shares a link to the video, optionally from a chosen start time, or gets embed code.

Roles Involved — all viewers (no sign-in required).

Preconditions — the viewer is on the watch page.

Main Flow

  1. The viewer clicks Share («اشتراک‌گذاری» / «اشتراک»). → The Share dialog opens.
  2. The dialog offers, in order: Share from exact time («انتشار با زمان دقیق») — a checkbox with a Start video from («شروع ویدئو از») MM:SS input — then the video link («لینک ویدئو شما») with a Copy («کپی») button, an Embed code («کد امبد») entry, and social targets (BR-3).
    • Design social targets: Facebook («فیسبوک»), WhatsApp («واتس‌اپ»), Twitter/X («توییتر» / «ایکس (توییتر)»), LinkedIn («لینکدین»), Telegram («تلگرام»), Eitaa («ایتا»).
    • Currently on the live product the primary targets are Copy link («کپی لینک»), Link with exact time («لینک با زمان دقیق»), Get embed code («دریافت کد امبد»), Bale («بله»), Telegram («تلگرام»), and a More («بیشتر») expander revealing X («ایکس»), WhatsApp («واتساپ»), and Facebook («فیسبوک»).
  3. To embed, the viewer opens Embed («کد امبد» / «دریافت کد امبد»). → The embed dialog («تنظیمات امبد») opens with the settings shown before the code (BR-4).
  4. The embed dialog offers code-type tabs Script («کد Script»), iFrame («کد iFrame»), and AMP («کد AMP»), plus options: Show video title & player icons («نمایش تیتر ویدئو و آیکون های پلیر»), Start muted («پخش اولیه بی‌صدا باشد»), Show the channel's other videos at the end («نمایش ویدئوهای دیگر کانال شما در انتهای ویدئو»), and Start playback from («شروع پخش از») a time input. → The code updates to match; the viewer clicks Copy code («کپی کردن کد») or Cancel («انصراف»), and can Close («بستن»).

Extensions — Alternative & Exception Flows

  • 2a. The viewer enables Share from exact time and enters a start time:
    • 2a1. The generated link/embed opens the video at that timestamp — the link takes the form .../v/{video-id}:{m:ss}.
  • 2b. The viewer copies the link or embed code:
    • 2b1. The value is copied to the clipboard (the copy affordance confirms).
  • 2c. A third-party site pastes the plain video URL rather than the embed code:
    • 2c1. The video also publishes a standard oEmbed description, so sites that resolve embeds automatically can render the player without the viewer copying anything.

Postconditions — the viewer has a shareable link or embed code, optionally starting at a chosen time.

Scenario 3: Save a video to a playlist

Purpose — the viewer saves the video to watch later or organise it into a list.

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

Preconditions — the viewer is on the watch page.

Main Flow

  1. The viewer clicks Save («ذخیره در لیست پخش» / short label «ذخیره»). → The Save dialog «ذخیره در لیست پخش» opens and the viewer's lists are fetched.
  2. The dialog lists the viewer's playlists (default Watch Later «بعدا می‌بینم», plus the viewer's own lists such as «خرید‌ها», «آموزش UX», «بورد گیم», «گجت هوشمند»), each with a Private («خصوصی») badge where applicable and a check state showing whether this video is already in it, plus a Create new list («ایجاد لیست جدید» / «ایجاد لیست») option (BR-5).
  3. The viewer selects one or more lists. → The video is added to each and the dialog reflects the new state.

Extensions — Alternative & Exception Flows

  • 1a. The viewer is signed out:
    • 1a1. The sign-in modal opens instead of the Save dialog (BR-2).
  • 2a. (Mobile) The Save action opens as a bottom-sheet modal rather than a centered dialog.
  • 2b. The viewer creates a new list:
    • 2b1. The create-list form asks for Playlist title («عنوان لیست پخش», placeholder «یک عنوان برای لیست پخش خود وارد کنید.»), an optional description («توضیحات لیست پخش را اضافه کنید.») and a Publication status («وضعیت انتشار») of Public («انتشار عمومی») or private, then Create («ایجاد»). The video is saved into the new list.
  • 2c. The viewer selects a list the video is already in:
    • 2c1. The video is removed from that list — selection is a toggle, not an add-only action (BR-5).

Postconditions — the video appears in the selected list(s).

Scenario 4: Download a video

Purpose — the viewer downloads the video for offline viewing.

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

Preconditions — the viewer is on the watch page and the video permits download.

Main Flow

  1. The viewer opens more options («گزینه‌های بیشتر») and chooses Download video («دانلود ویدئو»). → The download list opens, offering each available rendition with its size (BR-9).
  2. The viewer picks a quality. → The file downloads.

Extensions — Alternative & Exception Flows

  • 1a. The viewer is signed out:
    • 1a1. The sign-in modal opens immediately; no quality picker is shown until the viewer signs in (observed on the live product).
  • 1b. The video does not permit download:
    • 1b1. The download entry is not offered. The permission is a per-video property, not a per-viewer one.
  • 1c. The video is still processing:
    • 1c1. Only the renditions that exist yet are listed — the full ladder appears once processing completes (see Playback BR-7).

Postconditions — the video is downloaded at the chosen quality.

Scenario 5: Report a video

Purpose — a viewer reports a video that violates the rules.

Roles Involved — all viewers (the report dialog opens without sign-in; whether submitting requires sign-in is unconfirmed).

Preconditions — the viewer is on the watch page.

Main Flow

  1. The viewer opens more options — the three-dot control under the player — and chooses Report violation («گزارش تخلف»). → The report dialog «گزارش تخلف ویدئو» opens.
  2. The viewer selects a Report reason («دلیل گزارش», required; placeholder «انتخاب کنید»). → The dropdown offers 22 reasons, in this order: fake news («اخبار جعلی»); national-security / anti-terrorism concerns («ملاحظات امنیت ملی یا ضد تروریسم»); inappropriate dress («پوشش نامناسب»); sexually provocative content («محتوای تحریک آمیز جنسی»); ethnic insult / racism («توهین به قومیت ها / محتوای نژادپرستی»); insult to religious minorities («توهین به اقلیت های مذهبی»); insult to political figures («اهانت به مقامات سیاسی»); violent or disturbing content («داشتن محتوای خشن یا زننده»); slander/defamation («تهمت و افترا»); harmful or dangerous activities («فعالیت‌های آسیب‌زا یا خطرناک»); hate speech / intimidation / threats («نفرت پراکنی، ارعاب و تهدید»); child abuse («کودک آزاری»); content inappropriate for children («محتوای نامناسب برای کودکان»); imitative or antisocial behavior («رفتار تقلیدی یا ضد اجتماعی»); misleading content («داشتن محتوای گمراه کننده»); conflicting with the country's norms/laws («مغایرت داشتن با شئونات یا قوانین کشور»); title/description not matching the video («مغایرت داشتن تیتر و توضیح با محتوای ویدئو»); privacy violation («عدم رعایت حریم خصوصی افراد»); copyright violation («عدم رعایت حق نشر»); unauthorized advertising use («استفاده تبلیغاتی غیرمجاز»); audio/video technical problem («مشکل فنی صدا یا تصویر»); other («سایر موارد»).
  3. The viewer enters the violation moment(s) («لحظه‌ وجود تخلف»). → First moment («لحظه اول», required, marked «(اجباری)», MM:SS) plus optional second («لحظه دوم») and third («لحظه سوم»). Helper text (quoted, with the section's «ویدئو» spelling applied): «دقیقه‌ای را که تخلف در آن زمان رخ داده، بنویسید تا امکان پیگیری آن باشد. (مثال ′۰:۱۲) اگر زمان به‌درستی وارد نشود، گزارش بررسی نمی‌شود. برای هر ویدئو، حداکثر امکان ثبت ۳ زمان تخلف وجود دارد.»
  4. The viewer writes a Report description («توضیحات گزارش»; placeholder «توضیحات تکمیلی مربوط به گزارش خود را در اینجا بنویسید.») up to the shown character limit (counter «۰ از ۵۰»).
  5. The viewer clicks Send report («ارسال گزارش»). → The report is queued for Aparat's moderators; the dialog can be dismissed with Cancel («انصراف»).

Extensions — Alternative & Exception Flows

  • 2a. No reason is selected (required):
    • 2a1. The form cannot be submitted until a reason is chosen.
  • 3a. The first violation moment is empty or wrongly formatted:
    • 3a1. Per the helper text, a report with an incorrect time is not reviewed; the field is required, and the support centre states it is mandatory for operators (BR-7).
  • 3b. The viewer wants to flag more than three moments:
    • 3b1. Only three fields exist; the viewer must choose the three most representative (BR-7).
  • 4a. The description is empty:
    • 4a1. The form cannot be submitted (required field).
  • 5a. The report turns out to be incorrect:
    • 5a1. Aparat records a violation against the reporter (BR-8), and repeated false reports also cost the reporter the ability to comment (see Comments).
  • 5b. Whether submitting requires sign-in, and the success/validation messages after submit:
    • 5b1. [CLARIFICATION NEEDED: the report dialog opens without sign-in, but submission (and its success/error messaging) was not exercised — confirm.]

Postconditions — the report is queued for review by Aparat.

Mobile & Tablet View

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

  • The Save and Share dialogs open as bottom sheets. The mobile Save control is not the desktop button; tapping it opens the save sheet directly.
  • The action row is compressed: Like («N نفر پسندیدند»), comments, and Save («ذخیره») appear as labelled controls, with Share and “more options” as icon-only buttons.
  • Report, Download, and Embed are reached through the mobile more options menu / details sheet.

Open Questions

  • 2026-08-02 — Guest Like. The page's configuration marks liking as requiring an account, yet a like link is issued even to an anonymous caller and a live check saw a like register visually with no prompt. Confirm which is authoritative and what a signed-out viewer should see (Scenario 1, 1a). — waiting on Product.
  • 2026-08-02 — Report submission. The reason list and the form ship with the page, but no capture has ever recorded the call that files a report, so nothing here describes what happens after Send report (Scenario 5, 5b). — waiting on Engineering.
  • 2026-08-02 — Report timestamp maximum. The design and the support centre both say 3; an earlier live check on a different video offered only 2. Confirm whether the limit varies by content type (BR-7). — waiting on Product.
  • 2026-07-21 — Live vs design share targets differ (Scenario 2, step 2). — waiting on Product.

Changelog

DateChangeSource
2026-08-02Rewritten. Like is now documented as an account action with the gating source named; the full 22-reason report list was re-confirmed against the live product; added the false-report penalty, the operator-mandatory timestamp rule, download sizes, the save-as-toggle rule, the create-list form, oEmbed, and the owner-only entries in the more-options menu. 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 + support centre
2026-07-21Initial version.Figma "AWD - Video Single" + live product