<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: amer kasem</title>
    <description>The latest articles on DEV Community by amer kasem (@amer_kasem_49e31ccb43f4c9).</description>
    <link>https://dev.to/amer_kasem_49e31ccb43f4c9</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4204513%2F2a0bb029-95b4-4b9c-b362-431007a37998.png</url>
      <title>DEV Community: amer kasem</title>
      <link>https://dev.to/amer_kasem_49e31ccb43f4c9</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/amer_kasem_49e31ccb43f4c9"/>
    <language>en</language>
    <item>
      <title>The Easiest Way to Update SaaS Video Docs Without Re-Recording Your Screen</title>
      <dc:creator>amer kasem</dc:creator>
      <pubDate>Wed, 18 Nov 2026 22:27:26 +0000</pubDate>
      <link>https://dev.to/amer_kasem_49e31ccb43f4c9/the-easiest-way-to-update-saas-video-docs-without-re-recording-your-screen-28g3</link>
      <guid>https://dev.to/amer_kasem_49e31ccb43f4c9/the-easiest-way-to-update-saas-video-docs-without-re-recording-your-screen-28g3</guid>
      <description>&lt;p&gt;Your product ships every sprint. Your tutorial videos don’t. Within a few releases, the button in the video has moved, the menu has a new name, and customers who follow along get lost. This guide explains why that keeps happening, what today’s tools do about it, and a different approach: &lt;strong&gt;write your tutorial videos instead of recording them&lt;/strong&gt;, so updating one is a matter of editing a line and pressing Render.&lt;/p&gt;

&lt;h2&gt;
  
  
  The problem: video docs go stale faster than text docs
&lt;/h2&gt;

&lt;p&gt;Text documentation is easy to fix. Someone opens the help article, changes a sentence, and saves. Video documentation doesn’t work that way. A tutorial video is a recording of one moment in your product’s life, and the moment your UI changes, the recording is wrong.&lt;/p&gt;

&lt;p&gt;Fixing it usually means doing the whole thing again:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Prepare a clean demo account with believable data.&lt;/li&gt;
&lt;li&gt;Close notifications, hide bookmarks, set the right window size.&lt;/li&gt;
&lt;li&gt;Click through the flow by hand — and start over after one mis-click or an unexpected popup.&lt;/li&gt;
&lt;li&gt;Record the voice-over, or re-record it because one sentence changed.&lt;/li&gt;
&lt;li&gt;Edit, add captions, export, upload, replace the old link.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Multiply that by every lesson that touches the screen you just redesigned. Most teams can’t afford it, so the videos quietly fall out of date. Customers notice, trust the docs less, and open a support ticket instead. The videos meant to reduce support load end up creating it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The real cost isn’t making the first video.&lt;/strong&gt; It’s keeping fifty videos correct across fifty releases.&lt;/p&gt;

&lt;h2&gt;
  
  
  What “record once” tools fix — and what they don’t
&lt;/h2&gt;

&lt;p&gt;A new generation of tools promises that you only need to record once. You click through a flow a single time, and AI turns that capture into a polished result: a generated script, a synthetic voice, zoom effects, captions, sometimes a step-by-step written guide.&lt;/p&gt;

&lt;p&gt;That is a real improvement over editing raw recordings by hand. But look closely at the workflow and one thing hasn’t changed: &lt;strong&gt;a person still has to click through your product&lt;/strong&gt; to create the source material. And when your UI changes, that capture no longer matches your product. Depending on the tool, you either record the flow again or patch screenshots one by one.&lt;/p&gt;

&lt;p&gt;“Record once” moves the work around. It doesn’t remove the recording, and it doesn’t solve the update problem.&lt;/p&gt;

&lt;h2&gt;
  
  
  A different approach: write the video, let a browser perform it
&lt;/h2&gt;

&lt;p&gt;DashCast takes the human out of the recording completely. Instead of capturing your screen, you describe the video as a &lt;strong&gt;scenario&lt;/strong&gt;: what the narrator says, and what happens on screen while they say it — where to click, what to type, what to highlight or zoom into.&lt;/p&gt;

