Show HN: Someone.io – Task management for teams made easy
someone.io
someone.io
We are really pleased to see such interest and enthusiasm in the product, it chimes with what we've been hearing from users since we launched our beta in May. Your feedback is very useful for us - Someone.io is still in development and we are currently in the middle of an equity crowdfunding campaign which you can see over at http://invest.someone.io .
If there is anyone who wants to support us and become a shareholder, we'd love for you to go and have a look at our campaign and invest.
You're also more than welcome to follow us at http://www.twitter.com/someoneapp and http://www.facebook.com/someoneapp Thanks everyone!
Lasse @ Someone.io
Looks neat btw!
It gives the distinct impression they've already missed the promised deadline even if that's not the case.
You’re right! That plan to release the payment model this summer was made back in spring and that text wasn’t supposed to be there... The reason we changed was we started a partnership with http://www.sintef.no/en/ (Scandinavia’s largest independent research organisation) in March which made us change some things about the direction we are taking the product in.
We have been working with SINTEF and 6 pilot partner companies to fine tune the product to meet user needs as they define them and also to make sure we have a premium, paid version that is going to work.
It will be rolled out by the end of this month and, while I don’t want to give too much away, there will be a free option and a premium version with extra features where companies pay per user/per month. We will be sure to let you guys know when we have more details.
Thanks again, Lasse @ Someone.io
It's missing two things that I would need to actually use it:
1. An overview, where you can see the status and progress of all the projects at a glance. Right now, as far as I can tell, the only info the overview page gives about the projects is the project name and participants. I'd love to be able to see which columns were completed in the overview page.
2. Project templates. I want to have a few different project types, each type of which loads a default set of columns, colors, and tasks.
One final observation is that I'm not sure what the "state" field of the columns does. Changing the state doesn't seem to have any visible effect. For my purposes I'd like each of the columns to represent project stages and for it to be very meaningful when we've moved from one project state to the next.
Looking forward to seeing future iterations of this project! I've been amazed at how hard it is to find a software solution for my needs, and am very glad to see new promising new development in this area.
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.
Committing to a new process or software is an investment of time and trust. When we choose something to use in our group, we want to know it's going to be there in a year or two, and still doing the thing we bought it for.
Software you can purchase and install on your own servers / desktops does that. In fact, we'll choose one software package over another if it doesn't force us to submit to updates until we want them, or rely on someone else's servers to stay functional.
Browser-based tools from someone else can make it into our workflow, but only after they've been around long enough and achieved mainstream adoption, so we can be relatively sure they're unlikely to "pivot" or disappear. Google Docs and Slack are good examples of this.
When you're new and unproven, there are already a lot of hurdles to leap in order to get users, especially business users.
Making your software user-installable eliminates a huge hurdle, I would recommend it.
Onboarding your team to any software is a risk. Our focus on being the easiest and most engaging task manager is aimed at being the least risky. We want to remove as many of those hurdles for business users as we can through simplicity and making team members feel more interconnected.
It's easy to say Google was also once "new and unproven", but Mahn's response below is an excellent one. I guess the issue is epeople want tools they can trust which here is "only after they've been around long enough and achieved mainstream adoption". But then, Slack was launched in August 2013 with 0 users. By June 2015 they had 1M+ users and a valuation of $2.76bn. (Source: WSJ). So new entrants to this market like us can establish themselves quickly but they need to be very good at what they do and they need to earn trust.
We aim to do just that and as jipiboily points out elsewhere, a payment solution is the first step to sustainability, which we've been developing with our research partners and will be rolled out at the end of the month.
For every Slack or Google that reaches mainstream adoption, there are a hundred smaller, often amazing companies, who don't.
Rather than rolling the dice on an all-or-nothing SAAS strategy that requires a big hit to get people to feel comfortable committing a whole organization, you can sell something people can buy, install, and own.
It doesn't mean you can't offer the freemium hosted option. What it does do is give you a chance to see organic growth in the early days. With subscription-based support services, you can even book more revenue — just the kind of thing a startup needs when they're looking for traction in the bootstrapped / angel funded days.
You also have a limit of liability for the actual amount paid to you over the last 12 months (for a free service, this is $0), and on top of that a pretty broad indemnity clause.
Depending on your target audience, I think a pay for option at the lowest tier would help, as at least then I'm not left wondering how you make money and if you plan on selling data to advertising partners as a "related service".
From a design and functionality standpoint I appreciate the simple slick design and feature set. It focuses on the core need without feature bloat. Best of luck!
Paired with liability clause, basically this reads to me (my personal interpretation) as "we'll try our best but don't trust us with anything you that you really value and can't afford to lose". Which is probably acceptable for teams with low or no secrecy requirements, although it probably won't fit a group with stricter needs.
Disclaimer: not affiliated by any means, just looked up few pages, found no demo, haven't bothered to sign-up, still have opinion (haha)
I will give it a shot :)
Kudos!
Edit — Tried it out! is awesome! A few minor things though – It's a little too similar to Trello for me to bother switching, but looks way better (subjective I know, but works well for me!)
and also this: For the buttons (signup button on the home page. The element:focus{outline: none;} is something that really goes a long way in showing polish and detail on the front end.
The product is indeed very basic at its current stage. We wanted to do things right and design it beautiful before we jumped onto more features.
Thanks for commenting on the element:focus button.
It's kind of not cool to discriminate for the sake of "polish".
Reference: http://www.w3.org/TR/2008/REC-WCAG20-20081211/#navigation-me... http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/F78
Edited your domain name, and restricted www so it can't happen again. Thanks for pointing it out so we could correct it :-)
I've recently installed Kanboard (http://kanboard.net) on the smallest DI instance and it works a treat. Kanban board, task list, calendar view, Gantt chart, it has a view for everyone. Simple enough for non-technical team members, yet enough features to effectively manage development projects.
It's not perfect, there are a few small bugs, but it seems to be actively developed and in general I can recommend the product thus far. Spend an hour tweaking the CSS to taste, and it's a very nice tool.
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.
Thanks for your question, have a great day!
1. Our focus is to serve teams so in the near future, all of our new features will be directed towards teams. (btw which features of trello do you feel lack "focus on teams" ?)
2. Our visual design is better than Trello.
3. We will eventually bring in more "social" collaborative tools (any idea what these will be like?)
Some comments on initial signup: - Great approach to validating emails by sending an email after initially providing just that, As opposed to the classic "doing so after filling in all info". This way you get to figure out you messed up your email early in the process! I liked that.
- The confirmation email had a link to `Get started with...`. It would have been great if you also had smaller text saying "Or copy this link and paste in your browser: ...". Maybe it's just me but I get scared of clicking on links in emails without knowing where they are going to (or downloading in malicious cases)
- Would have been great to not have to go through so many screens for signup. Maybe have me provide my team name, name and password in one screen.
- The animations on the task cards and their dragging is pretty great!
1. When two or more people are editing the same card's description, the description goes out of sync and ends up not saving either of the changes.
2. The UI doesn't feel very snappy -- it feels kind of slow.
3. The state field of a column has no other purpose right now than to mark it as completed so that cards end up moving there automatically when completed. Perhaps show the state field somewhere?
4. Why are cards automatically moved when completed? I liked Trello because I can organize it in whatever way I wish..I'll turn off the Completed lane for now.
5. I can't assign more than one label/tag/color to a card.
This feedback is invaluable to us. We've been receiving a lot since this post hit No.1 this morning and the development team will be hard at work for the coming weeks implementing the best of the suggestions we have got.
Thanks!
While I do love Trello, I find it is missing support for some aspects of Kanban such as swimlanes and list limits. If something out there could match Trello on the majority of features, add in the classic Kanban stuff (optionally) and have a nice looking interface + mobile client, I'd be sold.
For an app like this, dedicating the team's time to it should take no less than 5 minutes of attention per person, about the time it takes someone to deliver post-it notes to everyone's desk or mount a corkboard to the wall. This also seems to work within that principle.
We've been looking for a tool with a good interface to use as a collaborative check list. Every checklist shares the bulk of its tasks + it has a few unique tasks per project. Duplicating the tasks by hand seems cumbersome.
If anyone has an alternative, it would be appreciated as well :)
Process Street; process.st
Asana; asana.com
Wasn't suitable for our use but sounds like these might help you.
Yes, duplicating projects is something other users have asked us for and it's something we have in the pipeline. There are a lot of really great suggestions we've had in recent weeks and this is just one that you can expect to see in the run up to Christmas.
Thanks again for your suggestion,
Dan @ Someone.io
In http://tasksinabox.com we use templates for this. You can instantiate a new project, which is a collection of tasks, from a template. That creates all the tasks, and from there on extend and customize as you wish.
We just signed up and are giving it a spin. So far we love how simple and light everything is at the moment. All the features were intuitive as well, even those not explicitly stated i.e. dragging tasks around to reorder for example. Super cool and looking forward to a mobile app ;)
These are the things I like about it:
1. Simplicity and easy set up. 2. I am not forced to provide my personal information 3. Customizable workspace 4. Easy to invite co-workers
Provide a paid version.
i understand your point. A premium, paid solution is actually something we are going to be releasing before the end of the year so you can put your mind at ease on that one and feel free to test the product in the meantime.
Dan @ Someone.io
This may be the funniest tagline I've ever seen.
we actually do integrate with slack! You can read a how to guide right here - http://blog.someone.io/post/117160294470/integrate-slack
Dan @ Someone.io
It isn't the case here but site/app makings take note: this is why I never "sign-in using <social media account or some such>" so if that is the only option you offer I won't be trying your service/app/other.
For email I have a sub-domain set as catch-all and give out addresses in that to new sites. If an address starts getting junk I can just block it. If the sub-domain as a whole gets deluged then I kill it and start another (any site/app/other I continue using gets given an address on my main domain so I'd lose nothing, though I've never actually had to do that). Because it is a sub-domain it gets skipped by junk mailers guessing commonname@domain.tld addresses. Some sites have bad email address checking that rejects something@sub.domain.co.uk (I assume their regexp doesn't like the extra dot in the server name) but if someone gets that wrong I don't trust the code in the rest of their app so I move on.