• Richard SisonRichard Sison, 5 months ago

    No worries! Here are my responses on both Maze and Framer


    • Testers.
      • For the projects I work on, I'd prefer to recruit myself. My products are usually pretty industry-specific so leaving it to a recruitment tool that doesn't provide that level of granularity isn't ideal.
      • You're probably interested in the demographics they offer. Here's what they say: >"All test participants are English-speaking and mostly US-based. You can filter responses based on sex (all, male, female) and age (18-70) when you place an order."
    • Pricing for testers. I didn't realise they hid this. Here's a screenshot of the credit packages they offer currently.
    • Pricing. You get a lot for free honestly. I often work on one project at a time (or at the very least, the phase where I'm doing my quantitative tests rarely overlap) so the free tier is perfect as I can cycle the "active project" (by archiving and unarchiving). I haven't had to yet, but apparently that's possible.


    • I'm learning Framer now actually. Meng To (designcode.io) always puts together great tutorials. He's got a few for Framer (I'm doing this one at the moment and it's really good so far and it's free).
    • As I'm only learning it now, I'm still forming my opinion around it. On paper it is a monster tool that is targetted at a huge gap in the design tooling. The ability to produce very realistic prototypes using code (and leveraging off existing code from design system), is a game-changer.
    • The approach Framer takes is completely different to Sketch and Figma (in my opinion) and complements either tool really well. Where I'm hoping to bring Framer into my workflow is after the fundamental design decisions are made and we need to get the design into the next phase. I'll probably still reach for Sketch for wireframes, quick prototypes and starting off the visual design. I see Framer carrying things on when things like interactions, microinteractions, transitions, animations, states need to be worked out.
    • Barrier to entry. Yep. Currently the barrier to entry is huge. I'm fairly comfortable with HTML and CSS but not with JS (and definitely not with React). So understanding how to use Framer (specifically the code aspects which is where Framer's power comes from) is a huge learning curve for me.
    • I think the barriers are definitely more in the learning curve for designers. While developers will need to be aware of the tool, and as a team you'll need to work out your workflow, the promise Framer has for product teams is a pretty big deal in my opinion. As far as handover is concerned, it bridges a huge gap that's otherwise left open to interpretation or potentially lots of conversations (which isn't necessarily a bad workflow by the way).

    Hope that helps!

    3 points