Roast my landing page!
Here's my landing page for a new web app I'm building. I won't describe it because I want you to figure it out by just seeing the page.
Bring it on!
Here's my landing page for a new web app I'm building. I won't describe it because I want you to figure it out by just seeing the page.
Bring it on!
Why don't you actually show the app in action? I think if you'd replace the top illustration with a nicely done screenshot of your app, I'd get it much faster. I see what it's supposed to do, but now how it's doing that. I think a video or animation could help a lot more than blocks of text as well.
Overall, I think the copy is super vague. You state the problem, that's fine, but your solution is described poorly. "deciding on one to read is not cool" – it's also not not cool, it just takes mental energy. Can you help reduce it? "We give that task to a machine". What kind of machine? Does it choose it randomly, or based on something smart
Lastly, and this is a personal one, I'm not the biggest fan of putting your personal bio and a donate link on the landing page. You are asking for something before giving me something, I don't think it'll do any good.
Once I've downloaded the app and used it for a week, that would be the time to ask me to chime in :)
/roast
That was very insightful, thank you! I'll start making the changes. BTW its only a web app now, I'll think of a mobile app later
So its an add on to Pocket app or you are competing with Pocket app? I hope its the latter.
Yeah I feared the page didn't describe it well enough. Its built on top of Pocket. It utilises the Pocket API to show you 5 articles per day. Essentially removing the task of choosing 1 article from a 1000 to read for the users'
That can't be the only thing wrong with Pocket - how did I end up with 1000 to begin with?
I think in this information age, we come across content faster than we can consume it. Hence the numbers keep piling up
So the only way that problem is fixable is if some of that content is not actually worth reading. You would have to explain how you determine what is not worth reading. For instance maybe you allow connections with friends and prefer the articles that they read so everyone can be on the same page.
That's a really nice idea, I'd bake it more and think about integrating it.
That's not the only problem, though. Sometimes, even when the articles are good and worthy of our time, there's just so many articles to choose from, the user is unable to do so (like analysis paralysis) and just gives up and closes the app.
Analysis paralysis is a defense mechanism. If you help them out of that defense without anymore reward than if they chose themselves they will eventually close the app anyway. I mean its like Wikipedia - when it first arrived we would all surf through it reading great stuff. No one does that anymore and its not just the too many articles problem. If you just randomly choose articles your subscribers will use you for a while and then quit - your solution has to be more value add than that.
I agree with this. I used to be very excited reading articles on Medium. They send something like a today's list. Soon I fell of the wagon and I don't even have a Medium subscription now. This could work for a new user but don't think this will work in long term.
Let's take your, "We git, you are busy" section. You are assuming there are 1000s of articles bookmarked because they are not able to select which one to read. That's not true. It could be because they have more content to read compared to the time they have.
You could do something like, hey you didn't open this article or any articles from this category? Do you want us to delete them? That could clear more unread articles which are never going to be read anyway.
For example, I bookmarked a lot of Java related articles but I am totally into AWS Amplify and writing my code in Python for AWS Lambda Function. I am not going to read those Java articles anytime soon. You could show a pop-up asking if they could be deleted.
Good point that is what GMail has started doing by suggesting unsubscribe when I haven't read something for a while.
BTW did you happen to run into something like https://github.com/aws-amplify/amplify-js/issues/6553 while you were using Amplify?
Hey. I am a total newbie to AWS Amplify and literally started learning it like 2 days ago. So, I dont know about this issue yet. Sorry.