&lt;p&gt;When you press Render:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;The voice comes first.&lt;/strong&gt; Your narration is turned into natural AI speech, with timing for every word.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;An automated browser records the scenes.&lt;/strong&gt; It opens your web app, signs in with a test account, and performs every action in sync with the voice — with a smooth cursor, zooms and highlights.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Subtitles are timed word by word&lt;/strong&gt; and everything is assembled into a finished video.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;You review it and publish&lt;/strong&gt; it to a page for your customers in one click.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Nobody touches the mouse or a microphone. And because the video comes from a script, &lt;strong&gt;it can be produced again at any time&lt;/strong&gt; — the same way, with the same quality — against the current version of your product.&lt;/p&gt;

&lt;h2&gt;
  
  
  Three ways to get a scenario
&lt;/h2&gt;

&lt;p&gt;A scenario isn’t only for developers. Paste your site link and let DashCast’s AI write it, let the AI tool you already use write it from your code, or design it yourself in the Scene Designer — or combine them: the AI drafts, you fine-tune.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. Paste your site link&lt;/strong&gt;DashCast’s AI signs in with your test account, reads your pages, writes the scenario and checks every click on your real site.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Your AI coding assistant&lt;/strong&gt;Copy a ready-made prompt into the AI tool you already use in your project. It reads your routes, templates and buttons and writes the scenario — or a whole series.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Scene Designer&lt;/strong&gt;A montage-style editor. Hear the real voice, see each scene’s screen, and pin actions to the exact spoken word they should happen on.&lt;/p&gt;

&lt;h3&gt;
  
  
  Your site link: AI writes and checks the lesson
&lt;/h3&gt;

&lt;p&gt;Give DashCast your site link, a test login and one sentence about what the lesson should explain. Its AI signs in, reads up to 15 pages of your app, writes every scene and then checks each click on your real site, fixing anything it cannot find. It usually takes a couple of minutes, and the result opens in the Scene Designer, ready to fine-tune or render. &lt;a href="https://dashcast.net/blog/ai-tutorial-video-from-website-link" rel="noopener noreferrer"&gt;See how it works&lt;/a&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  Your AI assistant: not even the script
&lt;/h3&gt;

&lt;p&gt;The fastest way is not to write the scenario at all. DashCast generates a prompt describing exactly how scenarios work. You paste it into the AI coding tool you already use inside your project folder. Because that tool can read your code — routes, templates, element IDs, demo accounts — it writes selectors that actually match your screens and narration that describes what is really there. For a whole course, it can write a single file with many lessons, which you import in one step. After a failed render, the prompt includes the errors from the last run, so the assistant can return a corrected file.&lt;/p&gt;

&lt;h3&gt;
  
  
  Scene Designer: edit like a video, not like a form
&lt;/h3&gt;

&lt;p&gt;Some people think in timing: “the click should happen exactly when I say &lt;em&gt;Export&lt;/em&gt;.” Scene Designer shows each scene as a track with the generated voice, the words laid out in time, and a snapshot of the screen. You drag actions along the track, preview the voice, and turn on &lt;em&gt;Pin to words&lt;/em&gt; so an action stays attached to its word even if you rewrite the sentence around it. “Pick on screen” lets you choose an element just by clicking it, and &lt;strong&gt;Load preview&lt;/strong&gt; captures your real screens and flags any button it can no longer find — before you render.&lt;/p&gt;

&lt;h3&gt;
  
  
  Under the hood: a short text file
&lt;/h3&gt;

