| Layer | Detail |
|-------|--------|
| Front‑end | React component <LinkVideoImporter />; uses React Hook Form for validation; fetches metadata via axios to backend; player powered by Video.js (HLS/DASH) with caption plugin. |
| Back‑end | Node.js (Express) micro‑service link-video-service.
• Endpoint: POST /api/v1/video/from‑link
• Validates URL, selects appropriate provider adapter (YouTube, Vimeo, TikTok, etc.).
• Calls provider APIs (YouTube Data API v3, Vimeo oEmbed, TikTok public endpoint) to obtain embed URL and metadata.
• Stores minimal record in link_videos table (id, user_id, source_url, title, duration, thumbnail_url, embed_url, created_at). |
| Provider Adapters | Separate module per host (youtubeAdapter.js, vimeoAdapter.js, …). Handles OAuth token renewal (if needed), rate‑limit handling, and fallback to public oEmbed when possible. |
| Caching | Redis cache (TTL 12 h) for metadata to avoid repeated API calls on the same URL. |
| Security | • URL sanitisation (DOMPurify).
• CSP frame-src whitelist includes approved video host domains.
• Rate limiting via express‑rate‑limit (10 requests/min per IP). |
| Storage | PostgreSQL table link_videos. Only store non‑personal data. |
| Analytics | Emit events to our analytics pipeline: video_link_import_started, video_link_import_success, video_playback_started, video_saved. |
| Testing | • Unit tests for adapters (Jest).
• Integration tests for the API (Supertest).
• E2E tests (Cypress) covering the full UI flow. |
| CI/CD | Pipeline adds a new job link-video-service-test and deploys to staging behind feature flag ff_video_link_import. |
Enable users to paste any supported video URL (e.g., a “Mujer con un perro se queda pegada” link) and instantly stream the full video inside our app, with preview, captions, attribution, and the option to save it—all while respecting copyright, privacy, and accessibility standards.
Allow a user to paste any video URL (YouTube, Vimeo, Dailymotion, TikTok, Instagram Reels, etc.) into a “Play from Link” widget. The system will:
The specific use‑case “Mujer con un perro se queda pegada” will be handled like any other video – the system does not embed the content itself but streams it from the source, respecting the source’s terms of service. mujer con un perro se queda pegada videos completos de link
| Phase | Activities | Timeline | |-------|------------|----------| | Discovery & Design | Finalise UI mock‑ups, provider adapter list, legal review. | 2 weeks | | Implementation | Front‑end component, back‑end service, adapters, caching. | 4 weeks | | Testing | Unit, integration, E2E, accessibility audit. | 2 weeks | | Beta Rollout | Enable feature for 5 % of users (feature flag). Gather telemetry, fix bugs. | 1 week | | Full Launch | Ramp to 100 % users, update help docs, send release note email. | 1 week | | Post‑Launch | Monitor metrics, address edge‑case provider changes. | Ongoing (first 4 weeks) |
| ID | Condition | Test | |----|-----------|------| | AC‑01 | URL validation rejects unsupported hosts or malformed URLs and displays a clear error message. | Unit test with whitelist/blacklist matrix. | | AC‑02 | Metadata fetch returns title, duration, thumbnail, and a safe‑to‑embed embed‑URL within 3 seconds. | Mock API calls to each provider; measure latency. | | AC‑03 | Playback starts after user clicks “Play” and shows a loading spinner if buffering > 2 seconds. | End‑to‑end test on Chrome/Firefox/Safari mobile. | | AC‑04 | Responsive player respects container width, supports picture‑in‑picture, fullscreen, and captions toggle. | UI regression on breakpoints (320‑2560 px). | | AC‑05 | Saving a video adds an entry in the user’s “Link‑imported” collection with source URL and timestamp. | Database entry verification. | | AC‑06 | Attribution appears below the player (source name, link, license badge). | Visual inspection and schema validation. | | AC‑07 | Reporting opens the standard report modal pre‑filled with source URL. | UI flow test. | | AC‑08 | Accessibility – All interactive elements have ARIA labels; captions are selectable via keyboard. | WCAG 2.1 AA audit. | | AC‑09 | Rate limiting – No more than 10 link fetches per user per minute. | Load test with simulated bots. | | AC‑10 | Privacy – No personally‑identifiable data from the source site is stored beyond URL, metadata, and optional user‑saved flag. | GDPR compliance checklist. |
Title: “Full‑Video Playback for “Mujer con un perro se queda pegada” (Link‑Based Retrieval) | Layer | Detail | |-------|--------| | Front‑end
Feature Tag: VIDEO_LINK_IMPORT
Target Release: v2.5 (Q4 2026)
Users often discover a video they want to watch (e.g., “mujer con un perro se queda pegada”) via a URL shared on social media, messaging apps, or forums.
Current workflow forces them to: Enable users to paste any supported video URL (e
Result: Friction, abandonment, and a poorer user‑experience.
| Requirement | Detail | |-------------|--------| | Performance | Metadata fetch ≤ 3 s; video start ≤ 2 s after play click. | | Scalability | Service stateless; can be horizontally scaled behind a load balancer. | | Reliability | 99.9 % uptime SLA for the micro‑service; fallback to cached metadata if provider API fails. | | Compliance | Must honor each provider’s Terms of Service (no downloading, only streaming). | | Privacy | GDPR‑compliant: no tracking of user’s external URLs beyond the session; ability to delete all link‑import records on request. | | Accessibility | WCAG 2.1 AA – captions, keyboard navigation, ARIA labels, focus management. | | Internationalization | UI strings translatable; default language Spanish (es) with fallback to English (en). | | Logging & Monitoring | Structured logs (JSON) with request ID, response status; alerts on error‑rate > 2 % for any provider. |