This looks like an interesting premise, but it's super sketch web design to ask for an email address with absolutely no explanation of how your service works.
Even if I was totally willing to give my email address to you - I'd still really like more of an explanation on how your service works before I invest any time into using it.
You could probably get a lot more positive feedback on this service by adding an explanation on how it works at a high level and what I am to expect by using it.
It asks for an email without explaining how it even works. I gave it a burner and then it immediately starts asking for all the contact info of everyone I want to stay in touch with. Pretty sure this is a data farming scam. It has no data policy listed as far as I can see.
solution:
show parts of the app that don't require a signed in user, simulate a user with dummy data, create a distinct user from browser session information behind the scenes, do that and ask for parts of that user periodically and still optionally, show us the benefit of “saving” the user, design your system around not needing to save by being able to recompute the user in the future
"The concept is fairly simple: I want to stay in touch with person p every t period of time. If t has passed, and you haven't talked to p, you get a reminder."
It's just basically a way to keep track of the last time you've sent a message to someone, assuming you update your list on infrequent.app itself.
This has a really depressing aire to it honestly. Deciding to send a message to someone because it’s been X days feels like it’s just there to prolong zombie friendships with people.
It’s alright to drift away from people sometimes, we all change. Enjoy the moments you did have with someone when you were both in-sync! If you don’t have any other reason to reach out to them, then maybe it’s just time to close that chapter.
11 comments
[ 4.9 ms ] story [ 30.3 ms ] threadEven if I was totally willing to give my email address to you - I'd still really like more of an explanation on how your service works before I invest any time into using it.
You could probably get a lot more positive feedback on this service by adding an explanation on how it works at a high level and what I am to expect by using it.
funnel fail
solution: show parts of the app that don't require a signed in user, simulate a user with dummy data, create a distinct user from browser session information behind the scenes, do that and ask for parts of that user periodically and still optionally, show us the benefit of “saving” the user, design your system around not needing to save by being able to recompute the user in the future
https://duarteocarmo.com/blog/infrequent
"The concept is fairly simple: I want to stay in touch with person p every t period of time. If t has passed, and you haven't talked to p, you get a reminder."
It's just basically a way to keep track of the last time you've sent a message to someone, assuming you update your list on infrequent.app itself.
It’s alright to drift away from people sometimes, we all change. Enjoy the moments you did have with someone when you were both in-sync! If you don’t have any other reason to reach out to them, then maybe it’s just time to close that chapter.
I don't personally think this tool is right for me but I can see how a reminder would be useful and healthy.