&lt;p&gt;For the technically curious: every video is stored as a short text file (YAML) — you never have to touch it. Here is a complete scene:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="na"&gt;scenes&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
  &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="na"&gt;url&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;/invoices&lt;/span&gt;
    &lt;span class="na"&gt;login_as&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;admin&lt;/span&gt;
    &lt;span class="na"&gt;narrate&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;|&lt;/span&gt;
      &lt;span class="s"&gt;Open Invoices and press New invoice.&lt;/span&gt;
      &lt;span class="s"&gt;Pick a customer, add a line, and save. That's it.&lt;/span&gt;
    &lt;span class="na"&gt;actions&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
      &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="s"&gt;at:&lt;/span&gt; &lt;span class="mf"&gt;1.0&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;do:&lt;/span&gt; &lt;span class="s"&gt;click&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;     &lt;span class="s"&gt;target:&lt;/span&gt; &lt;span class="s2"&gt;"#btn-new"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
      &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="s"&gt;at:&lt;/span&gt; &lt;span class="mf"&gt;3.2&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;do:&lt;/span&gt; &lt;span class="s"&gt;type&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;      &lt;span class="s"&gt;target:&lt;/span&gt; &lt;span class="s2"&gt;"#customer"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;value:&lt;/span&gt; &lt;span class="s2"&gt;"Lisbon Coffee Roasters"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
      &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="s"&gt;at:&lt;/span&gt; &lt;span class="mf"&gt;5.0&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;do:&lt;/span&gt; &lt;span class="s"&gt;blur&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;      &lt;span class="s"&gt;target:&lt;/span&gt; &lt;span class="s2"&gt;".customer-email"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
      &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="s"&gt;at:&lt;/span&gt; &lt;span class="mf"&gt;6.4&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;do:&lt;/span&gt; &lt;span class="s"&gt;highlight&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;target:&lt;/span&gt; &lt;span class="s2"&gt;".total"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;for:&lt;/span&gt; &lt;span class="mi"&gt;2&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
      &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="s"&gt;at:&lt;/span&gt; &lt;span class="mf"&gt;8.0&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;do:&lt;/span&gt; &lt;span class="s"&gt;click&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;     &lt;span class="s"&gt;target:&lt;/span&gt; &lt;span class="s2"&gt;"button[type=submit]"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;It reads almost like a storyboard: a page, a narration, and a list of timed actions. Because it’s plain text, you can keep it in Git next to your code and review a change to a video the same way you review a change to the product.&lt;/p&gt;

&lt;h2&gt;
  
  
  Updating a video when your UI changes
&lt;/h2&gt;

&lt;p&gt;This is where writing beats recording. Say the next release renames the “New invoice” button and gives it a new ID. With a recording, that lesson has to be redone. With a scenario, the change is one line:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;  &lt;span class="na"&gt;actions&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
&lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="na"&gt;  - { at&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;1.0, do: click, target: "#btn-new" }&lt;/span&gt;
&lt;span class="na"&gt;+   - { at&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;1.0, do: click, target: "[data-action=create-invoice]" }&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Press Render, and the browser performs the lesson again on the new UI, with the same voice, pace and look. If the wording changed too, edit the sentence; the voice and subtitles are regenerated to match. Several lessons can render in parallel, so refreshing a whole library after a big redesign is an afternoon of edits, not weeks of re-recording.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Tip:&lt;/strong&gt; give the important buttons in your app stable attributes such as &lt;code&gt;data-test&lt;/code&gt; or &lt;code&gt;data-action&lt;/code&gt;. Your scenarios — and your end-to-end tests — will survive redesigns without any change at all.&lt;/p&gt;

&lt;h2&gt;
  
  
  How DashCast compares with existing tools
&lt;/h2&gt;

&lt;p&gt;Every tool below is good at something. The question is which job you’re hiring it for. If the job is &lt;em&gt;a library of product tutorials that stays correct after every release&lt;/em&gt;, the deciding question is: &lt;strong&gt;what do you have to do when the UI changes?&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Approach&lt;/th&gt;
&lt;th&gt;Who performs the clicks&lt;/th&gt;
&lt;th&gt;Voice &amp;amp; subtitles&lt;/th&gt;
&lt;th&gt;When the UI changes&lt;/th&gt;
&lt;th&gt;Best for&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Screen recorderse.g. Loom, Camtasia&lt;/td&gt;
&lt;td&gt;You, live, every time&lt;/td&gt;
&lt;td&gt;Your own microphone; captions added afterwards&lt;/td&gt;
&lt;td&gt;Record the video again&lt;/td&gt;
&lt;td&gt;Quick one-off explanations and async messages&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;“Record once” AI toolse.g. Guidde, Scribe, Trupeer, Clueso&lt;/td&gt;
&lt;td&gt;You, once per version of the flow&lt;/td&gt;
&lt;td&gt;AI voice and captions generated from your capture&lt;/td&gt;
&lt;td&gt;Capture the flow again, or patch steps by hand&lt;/td&gt;
&lt;td&gt;Polishing a recording into a guide or video quickly&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Interactive demo builderse.g. Arcade, Supademo, Storylane&lt;/td&gt;
&lt;td&gt;You, once, to capture the screens&lt;/td&gt;
&lt;td&gt;Mostly text callouts; voice optional&lt;/td&gt;
&lt;td&gt;Recapture the affected screens&lt;/td&gt;
&lt;td&gt;Clickable marketing demos and product tours&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;AI avatar videoe.g. Synthesia, HeyGen&lt;/td&gt;
&lt;td&gt;Nobody — but product screens must still be recorded and inserted&lt;/td&gt;
&lt;td&gt;AI presenter and voice&lt;/td&gt;
&lt;td&gt;Re-record the screen parts, regenerate&lt;/td&gt;
&lt;td&gt;Presenter-led training and announcements&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;DashCastscripted browser automation&lt;/td&gt;
&lt;td&gt;Nobody — an automated browser, from your scenario&lt;/td&gt;
&lt;td&gt;AI voice and word-synced subtitles, generated together&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;Edit a line, press Render&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Tutorial libraries for web software that changes often&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;To be fair about the limits: DashCast records &lt;strong&gt;web applications&lt;/strong&gt; — anything that opens in a browser. If you need to film a desktop or mobile app, or you want a quick, personal walkthrough with your own face and voice, a screen recorder is still the right tool. And if your goal is a clickable demo on a marketing site, interactive demo builders are made for exactly that.&lt;/p&gt;

