Posts, a community app by Read.cv

Thread
Cathy Liu
Replying to @andy

Is read.posts.cv and posts.cv an option?

Andy Chung
Replying to @cathy

Nah I don’t think we would change read.cv right now

Cathy Liu
Replying to @andy

No worries, only reason I ask is b/c it seems like read is a feature in posts, but that’s only from my perspective!

Andy Chung
Replying to @cathy

Fair enough! We’re cannibalizing ourselves faster than anticipated hehe

Cathy Liu
Replying to @andy

Nom nom — in that case I vote (2) if you want to start signaling the difference between the two and move users into posts being the primary product. The (1) makes me think posts is a feature of read. Not sure if that’s what you guys want to signal.

Spring 🏳️‍🌈
Replying to @andy

2️⃣! for simplicity. but are you ready for the post.app and posts.app conversation? people get confused.

Andy Chung
Replying to @spring

I’m here for it 😤

Spring 🏳️‍🌈
Replying to @andy

when the beta invites were sent around on twitter, everyone took pains to say it was "postS" not "post". i myself checked several times. some alts: dispatch.cv memos.cv friends.cv club.cv

Spring 🏳️‍🌈
Replying to @andy

mutuals.cv / mutual.cv

Guico
Replying to @andy

I still don’t get why this is separate from read.cv 😬 there seems to be significant overlap?

Andy Chung
Replying to @guico

I think the two will be tightly coupled - but having the two profiles separated feels like they address two different but symbiotic use cases for now

Benny Bowden
Replying to @andy

Two / 2 / 2️⃣ / ✌️!!!

Oliver Schwaiger
Replying to @benny @andy

Haha^^ why 3 exclamation marks? 🙈

Benny Bowden
Replying to @zehigel @andy

Ahhhh, I ruined it!

Oliver Schwaiger
Replying to @benny @andy

😅

Andy Chung

Ok posts.cv coming very soon ahhhhhh 💥

 @
Replying to @andy

👏🏻👏🏻

Bobby Solomon
Replying to @andy

2️⃣✨

Muhammed Kılıç
Replying to @andy

posts.cv 🥇🤞

Jenny Famularcano
Replying to @andy

Definitely 2✌🏼

miha
miha @miq
Replying to @andy

Def 2

Adrien Picard
Replying to @andy

+1 for 2️⃣

Leland Foster
Replying to @andy

2

Angela Martinez
Replying to @andy

2!!

Anton Stallbörger
Replying to @andy

2️⃣

Josh Byers
Replying to @andy

In my experience subdomains are better used for internal organizational structure. TLD with a path are better for UX. Also, simpler is almost always the right choice. So #2 would be best :)

Sasha
Replying to @andy

2️⃣

Chloe
Replying to @andy

2

AJ Adams
Replying to @andy

1️⃣ 😅

Samuel Kantala
Replying to @andy

2️⃣

Lorenzo de Lijser
Replying to @andy

2️⃣

Nathan Pokpongkiat
Replying to @andy

2️⃣

Laura 🦄
Replying to @andy

Definitely 2️⃣!

JC Alvarez
Replying to @andy

2️⃣

Joe Russell
Replying to @andy

read.cv/posts ?

Alexander Lewis
Replying to @andy

TLD!

Patrick
Replying to @andy

posts.cv 🤌

Ethan Mooney
Replying to @andy

posts.read.cv?

Bruno Figueiredo
Replying to @andy

Number 2 solves the access is a easier way.

Lisa Oreshkina
Replying to @andy

I thought you were planning to merge read.cv’s Explore with Posts later on So I was expecting read.cv/posts :) TLD otherwise

Facu Montanaro
Replying to @andy

posts.cv 💯

Mu-An Chiou / 邱慕安
Replying to @andy

2 ♡

André Mooij
Replying to @andy

posts.cv 🌹

Jonas Maaløe
Replying to @andy

posts.cv 🪩

Cory Etzkorn
Replying to @andy

read.cv/posts Otherwise posts.cv

Christian Vasile
Replying to @andy

No subdomain

Georgemaine
Replying to @andy

2️⃣ seems easier to remember. What’s your thinking on read.cv’s relationship to posts atm?

Dan Donald
Replying to @andy

read.cv/posts?

David Mendes
Replying to @andy

2 is catchier, but 1 makes more sense. read.cv/posts There’s no posts without readcv. At least for now.

Oliver Schwaiger
Replying to @andy

2️⃣

Michael Martino
Replying to @andy

2