I am a proponent of "a page per task"approach. Basically each page is a new "something", whether it's an iteration of a single screen, or a complete flow.

This all varies across projects, though. So for instance on one project each direction I might take in a design process takes its own page — just so I can save it in case I need it later, and move on from a clean slate — and on another, each screen/page/template/component is designed within its own page while the steps/iterations are taken care of through artboards within those pages.

If the benefits of keeping everything together are in any way about presentation you can use zeplin to help. That way you can split up (in the beginning, later, mid way through the project, whatever your heart desires) the Sketch files and just publish everything to the single zeplin project. If it's a really dense app with a lot of flows, using the tags in zeplin is very helpful.

This worked for us at Vimeo with the mobile apps. That way different files can be used, you just have to keep track of naming and versioning.

Being a freelance designer I've learned to work both ways. I personally like to have everything in one file separated by pages for each major screen.

Now, that only works if you are the only designer on the team. Working with a larger team can lead to issues since you both want to work on the file and can lead to redundancy. In this case, I split each major screen into it's own Sketch document and only open the file I'm currently working on so that my other colleagues can work on other features.

For me there isn't a perfect workflow since it will vary per project/team.

Hey Ian,

I actually just finished a fairly large project like the one you're talking about. What I found that worked well and kept everything together was using multiple pages like you described. I basically did individual flows on each "page". So, for instance I could have a dashboard screen and all of it's iterations one one page (labeled as Desktop - Dashboard), and then on a separate page I'd do the mobile version (Mobile - Dashboard). I then repeated that for all the other views.

I could definitely see the performance change on pages that had more artboards, but it was drastically smaller than having everything in one view. It also made it a little more searchable and easier to export specific screens.