149 karma · joined September 9, 2012
There are absolutely no "designed-for-URX tags" that we have documented. All of the meta/link tags that are documented are usable by Twitter, Facebook, Google, etc. It might not be entirely clear in our documentation unfortunately, but the "omnilink standard tags" are actually just an extension of Google's app-indexing tags, and are fully compatible with their initiative.
[full disclosure, I'm an engineer at URX]
[full disclosure, I'm an engineer at URX]
1. There is no third-party service that needs to be intergrated into the mobile application for omnilinks; you can simply prepend "http://urx.io/" in front of your normal web URL, and, assuming you have deeplinks installed on your mobile application, we will try to bring your users to the app if they have it installed.
2. It does a little more than any Android intent. It works across all platforms and degrades gracefully; you can't text a plain Android intent to a restaurant on Yelp and have an iPhone recipient view the content.
[full disclosure, I'm an engineer at URX]
In my experience developing both in net-new codebases in addition to large legacy codebases, there certainly are cases where better abstractions/paradigms equate to less code, and ultimately to less complexity. Yet at the same time, these improvements tend to yield more flexibility and capability, potentially providing additional features (sometimes entirely by chance). I find that in these such cases, it actually becomes easier to reason about what your code does, because you have come to a point where you can clearly generalize about your software.
On the flip-side, I can also greatly empathize with the author, as even in my attempts to generalize the functionality of software, there often exist ugly one-off bits of critical business logic that invariably dirty the water. In these such situations, it seems to become harder and more complex to build generic code, and you are much better off just sticking to the straightforward implementation without allowing for any of the bells-n-whistles that a more generalized approach might offer.
TL;DR--It really depends on the situation, in my opinion, but this shouldn't prevent you from trying to find a generic solution that is less complex yet offers more.
This does of course make for the argument that perhaps this style of writing is not suitable for skimming, though I'd agree with another comment on this post that after reading the part about 95% of 3,875,000 equating to approximately 1,000,000, I was definitely more perceptive that something silly was going on.