Loading...
Answers
MenuWhat's your advice for drilling down on use-case for our real time communications iPad app for co-viewing docs together?
Our iPad app lets you view Dropbox docs or browse the web together with others in real time, while you have voice conversation (VoIP built in). There are many use-cases and we're struggling with defining a clear message around them.
(The app can be found at getjuntoo.com)
Answers
Hmmm? This is a tough one because your product is so wonderfully horizontal, meaning it applies to a very broad set of cases. I'd slice and dice in two directions.
First, I'd think about the general process of collaboration on a document, for example: a) drafting - are two people actually writing the words together? I personally don't like this. b) first read through together staying on the same sentence or page, c) editing together, etc.
Second, I'd think about industries or verticals or contexts, such as in a Legal setting, in a Tech Documentation setting, in a coding or XP dual programming setting, in a social media post drafting setting, and so forth.
Check out: https://medium.com/look-what-i-made/fd48c3b412bc Seems to be evocative of what you're doing, but targeted to one specific use case of "pair programming".
I'd suggest:
1. Looking at different industry verticals where a truly synchronized viewing of documents is of use
2. Then arrange those in a descending order using a mix of variables such as size of market, perception of pain felt by client, etc.
3. For the verticals that come out among the top 3-4, it might make sense to do another round of customer development interviews to validate your hypotheses around utility to customer
This could potentially point you to a small number of compelling use cases.
I'd be happy to look at (a) what use cases you currently have and (b) brainstorm/be a devil's advocate as you go through the process above.
To find out how to describe your use case, I would get real users to use your product, then ask them "How would you describe this product to others" or "If you were to recommend this to a friend, when would you recommend a friend used this?"
Do this with 10 pairs of people (one presenting and one watching) and ask them the above questions. I guarantee that you will learn the answer to your question.
For me as a user, your landing page is confusing to me. When reading at the top I was assuming this was to be used when two people are meeting remotely, kind of like a skype + screen share replacement. Then in your graphics you show two people standing next to each other. So I would be talking to my co worker and also controlling her screen.
As this is in Lean section : what is your value hypothesis?
Related Questions
-
Is having "HOME" button in navigation menu necessary if I have a clickable logo? What makes most sense from UX POV?
We have been collecting usage data on the home button from about 750 websites we manage across North America in an effort to try to determine if it is necessary or not. While each website is different, and much of the data is statistically insignificant, we have started to operate with a few assumptions. 1.) Most users, particularly younger users, recognize the logo as a way to get to the home page. 2.) Websites without home buttons seem to get a comparable amount of traffic to the home page as those that do not. We don't see a significant difference between having a home button or not. 3.) Websites without a home button often will see an increase in direct traffic from returning users during a session indicating that users who do not know the logo is a route to the home page will instead clear the address bar back to the root domain to get back home. Based on our research, we have decided to omit the home button in most instances. Although when it is present, it is often used, most users seem to understand how to get to the home page regardless of the inclusion of a home button. With the complexity of modern websites, we are usually pressed for space in the header and can better use the real estate that would be dedicated to the home button for other UI elements. That said, if the audience for our website skews older, we will still include the home button. Our research has indicated older users are less familiar with the concept of the logo being a home button.RS
-
How do I grow from a one man startup when I don't have the money to hire & don't have skills or time for investors?
Stop thinking you don't have the skills to do something. You can learn anything if you decide to, but assuming up front that you can't (forever) is dangerous. my2centsDM
-
How should the dynamic between a ux designer and a developer who are working together look like?
It depends a lot of in the skill sets and experience of both people but in most cases the ux designer should be controlling the developer pretty heavily in order to make sure his ideas come through properly. The UX designer may just need to work on his approach so people don't feel bossed around and more like they are working together. In an ideal world, there would be a project manager who makes sure everything is communicated well and keeps the dynamic feeling great.JM
-
What's considered "Traction" in the B2C app world these days?
Mobile app that has launched: You need ALL of the following: 1) Trending towards or at 100000 installs within first 90 days of launch; 2) Day 30 retention rate of at least 20% 3) Core "MTM" (metric that matters) healthy (dependent on business model, usage model etc) 4) Evidence that growth is just "getting started" with plenty of upside left. Happy to talk more in a call.TW
-
What are ways to find and engage B2B beta users for a brand new application?
Find apps that are B2B and go to the review sections. Specifically going to Google's play or Chrome store and look at reviews and follow them to Google+ to engage. I took that same angle for B2C app I was building last year. Check it out. http://blendah.com/post/37331434653/lean-startup-hackTM
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.