4 ms·
> building web properties This phrase gave me pause (why not just say "making wesbites"?), but I think I have a handle on what it implies. "Making websites" i
by gaur 10y ago
> building web properties
This phrase gave me pause (why not just say "making wesbites"?), but I think I have a handle on what it implies.
"Making websites" is what you do when your main deliverable is content. Maybe you throw in some javascript for a little aesthetic kick or some nice features, but if a user comes to your website with javascript disabled, your goal is to still get the content to them.
"Building web properties" is what you do when your main deliverable is non-content: ad clicks, tracking, etc. Whatever content you offer on the site is just a honeypot. If a user comes to your website with javascript disabled, your goal is to intentionally turn them away because they've refused the delivery of your non-content.
- dwaltrip 10y agoI used the term "properties" as I thought it would be a more generic term. We are past the days where the internet is only used for static web pages. I wasn't trying to imply monetization via ads. You paint a stark dichotomy between static websites and javascript powered "content honeypots". There are millions of web apps out there that are not the latter, and use javascript to provide real value.
- smsm42 10y agoRegular people build websites. Enterprises create (or, more frequently, acquire) web properties. Buying a website for 100M dollars sounds insane, buying a "web property" sounds distinguished.