<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>flove making-of — UX questions</title>
    <link>https://flove.org/making-of.html</link>
    <description>New UX design questions from flove interviews.</description>
    <language>en</language>
    <item>
      <title>When should the form replace asking inline?</title>
      <link>https://flove.org/making-of.html#talk2web-design_q3</link>
      <guid isPermaLink="false">talk2web-design_q3</guid>
      <category>Skills</category>
      <category>UX</category>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>• Many questions (~4+) — Use the form whenever there are roughly 4+ questions; ask 1–3 inline.
• Always in brainstorm/plan — Always render the form when there are questions.
• Only when I offer it — I propose the form and you opt in each time.

★ decided: Only when I offer it · ◇ recommended: Many questions (~4+)</description>
    </item>
    <item>
      <title>How should the user tune the copied prompt?</title>
      <link>https://flove.org/making-of.html#talk2web-design_q6</link>
      <guid isPermaLink="false">talk2web-design_q6</guid>
      <category>talk2web</category>
      <category>UX</category>
      <category>Frontend</category>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>• Editable textarea (prefilled) — A box prefilled with the default prompt, fully editable, persisted.
• Presets + free add-on — Pick an intent (conflicts/summarize/draft-plan/critique) plus an optional extra line.
• Appendable notes box — Base prompt fixed; user only appends extra instructions.

★ decided: Presets + free add-on · ◇ recommended: Editable textarea (prefilled)</description>
    </item>
    <item>
      <title>How should a per-question reference behave?</title>
      <link>https://flove.org/making-of.html#talk2web-design_q8</link>
      <guid isPermaLink="false">talk2web-design_q8</guid>
      <category>talk2web</category>
      <category>UX</category>
      <category>Frontend</category>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>• Inline reveal chip — A '↗ brief §B.2' chip; clicking reveals that excerpt; prompt notes '(see §B.2)'.
• Pointer in prompt only — Reference appears only in the copied prompt, no inline reveal.
• Inline reveal + re-inject excerpt — Reveal inline AND duplicate the excerpt into the prompt.

★ decided: Inline reveal chip · ◇ recommended: Inline reveal chip</description>
    </item>
    <item>
      <title>Intent preset set, and setup-block default state?</title>
      <link>https://flove.org/making-of.html#talk2web-design_q10</link>
      <guid isPermaLink="false">talk2web-design_q10</guid>
      <category>talk2web</category>
      <category>Frontend</category>
      <category>UX</category>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>★ decided: Presets OK (Conflicts · Summarize · Draft-a-plan · Critique); the setup block starts collapsed like every other block.</description>
    </item>
  </channel>
</rss>
