Great question! I think in our case with this product the reason I've coined it as a platform is more because within our product lineup it's all app that is at the base of everything else. It's going to be a place where we build up lots of new features for each of our products and kinda lives in the middle space between our main core products. Because of that I kinda see it more as a platform then as a singular product on it's own. In some ways it's kinda like an Envoy operating system (not an actual OS but the idea of it).

Not sure if that makes sense or not but that's how I've envisioned it personally and why it kinda feels a bit different from a typical app.

That's a great point! I think that's definitely a factor in determining what prototyping approach to take. I think static ones are still useful for those quick checks I think it's still a matter of being careful with those results and understanding it might not give you the full picture. A full picture can only truly be gained through a more comprehensive prototype so if that is an important decision making factor then finding the time to do it could be worth the investment.

Thanks for suggesting! It's been added now :)

Yeah, great suggestion! I was thinking of adding that in a future iteration :)

There is another way you could do this. You can build custom components in Framer X that you can toggle states on/off with. For example there's some good iOS status bars available in the Framer store and you'll see how those have these different states you can toggle on and off.

Essentially the same thing could have been done with what I have here this was meant more to show the micro-interaction of changing the state through animation but if you wanted that kind of control in the canvas and be able to use it on different artboards more statically that would be possible too. It's a bit of a different workflow but would definitely make sense based on what needs you had for your designs. I can see either one being useful for their own reasons. Hope that makes sense :)

Yeah I had used the original framer basically since the beginning when it first came out and was code only. The jump to Framer X was definitely quite a different one so I would say you don't need to have previous Framer knowledge to be able to jump into Framer X. Most of it was a re-learning experience for me.

We’re the design team at Envoy, and we’re excited to come out from behind the pixels and finally say hello. Thanks for being here! ✨

Like many design teams, we fancy ourselves big thinkers and problem-solvers, but we try not to take ourselves too seriously along the way. In our stories, we’ll share a little bit of all of that — from practical resources to personal insights and everything in between.

You’ll also get to know our team here, too. As a small group of writers, product designers, and visual designers, we each have a big impact on what design means at Envoy. We all have a different backgrounds, unique passions, and personal obsessions (brunch, anyone?) that we’re excited to let you in on.

While we plan to give you a peek inside all things Envoy, we hope you’ll share your stories with us, too. Let’s connect on Twitter, Dribbble, or right here in the comments.

It's true man :( We can still be bff's though, just move here :) Canada's the best <3

Thanks Nick :) yeah I hope to turn it into more of a portfolio one day too

Hey Cory! Thanks for the thoughtful comment :) I totally agree and that was definitely more of what my intention was. I'd love to post something else soon that has more of a critique component to it as well. There's a lot of value in getting the communities feedback on that kind of thing