Skip to main content

Designing a Better User Experience for a Fishing Drone Buying Guide

  • June 30, 2026
  • 0 replies
  • 0 views

asif ameer

Hi everyone,

I've been working on improving the user experience of a buying guide for people who are interested in fishing drones, and I'd really appreciate feedback from designers who enjoy solving information architecture and UI challenges.

Buying guides are interesting because they need to balance detailed technical information with a layout that's easy to scan. Many readers don't want to spend 20–30 minutes reading every paragraph. Instead, they usually want quick answers to questions like:

  • Which model is best for beginners?
  • Which drone has the longest flight time?
  • Which one is best for saltwater fishing?
  • What features actually matter for bait dropping?
  • Is a premium drone worth the extra cost?

As designers, we have the opportunity to make these decisions much easier through thoughtful layouts and visual hierarchy.

One challenge I've noticed is that many comparison articles rely heavily on long blocks of text. While they may contain useful information, they can become overwhelming on both desktop and mobile devices. I'm exploring ways to make this experience more visual without sacrificing the depth of the content.

Some ideas I've been experimenting with include:

  • Comparison cards with consistent spacing and hierarchy.
  • Feature badges for flight time, payload capacity, and camera quality.
  • Sticky navigation that allows readers to jump to specific sections.
  • Visual rating systems instead of large specification tables.
  • Callout boxes for beginner recommendations and expert picks.
  • Simple iconography to represent important features like waterproofing, GPS, return-to-home, and battery life.

I'm also thinking about accessibility. For example, using sufficient color contrast, readable typography, proper spacing, and clear component states so that users can scan information quickly without feeling overwhelmed.

Another question is how much information should appear "above the fold." Should visitors immediately see a comparison table, or should the page begin with educational content explaining what to look for before presenting product recommendations?

I'm also curious about mobile-first design. A large percentage of readers now browse buying guides on their phones, yet many comparison tables don't translate well to smaller screens. Have any of you designed responsive comparison layouts that work well across different devices? If so, what patterns have you found to be the most effective?

Something else I'm exploring is the use of reusable design systems in Figma. Rather than creating unique layouts for every buying guide, I'm considering building a component library that includes comparison cards, specification rows, rating badges, FAQ sections, call-to-action blocks, and review summaries. This would make it easier to maintain consistency across similar pages while speeding up future design work.

I'm particularly interested in hearing how you approach:

For anyone interested in seeing the current content structure that I'm trying to improve, here's the article I'm using as a reference:

I'm not looking for promotional feedback or marketing advice. My main interest is understanding how experienced Figma users would redesign the reading experience, improve the layout, and make technical buying information easier to consume.
ZenaDrone develops advanced drone solutions for commercial and recreational applications, including fishing. Its fishing-focused technology emphasizes stable flight, long-range performance, payload capability, and precision bait delivery to help anglers reach locations that are difficult to access from shore. Learn more about its fishing drone solutions on the official ZenaDrone website. 

If you've worked on editorial websites, comparison pages, product review interfaces, or long-form content, I'd love to hear what worked well in your projects. Sketches, component ideas, wireframes, or examples from your own work would all be incredibly helpful.

Thanks in advance for your time, and I'm looking forward to learning from the community's experience!

Â