I've been thinking a lot about a big parenting question while working on an app: Should we give kids money to clean their room or empty the dishwasher? Many parents (and I, of course) and experts believe that paying kids teaches them about "work," but I'm concerned that it may make them feel entitled and alter the way the family operates.

The issue I had to deal with was "What's in it for me?" Trap

I figured out that paying my kids to clean their room is a bad idea because it teaches them that they can skip the cleaning if they don't get paid. Adults have to clean up their own messes in real life!

Hi there, Product Hunters, it's Alex!
I'm Kvestify reator, the application that transforms tedious domestic activities into thrilling family adventures (similar to Duolingo, but for cleaning! ).

Creating Kvestify was really enjoyable, but the main issue I had with the architecture was very simple: I was creating an app for families that would have to support two totally different users the Parent (The Boss ) and the Child (The Player ) all in the same app.

If the User Experience of the app is unclear, it will only create new conflicts in the family, and that will totally defeat the purpose! Below are the two major multi-role difficulties I overcame (and one I am still optimizing) that might be recognized by anyone who is building collaborative tools:

The end of the "Account" identity crisis resolved