&lt;h2&gt;
  
  
  What you get, beyond not recording
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Consistent quality.&lt;/strong&gt; Same resolution, pace, cursor and voice in every lesson — the library looks like one product, not twenty recording sessions.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A clean frame.&lt;/strong&gt; No notifications, browser tabs or desktop clutter — only your system.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Privacy by default.&lt;/strong&gt; The browser signs in with a test account whose password never appears in the video or the scenario, and a blur action hides private fields before they reach the screen.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Many languages from one workflow.&lt;/strong&gt; Narration and subtitles in 14 languages, so you can serve customers in their own language without hiring voice talent.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Less support load.&lt;/strong&gt; When the video is always right, you can answer a ticket with a link instead of a paragraph.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Faster onboarding.&lt;/strong&gt; New customers and new staff get short, accurate lessons for every screen from day one.&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://dashcast.net/blog/update-saas-video-docs-without-re-recording" rel="noopener noreferrer"&gt;dashcast.net&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>video</category>
      <category>tutorial</category>
      <category>saas</category>
      <category>productivity</category>
    </item>
    <item>
      <title>How to Make a Software Tutorial Video for Free</title>
      <dc:creator>amer kasem</dc:creator>
      <pubDate>Thu, 05 Nov 2026 13:24:04 +0000</pubDate>
      <link>https://dev.to/amer_kasem_49e31ccb43f4c9/how-to-make-a-software-tutorial-video-for-free-2an6</link>
      <guid>https://dev.to/amer_kasem_49e31ccb43f4c9/how-to-make-a-software-tutorial-video-for-free-2an6</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fsvlvmrt3dbmsv2t42qns.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fsvlvmrt3dbmsv2t42qns.jpg" alt=" " width="800" height="420"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;A tutorial video for your software does not have to cost money. But “free” often hides the real price: a free screen recorder still needs you to record, retake, cut, narrate and export, and that is an afternoon for a few minutes of video. This guide shows how to get a finished, narrated tutorial video for free, without recording anything, and how far the free minutes go.&lt;/p&gt;

&lt;p&gt;What “free” usually means&lt;br&gt;
Free option What you get    What it still costs you&lt;br&gt;
Built-in screen recorder    A raw recording of your screen  Retakes, editing, your own voice, no subtitles&lt;br&gt;
Free plan of a recording tool   Recording plus simple sharing   Often a watermark or a time limit, and you still record&lt;br&gt;
Free video editor   Cuts, text and music    You need a recording first, and time to learn the editor&lt;br&gt;
DashCast free account   A finished video: clicks, voice, subtitles  Your site must open in a browser over the internet&lt;br&gt;
What the free DashCast account includes&lt;br&gt;
10 minutes of video, with no credit card, and 5 more minutes after your first video is finished.&lt;br&gt;
The AI writer: Write it for me automatically for 3 lessons a day.&lt;br&gt;
AI voice and subtitles in 14 narration languages.&lt;br&gt;
The Scene Designer to edit the narration and the clicks.&lt;br&gt;
Desktop or Mobile videos, and MP4 and subtitle downloads.&lt;br&gt;
Free re-renders on every video, and a failed render is never charged.&lt;br&gt;
Most software tutorials are one to three minutes long, so 15 free minutes are enough for several real lessons, not just a test.&lt;/p&gt;

