Automation for design mocks

Designers at MakeMyTrip and Goibibo were spending too much time pretending to be copywriters and content operators. Every new card needed names, prices, codes, and logos before it could be reviewed, and most of that work was manual.

The problem was not design. It was data entry.

Lore Ipsum is fine for layout, but travel products need something more believable. A flight card with a fake route or a hotel card with an empty name field does not help stakeholders understand the experience.

Designers were repeatedly typing the same kinds of details by hand:

• Hotel names, city pairs, and flight codes
• Prices, durations, and distances from landmarks
• Airline logos, hotel imagery, and other visual assets

The work was small on its own, but multiplied across many screens it became a real tax on design time.

I wanted the mock to feel real without making the designer do the real-world busywork.

The solution was one click

I built Trip Content so designers could choose a service category, select their card frames, and populate everything instantly. Instead of manually hunting down each piece of content, the plugin filled the layers with context-accurate text and visuals.

That meant a designer could take a blank travel card and turn it into a realistic review-ready mock in seconds.

How I built it

Trip Content was my first Figma plugin, so the build was as much about learning the platform as it was about solving the workflow problem.

• Figma API. Read the user's selection and filled text and image layers programmatically.
• Cursor. Helped speed up the coding process and structure the plugin logic.
• Custom asset CDN. Hosted logos and photos in one lightweight source so the plugin stayed fast.
• Smart datasets. Used realistic JSON data for Indian routes, services, and pricing.

The main design challenge was balance. The output had to feel realistic enough for reviews, but the logic still needed to stay simple and dependable for designers using it quickly.

What changed for the team

Trip Content removed a surprisingly common source of friction. Instead of spending hours cleaning up mock data, designers could focus on the actual experience.

The plugin made design reviews faster, reduced copy-paste drift, and gave every card a more believable context. That mattered because realistic content helps teams make better decisions earlier.

What I learned

Building Trip Content taught me that a good internal tool does not have to be complicated to be useful. If it removes a recurring annoyance cleanly, it can become something people rely on every day.

It also became a useful starting point for everything I built after it. Once I saw how much time a small plugin could save, I became much more interested in designing tools for the people behind the product, not just the end customers.