|
|
|
|
|
|
by aeonflux
2193 days ago
|
|
|
Yeah, that sucks big time. I can accept the closed ecosystem, not being able to use open protocols. If you wan't to do something far away from known standards, then this might be a requirement. But locking users into the service like this gets into the way of their general stance. Perhaps they plan to introduce custom domains in future? Maybe this just didn't fit into the initial release? |
|
|
Most probably.
This is how basecamp always did thing, even back when it was called 37signals: they release a MVP, they generate money as early as they can, then they start agile feedback loop, improving the product throught many iterations.
They were one of the teams that made agile popular after all.
They also promote the philosophy of rejecting features and not noting the requests for them down.
Only a feature that has been requested and rejected enough times pass their "filter" of something that should be added to the product.
I'm betting a custom domain name will pass such filter and end up being implemented in one year or two.