&lt;p&gt;Step by step: your first free tutorial video&lt;br&gt;
Create a free account. No credit card.&lt;br&gt;
Start a new video and choose its type: Tutorial for one task, Onboarding for a first tour.&lt;br&gt;
Choose Write it for me automatically. Paste your site link, a test login if the page needs one, and one sentence about the lesson, for example “Show how to create an invoice and send it to a customer.”&lt;br&gt;
Pick the language and Desktop or Mobile.&lt;br&gt;
Read the result in the Scene Designer. The AI writes the narration and the clicks and checks every click on your site. Change any word you like.&lt;br&gt;
Render. You get a notification and an email when the video is ready. Download it with ⬇ Video.&lt;br&gt;
Want to see a result before you sign up? Use Try it live on the home page: it renders a real demo, no account needed.&lt;/p&gt;

&lt;p&gt;How to make the free minutes go further&lt;br&gt;
One task per video. Short videos are watched more and use fewer minutes.&lt;br&gt;
Press 🔍 Check selectors before rendering. A check walks through the clicks without voice or recording, so you catch a broken step before it costs a render.&lt;br&gt;
Start with your most asked question. The lesson your support team explains every day pays back first.&lt;br&gt;
Fix, do not redo. After a change, render the same video again: re-renders are free, and only the changed scenes count after them.&lt;br&gt;
When you need more&lt;br&gt;
When the free minutes run out, nothing is charged by itself. You can buy a 100-minute pack for $5, valid for 60 days, or choose a plan from $9 a month. Pro and Business also add team seats and priority in the render queue. The voice, subtitles and every language are always included.&lt;/p&gt;

&lt;p&gt;Free does not have to mean out of date&lt;br&gt;
A free recording becomes a problem the day your product changes. A DashCast video is a script, so after an update you press 🔍 Check selectors, fix the steps it lists, and render again. More in updating video docs without re-recording, and see six types of software videos to choose what to make first.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>tutorial</category>
      <category>web</category>
      <category>saas</category>
    </item>
    <item>
      <title>I Let Claude Code Write a 20-Lesson Tutorial Course for My App From Its Codebase</title>
      <dc:creator>amer kasem</dc:creator>
      <pubDate>Sat, 31 Oct 2026 21:00:51 +0000</pubDate>
      <link>https://dev.to/amer_kasem_49e31ccb43f4c9/i-let-claude-code-write-a-20-lesson-tutorial-course-for-my-app-from-its-codebase-4o1d</link>
      <guid>https://dev.to/amer_kasem_49e31ccb43f4c9/i-let-claude-code-write-a-20-lesson-tutorial-course-for-my-app-from-its-codebase-4o1d</guid>
      <description>&lt;p&gt;I build dashboards. Admin panels, reports, forms, the usual things people need at work. Writing them is the part I enjoy. Explaining them is the part I don't.&lt;/p&gt;

&lt;p&gt;Every project ended the same way: "how do I add a product?", "where is the monthly export?", the same screen share again for each new person on the client's side. I knew I should make tutorial videos, but recording them meant a quiet room, a clean screen, retakes every time I misclicked, and then the next release would make half of them wrong.&lt;/p&gt;

&lt;p&gt;So I tried something else. I opened Claude Code in my project folder and gave it one prompt asking it to write a tutorial series for the app. It already had the whole codebase in front of it: every page, every button label, every role, every form field. It came back with a series of more than 20 lessons. I imported that reply once into DashCast, the tool I've been building for this, and each lesson became a narrated video with clicks, zooms and subtitles. I didn't record anything.&lt;/p&gt;

&lt;p&gt;  &lt;iframe src="https://www.youtube.com/embed/ky1DhxrzGWk" width="710" height="399"&gt;
  &lt;/iframe&gt;
&lt;/p&gt;

&lt;p&gt;That changed how I think about tutorial videos, so here is what I learned, and what the tool does and doesn't do.&lt;/p&gt;

&lt;h2&gt;
  
  
  The AI in your project already knows your app
&lt;/h2&gt;

