Not long ago I took a design challenge from Status.im—an open source platform for Decentralized Apps built on Ethereum. The brief included a Sketch file and stated the following:

Status Open Bounty is a web-based project of Status.
It's a bounty-based, open source collaboration solution for developers and organizations who want an easier way to get projects done.
Status Open Bounty provides organizations—including our own—with a path to decentralize their development. It also makes it easier for developers around the world to be rewarded for participating in open-source projects. Status Open Bounty now:
• Rewards code contributions on projects you choose.
• Pays rewards in SNT or a cryptocurrency of your choice (ETH and most ERC–20 tokens), without the third-party fees.
• Provides quick setup and bounty payouts as it plugs directly into GitHub.
Create a Dashboard for Developers or for Organisations (choose one). Think about what would be important for them to have an overview of. Think about the structure and content hierarchy of that Dashboard. Identify the information the user would want to be presented and how best to group the dashboard information/metrics into categories.
Feel free to edit the Sketch file, visual implementation is not a priority, although showing your UI skills does matter as well.

The Sketch file had the mobile and desktop UIs for the Open Bounties and Activity pages, not very different from what I could see online. I immediately listed several UI/UX improvements as notes. More on that later.

Next, I chose to work on the organizations' side of the application and started with the Desktop experience because it was the one that those users would be seeing most frequently. When it was defined, I adapted the main screen layout to the mobile, so that the Organization members could also browse their Bounties from their phones and Status team would see that I also care about the mobile experience for their users.

The original design included pagination by the end of the Open Bounties pages. I replaced it with a Load More button. I've learned about those during my 7 years building e-commerce websites. It's a common design question: Pagination, Load More button or Infinite Scrolling? Even Smashing Magazine wrote an extensive article that I've recently sent to a couple of colleagues at work.

2 days of design work later, I sent an InVision prototype link to the Status team.
What do you think about the layout? Let me know your thoughts.