Thanks for taking the time trying out our product.
1.The product so far is in its early days. A better overview across projects will definitely be developed.
2. In the backend, a project is based on a template system. It's not visible to the user yet as this concept further needs adjustments before we can roll it out . In fact the current project design is just our first "plugin" of how a project can look. We hope to offer multiple ways to visualize a project in the future.
The state field is a system state (not changeable) that is used for triggers and in the future reporting. When you tick of a Task as finished, a trigger occurs that will look up the column with the system state "Completed" and move the task there. It's a bit rough at the moment, but could be a handy way to automate certain tasks later on and provide reports across projects.
I'll admit that there are some similarities, but our focus is very different. What you see today is perhaps closer to Trello than what the experience of Someone.io will be a few months from now.
We have heard from many users who tell us that it is our design and attention to detail that they prefer over Trello. We know that won’t be the case for everyone, but there is plenty of demand for products that serve a similar purpose to Trello, but do things a little differently.
With that said, I think there are 3 main differences between us and Trello.
1. We are team focused. Someone.io is specifically focused on delivering value to teams in a work environment, where Trello has much broader aims. Our focus on teams allows us to better meet their needs.
2. We have simple but beautiful design. We want to be the easiest and most engaging task management tool on the market. Our research tells us that some users find Trello to be “dull" and “uninspiring" and we’ve found particular traction with creative teams who enjoy our approach.
3. We are in the process of becoming the first "Social Task Management” tool. Together with our research partners, we have developed some features designed to make users feel more interconnected with their team and more engaged with their work which we’ll start deploying soon.
We try to be very playful and original with our design and Wordpress don't give the sort of freedom we are after.
When testing out wordpress for the translation aspects, I guess it could work. However we are not found of the solution. It duplicates and dumps a document to the database which slows down the pages. Django handles translations much better.
Thanks for sharing. Working with the same concept for the last few days. Cube (mongoDB/nodeJS rest server), http://square.github.com/cube/, really gave me a kickstart on simple datacapture and quering. (I use highcharts for the visualization).
Always have a backup presentation. Either powerpoint, video or something else that your are comfortable with. I believe that the audience will understand...