&lt;p&gt;The coding assistant you already use has read your routes, templates and labels. That makes it a good author for "how to use this" lessons, better than anything looking at your app from the outside.&lt;/p&gt;

&lt;p&gt;The flow is: DashCast gives you a prompt, you paste it into Claude Code, Cursor or any AI tool opened in your project folder, and you paste its reply back. A series is imported in one step. Rendering still happens lesson by lesson.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Your source code doesn't leave your machine. The prompt runs in your own tool, and DashCast only receives the finished lessons.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  No repo? Start from a link
&lt;/h2&gt;

&lt;p&gt;Sometimes the app isn't yours: a client's system, a third-party tool, an old project you no longer have the code for. In that case you give DashCast a link, a test login and one sentence about the video you want. A built-in AI writer explores the screens, writes the lesson and checks each click before you render. It is limited to 3 lessons a day on a free account and 10 on paid plans.&lt;/p&gt;

&lt;h2&gt;
  
  
  A script, not a recording
&lt;/h2&gt;

&lt;p&gt;This is the part that mattered most to me. A recorded video is frozen on the day you record it. A lesson here is a script: what the voice says and what happens on screen at each moment.&lt;/p&gt;

&lt;p&gt;When a button moves or a menu gets renamed, you change that one step and render again. The voice, the timing and the rest of the lesson stay the same, and only the lessons that changed need a new render.&lt;/p&gt;

&lt;p&gt;If you want finer control, there's a timeline view (the Scene Designer) that shows the narration word by word with the actions on their own track. You drag a click to the word where it should happen.&lt;/p&gt;

&lt;h2&gt;
  
  
  Checking which lessons a release broke
&lt;/h2&gt;

&lt;p&gt;After a deploy, there's a "Check selectors" button on each lesson. In about a minute it lists every button and field the lesson can no longer find on the live app. I use it as a quick way to see which parts of the UI a release actually changed, before a user watches an outdated video.&lt;/p&gt;

&lt;h2&gt;
  
  
  Other things I use it for
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Client handover.&lt;/strong&gt; Instead of a call after delivery, I hand over a short course with the code: "How to add a product", "How to approve an order", "How to export the monthly report". It's also something you can list in a quote.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Release videos.&lt;/strong&gt; People skip changelogs but will watch 60 seconds of a new feature. There's a "What's new" video type for that.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Support answers.&lt;/strong&gt; One common ticket, one video under a minute, sent as a link instead of a long reply.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A launch video for your own product.&lt;/strong&gt; The "Marketing" type makes a 30 to 60-second video that talks about outcomes rather than buttons.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Logins and sensitive data
&lt;/h2&gt;

&lt;p&gt;Most of what users need to learn is behind a login. Lessons sign in with a test account before recording starts, so the password never shows up in the video or the narration. Fields like emails, phone numbers or amounts can be blurred. I use a test account with sample data so the videos show what a real user sees without exposing anything real.&lt;/p&gt;

&lt;h2&gt;
  
  
  Languages
&lt;/h2&gt;

&lt;p&gt;The same lesson can be rendered in 14 languages: English, Arabic, French, German, Spanish, Italian, Portuguese, Dutch, Russian, Turkish, Indonesian, Persian, Urdu and Hindi. The clicks stay the same and only the narration changes. Arabic, Persian and Urdu get right-to-left subtitles. Each video downloads as an MP4 with its subtitle file. Chinese, Japanese and Korean narration aren't available yet.&lt;/p&gt;

&lt;h2&gt;
  
  
  Teams
&lt;/h2&gt;

