<?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: Tover Wu</title>
    <description>The latest articles on DEV Community by Tover Wu (@tover0314).</description>
    <link>https://dev.to/tover0314</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3673381%2F0e27ce5d-1a56-4bda-b232-8b496bad7eae.jpg</url>
      <title>DEV Community: Tover Wu</title>
      <link>https://dev.to/tover0314</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/tover0314"/>
    <language>en</language>
    <item>
      <title>Day 0: I want to kill the pain of making slides — an indie dev’s starting point with Nano Banana Pro</title>
      <dc:creator>Tover Wu</dc:creator>
      <pubDate>Mon, 22 Dec 2025 08:16:34 +0000</pubDate>
      <link>https://dev.to/tover0314/day-0-i-want-to-kill-the-pain-of-making-slides-an-indie-devs-starting-point-with-nano-banana-pro-1jlp</link>
      <guid>https://dev.to/tover0314/day-0-i-want-to-kill-the-pain-of-making-slides-an-indie-devs-starting-point-with-nano-banana-pro-1jlp</guid>
      <description>&lt;p&gt;Today is Day 0 (Dec 22, 2025). I’m starting a 10-day public build log to document one thing:&lt;br&gt;
How I’m using Nano Banana Pro to turn “making PPTs” from a slow, messy craft into a repeatable, productized workflow.&lt;br&gt;
I’m not a designer. I’m not a consultant who lives in decks. I’m an indie developer who can ship code and build products — but every time I need slides, I fall into the same black hole:layout, visuals, and style consistency.&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.amazonaws.com%2Fuploads%2Farticles%2Fj9fxk45h8x9l5bkn07c0.png" 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.amazonaws.com%2Fuploads%2Farticles%2Fj9fxk45h8x9l5bkn07c0.png" alt="Nanobanan Pro PPT" width="800" height="446"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The real pain isn’t writing content — it’s making it look like a deck&lt;br&gt;
If you’ve ever built a product pitch, a demo deck, or a talk, you probably know this pattern:&lt;br&gt;
The outline takes 30 minutes&lt;br&gt;
Then you lose 3 hours to font sizes, spacing, colors, and image hunting&lt;br&gt;
And somehow it still looks “stitched together,” not cohesive Content is thinking. Visual consistency is operations.&lt;/p&gt;

&lt;p&gt;Slides need rules — a system — not just effort:&lt;br&gt;
the same constraints, the same visual language, and the same layout logic across pages.&lt;/p&gt;

&lt;p&gt;What I’m building: DrawPPT — from outline to a deliverable deck in minutes&lt;br&gt;
I’m building DrawPPT with one goal:Make it possible for non-designers to consistently produce decks that look professional, structured, and visually unified — and exportable as PPTX.&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.amazonaws.com%2Fuploads%2Farticles%2Frthzh0cphbwpvggyt7b0.png" 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.amazonaws.com%2Fuploads%2Farticles%2Frthzh0cphbwpvggyt7b0.png" alt="DrawPPT Interface" width="800" height="405"&gt;&lt;/a&gt;&lt;br&gt;
Not “a deck that exists.”&lt;br&gt;
A deck that feels like it was made by one system, not assembled at 2am.&lt;br&gt;
Why I’m betting on Nano Banana Pro: slides don’t just need images — they need layout + readable text&lt;/p&gt;

&lt;p&gt;Here’s the key insight:&lt;br&gt;
In slides, images aren’t decoration. They often carry the structure.&lt;br&gt;
Title pages / section dividers that set the tone&lt;br&gt;
Infographics: process, comparison, timeline, funnel&lt;br&gt;
Chart styling: making data pages feel “on brand”&lt;br&gt;
Icons / illustrations: a consistent visual language&lt;br&gt;
And all of these have a hard requirement:&lt;br&gt;
Text inside visuals must be readable, and composition must be intentional.&lt;/p&gt;

&lt;p&gt;That’s why I’m betting on Nano Banana Pro — because it’s optimized for producing usable assets, not just pretty images. For PPT use cases, “text clarity + layout awareness” is everything.&lt;br&gt;
What you’ll see in the next 10 days: from “looks good” to “fits into PPTX”&lt;/p&gt;

&lt;p&gt;Here's How I use DrawPPT to make a Mckinsey Style PPT&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.amazonaws.com%2Fuploads%2Farticles%2Fwfplqxfs8q696i10k6m8.png" 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.amazonaws.com%2Fuploads%2Farticles%2Fwfplqxfs8q696i10k6m8.png" alt="Mckinsey Style PPT" width="800" height="446"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If you want early access / waitlist for DrawPPT: &lt;a href="https://drawppt.com" rel="noopener noreferrer"&gt;https://drawppt.com&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Quick question for you&lt;br&gt;
What’s your biggest slide-making pain?&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Finding visuals?&lt;/li&gt;
&lt;li&gt;Keeping a consistent style?&lt;/li&gt;
&lt;li&gt;Infographics that don’t look amateur?&lt;/li&gt;
&lt;li&gt;Exporting to PPTX cleanly?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Drop a comment — I’ll use it to prioritize the next days.&lt;/p&gt;

</description>
      <category>programming</category>
      <category>ai</category>
      <category>beginners</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
