Baseline: My original input, and Figma Make's output
First, I wrote the input as how I typically would.
Create a mobile app screen for a money transfer app that supports currency exchange and transfers. On this screen, users should be able to see the recipient, enter an amount in one currency, view the equivalent amount in another currency, choose a funding method, and tap the “Transfer Money” button.
This is what I got.👇
Design generated from my baseline prompt
Front-loaded prompt
Then I rewrote the prompt using the TCEBC format.
While writing it, I realized new requirements I hadn’t considered:
Users should be able to enter an amount in either "send" or "recipient gets" field
UX and copy must be extremely clear and beginner-friendly
Incorporating these thoughts, I wrote a structured prompt:
Task: Create a screen for a mobile app where users can exchange currency and transfer money.


 ​ Context: This screen is part of a money transfer mobile app that allows users to send and request payments globally. Users arrive on this screen after starting a payment flow and selecting a recipient.



 ​ Key design elements:

• Display the selected recipient

• An area where users can enter the amount currency they want to send. They should also be able to select the currency. (default to EUR)

• A second area showing the equivalent amount in another currency. Users should also be able to select the currency (default to USD)

• A section for selecting a funding method (default to credit card)

• A “Transfer Money” button



 ​ Expected behaviors:
 
• Users should be able to enter the amount in either currency field, with the other field updating dynamically based on the exchange rate

 ​ UX considerations:


 • Copy should be clear and simple, so it is easy to understand even for less tech-savvy users



 ​ Constraints:

• The screen should fit within a single view with no scrolling required

• The “Transfer Money” button must remain visible at the bottom of the screen without scrolling
This was the output. 👇
Design generated from the front-loaded prompt
Making a comparison
​
Comparing the two different outputs, here's what I found:
Baseline prompt output
More visually bold (I love the large cards)
More UX issues (Why is the EUR tag floating? What's the logic behind using the primary purple everywhere? Is it clear to users what they can tap on?)
Front-loaded prompt output
Better alignment and hierarchy
Fewer usability issues
Less visually adventurous (more boring than the baseline)
Both designs
Not production-ready (need to tweak the designs)
Added elements independently (e.g., "No fees" or "terms and conditions"
The verdict
So, is the structured prompt better?
If your goal is to get a design that's closer to production ready, then yes, because:
The output has better usability
The design is easier to refine in Figma
Writing the prompt forces you to think through requirements (this actually made the most difference, IMO)
If your goal is visual exploration, not necessarily. There are better ways to use Figma Make for visual ideation. I promise, I will cover that in one of the upcoming newsletters.
If you've also tested different prompting methods, I'd love to hear your findings. You can always email back directly.
Hi friend, This is Design Current, your go-to newsletter about user experience design. In this issue, we want to share a few design inspirations and thought pieces that has helped us grow and reflect. First, a celebration! Our studio has just entered our 4th year! We started Koi Studios with a simple belief: thoughtful design can do good. What began as a desire to create impactful work grew into a studio built around care: for users, partners, and the problems worth solving. Fast forward to...
Hi friend, This is Design Current, your go-to newsletter about user experience design. And to those celebrating: Happy Thanksgiving! ✨ As a little gift of gratitude, we pulled together a handful of design gems our team at Koi Studios fell in love with this year. They sparked a ton of inspiration for us, and we hope they do the same for you. Design candy Understand neural network visually → Epic visual storytelling that turns a complex topic into something truly digestible. Poolsuite → An...
Hey friend, This is Design Current. A newsletter about user experience design. Lately, I’ve felt a bit… gaslit by AI products about my prompts. Any time the output misses the mark, I’m told: “To get good results, you need to write better prompts.” But why should users know what is a good prompt??? This is a real issue for AI products that rely on chat interfaces. As designers, we take this seriously. This is what we did to improve AI chat UX and, in turn, boosted product adoption. 1. We...