Thanks for the tips and the note about the broken link. We'll fix these things.
As I mentioned in another comment, we had a developer that saw an overall 140% CTR because his users clicked on the app discovery grid multiple times. Meaning - there were users that clicked on multiple apps in the app discovery grid.
So, if I'm reading you right, you have a grid with multiple options open, and you counted clicking each option once so if I click two options, that's +2, 3 options would be +3, but viewing the options page only counts as 1?
The problem is that you should only get 1 click from 1 view for a particular object. So if I am selling 3 things in your grid, and someone clicks on all 3, it's not +300% for me, it's 100%. If someone clicks one out of the three options, then overall I'd have a 33%.
It's not as useful that way, though. So if I transition this to talking about a series of banner ads as an example: If I have 3 ads for 3 different products on the same page, I'll count their CTR separately. If someone clicks on ad 1 but not ad 2 or three, then ad 1 has 100% and 2 and 3 both are at 0. If someone clicks all three on the same view somehow, then each ctr would be 100% for that view.
100% is the max. Otherwise it's not really useful; how do you know from your way which ad is successful? That's really what CTR starts to measure.
Plus, 140% out of how many options on the list? What if there are 20? It's just not useful unless 100% is the max.
We had a developer that saw an overall 140% CTR because his users clicked on the app discovery grid multiple times. Meaning - there were users that clicked on multiple apps in the app discovery grid.
I see your point. I think cross-promotion, if done right, can drive some very engaged users. In both cases, it's a true organic user. However, with this, it's likely you're getting users with better engagement than a random user browsing through the store. A lot of developers have integrated our app discovery grid with a button that the user chooses to tap on. This results in installs from dedicated users who are already engaged with that developer's apps and chose to view it in an effort to find more of the developer's apps or apps the developer would recommend.
So you are saying the apps which show up are curated with respect to context. So if I make a bible reading app, strip club apps will not show up as options...more likely you will see religious or reading apps?
It is completely up to the app developer to choose which apps they want to show. The developer controls this. So they can just show their own apps and / or apps that are complementary to theirs. They can change this in realtime on our backend dashboard.
Good points! Integration is completely customizable. The bar is optional, and you're free to programmatically call up the grid using breakpoints defined in your code. If you do choose to integrate the bar, it can be completely customized to fit the style of your app. It can also be placed on the top of your interface if this is more appropriate.
We're allowing complete customization so that the developers that know their users best can decide how to implement it in their apps.
Lagging?? Vine has grown fastest out of all of the social networks you mentioned within my group of non-techie friends. All I see on my Twitter feed is Vine links. All anyone talks about in person is whether we're going to 'Vine' whatever we're doing. Maybe this is just my group of friends though (early 20s).
Will Sasso alone has over 250k followers and the app has been live for like, a little over two months now? I'd say it's growing pretty rapidly.
They really should have released the chat portion as a standalone app. It's not consistent with their digital journal concept. Now the app feels heavy, crammed, and confusing.
That being said, they did a beautiful job implementing chat and in my opinion it blows every other messaging app (ex. groupme) out of the water. I just wish they had released it as it's own app.
My thoughts exactly. Just tried registering a new account on the "new" path and it left me confused and unsure of what to do next, feeling especially empty as well.
I disagree. UI walkthroughs are like instruction manuals. Some people read them, but most just toss them aside and learn about the product by using it. I think there definitely needs to be some sort of help section within the app that the user can refer to when needed, but for the most part UI walkthroughs are just barriers of entry. I would even argue that most UI walkthroughs are pretty overwhelming for the average user.
