<story><title>Telegram: Payments 2.0, Scheduled Voice Chats, New Web Versions</title><url>https://telegram.org/blog/payments-2-0-scheduled-voice-chats</url></story><parent_chain><item><author>perryizgr8</author><text>I don&amp;#x27;t understand why there are 2 slightly different websites. Both are good, just with minor changes to the fonts and spacing.</text></item><item><author>est</author><text>&amp;gt; With the new web versions you can get instant access to your chats on any device – desktop or mobile. These apps are incredibly efficient, requiring only a 400 KB download (that&amp;#x27;s like two photos of a medium-sized cat) and no installation.&lt;p&gt;webz.telegram.org and webk.telegram.org look amazing.&lt;p&gt;That&amp;#x27;s web apps done right. Small .js files intead of 20MB main.min.js crap.</text></item></parent_chain><comment><author>MildlySerious</author><text>Telegram outsources parts of its development into multi-stage coding contests[1] with prize money. I don&amp;#x27;t know why they decided to keep two separate versions in the end, but I assume they both came out of the Javascript contest.&lt;p&gt;[1] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;contest.com&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;contest.com&amp;#x2F;&lt;/a&gt;</text></comment>
<story><title>Telegram: Payments 2.0, Scheduled Voice Chats, New Web Versions</title><url>https://telegram.org/blog/payments-2-0-scheduled-voice-chats</url></story><parent_chain><item><author>perryizgr8</author><text>I don&amp;#x27;t understand why there are 2 slightly different websites. Both are good, just with minor changes to the fonts and spacing.</text></item><item><author>est</author><text>&amp;gt; With the new web versions you can get instant access to your chats on any device – desktop or mobile. These apps are incredibly efficient, requiring only a 400 KB download (that&amp;#x27;s like two photos of a medium-sized cat) and no installation.&lt;p&gt;webz.telegram.org and webk.telegram.org look amazing.&lt;p&gt;That&amp;#x27;s web apps done right. Small .js files intead of 20MB main.min.js crap.</text></item></parent_chain><comment><author>tenacious_tuna</author><text>They did this a while back with their Android (and iOS?) apps--they had the core Telegram app, and Telegram X. Both had 90% overlapping features, but some subtle differences. It&amp;#x27;s long enough ago that it&amp;#x27;s a bit fuzzy in my head, but I think X had slightly better reply gestures, and maybe chat pinning.&lt;p&gt;Later I think they absorbed the X features into the core app.&lt;p&gt;I can&amp;#x27;t decide if I think it&amp;#x27;s an awesome strategy to launch a self-competing project, or if it just leads to terrible internal issues. I&amp;#x27;m leaning more towards the former--I&amp;#x27;m a huge believer in the instructive power of contrast, and it&amp;#x27;s a lot &amp;quot;safer&amp;quot; to contrast against another one of your own products than a competitor. You control much more of the &amp;quot;experiment&amp;quot;, and you don&amp;#x27;t run the risk of cannibalizing your own users.&lt;p&gt;Plus, from an engineering standpoint, it forces you to have portable technologies and configs, and probably gives your team opportunities to learn from greenfield stuff that can then encourage refactors or other paying-down-tech-debt activities.&lt;p&gt;It&amp;#x27;s also just dang impressive that they&amp;#x27;re able to spin up multiple versions of the same app, and deploy them, and maintain them. That speaks volumes to me about their internal systems, build systems, resource allocation, etc.</text></comment>