&lt;p&gt;On the Pro and Business plans a team shares one workspace with admin, editor and viewer roles. Pro has 2 seats and Business has 5.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it costs
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Option&lt;/th&gt;
&lt;th&gt;Price&lt;/th&gt;
&lt;th&gt;Video minutes&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Free sign-up&lt;/td&gt;
&lt;td&gt;$0, no card&lt;/td&gt;
&lt;td&gt;10, plus 5 after your first video&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Minute pack&lt;/td&gt;
&lt;td&gt;$5&lt;/td&gt;
&lt;td&gt;100, valid 60 days&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Starter&lt;/td&gt;
&lt;td&gt;$9 / month&lt;/td&gt;
&lt;td&gt;300&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Pro&lt;/td&gt;
&lt;td&gt;$19 / month&lt;/td&gt;
&lt;td&gt;1,000, 2 seats&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Business&lt;/td&gt;
&lt;td&gt;$49 / month&lt;/td&gt;
&lt;td&gt;3,000, 5 seats&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;You pay for rendered minutes. Voice, subtitles and languages are included, writing lessons with your own AI tool costs nothing extra, and failed renders aren't charged.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where it doesn't fit
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;It records web apps in a browser. It doesn't do desktop or mobile apps.&lt;/li&gt;
&lt;li&gt;It isn't for talking-head videos of yourself.&lt;/li&gt;
&lt;li&gt;If your UI changes completely, you'll still be rewriting lessons. Small changes are cheap; redesigns aren't free.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Do I need video editing skills?&lt;/strong&gt;&lt;br&gt;
No. You describe the video, the AI writes the lesson, and you get a finished MP4 with voice, subtitles, clicks and zooms. If you want to adjust timing, the Scene Designer works like a simple timeline.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Does DashCast see my source code?&lt;/strong&gt;&lt;br&gt;
No. When you use your own AI tool, the prompt runs on your machine inside your project folder, and DashCast receives only the finished lessons. You can also skip the code entirely and start from a link to your app.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Does it work with my stack?&lt;/strong&gt;&lt;br&gt;
It works with any web app that opens in a browser, whatever it's built with: Laravel, Django, Rails, Node, React, Vue, WordPress and so on. It doesn't record desktop or mobile apps.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can I make videos for a client's app?&lt;/strong&gt;&lt;br&gt;
Yes. Use a test account on the client's app, render the lessons, then download the MP4 files and subtitles or publish them on a page for the client's users.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;This post was first published on the DashCast blog: &lt;a href="https://dashcast.net/blog/dashcast-for-developers" rel="noopener noreferrer"&gt;DashCast for Developers&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>webdev</category>
      <category>productivity</category>
      <category>laravel</category>
    </item>
    <item>
      <title>Tutorial videos for your software, without recording</title>
      <dc:creator>amer kasem</dc:creator>
      <pubDate>Sat, 24 Oct 2026 10:58:20 +0000</pubDate>
      <link>https://dev.to/amer_kasem_49e31ccb43f4c9/tutorial-videos-for-your-software-without-recording-55a6</link>
      <guid>https://dev.to/amer_kasem_49e31ccb43f4c9/tutorial-videos-for-your-software-without-recording-55a6</guid>
      <description>&lt;p&gt;Hey  👋&lt;/p&gt;

&lt;p&gt;I built &lt;a href="https://dashcast.net" rel="noopener noreferrer"&gt;DashCast &lt;/a&gt;because making tutorial videos for software is painful. You record your screen, re-record when you stumble, record your&lt;/p&gt;

&lt;p&gt;DashCast does all of that for you. You get a finished tutorial video of your own web app:&lt;/p&gt;

&lt;p&gt;🎬 ReCal screen footage of your product, not mock-ups&lt;/p&gt;

&lt;p&gt;🗣️ RNatural AI narration in 14 languages&lt;/p&gt;

&lt;p&gt;💬 Word-by-word subtitles, included&lt;/p&gt;

&lt;p&gt;🔄 WApp changed?sMake lhs video again in minutes instead of re-recording&lt;/p&gt;

&lt;p&gt;Watch the demo in the gallery: it walks through a freight dashboard, and not a single click in it was made by a person. DashCast drove the&lt;/p&gt;

&lt;p&gt;screen and spoke every word.&lt;/p&gt;

&lt;p&gt;It's made for:&lt;/p&gt;

&lt;p&gt;• SaaS teams who need onboarding videos&lt;/p&gt;

&lt;p&gt;• Support teams who answer the same "how do I…?" questions every day&lt;/p&gt;

&lt;p&gt;• Product teams who ship often and need docs that keep up&lt;/p&gt;

&lt;p&gt;I'd love your honest feedback: what would you make a video of first, and what's missing for your use case?&lt;/p&gt;

&lt;p&gt;I'll be here all day answering questions 🙏&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Flgb4a1r0e34y6obni4rf.JPG" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Flgb4a1r0e34y6obni4rf.JPG" alt=" " width="799" height="558"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>saas</category>
      <category>ai</category>
      <category>tutorial</category>
      <category>website</category>
    </item>
  </channel>
</rss>
