Telegram 3.8 – New design, Stickers and Bots 2.0

Hi guys! We already know the new features for next Telegram version (3.8). Recall that Pavel said that something big is going to come! And those Bots 2.0 look like really cool.
telegra-update-bots

NEW DESIGN & STICKERS

  • Redesigned chat screens, optimized colors, new buttons and message bubbles, beautiful progress bars, revamped documents and other attachments.
  • Tap on any sticker to view its pack and add it to your collection. Preview and send stickers from the pack preview menu.

new-design

BOT API 2.0

  • Introducing Bot API 2.0, the biggest update to our bot platform since June 2015.
  • New inline keyboards with callback, ‘open URL’ or ‘switch to inline mode’ buttons help create seamless interfaces.
  • Bots can now update existing messages on the fly as you interact with them.
  • Prepare for the rise of location-based bots: all bots can now ask users to share their location.
  • Inline bots can now send all attachments supported in Telegram (videos, music, stickers, files, etc.).
  • Try out these sample bots to see what’s coming your way soon: @music, @sticker, @youtube, @foursquare

You have more info at Telegram Blog!

Geeks Channel
Follow us on Telegram Geeks Channel.

forward

Daniel LaRusso

Daniel LaRusso

Engineer, developer, open source enthusiast, passionate for technology. Consultant and researcher in robotics and automation.

You may also like...

9 Responses

  1. rocksteadyFTW says:

    can’t wait to see the new location feature!!

  2. Stephen says:

    was really hoping for that telephony feature… :/

  3. Enzo says:

    Nice update!

  4. Pedram says:

    Why they removed “save to music ” ?????
    it’s very annoying.

  5. Chris says:

    Can we please stop misdirecting the clipboard when copying messages? I copy something I don’t expect telegram to interfere and introduce unexpected behaviour of higher level software layers. Telegram currently adds its own text to anything you copy, this behaviour breaks clipboard expected behaviour and represents a general anti pattern in application design. If you want to give the user the ability to add custom text to any copied text, create a bespoke copy context menu option, do not twist exiting mechanisms. As it happens, this is absolutely infuriating since every time something is copied to clip board it is prefixed with text that has to be manually deleted each time.
    If we have people who think this is a way forward on the design team, I am very worried for the other foibles in design, perhaps more critical areas within the application such as in security or reliability.
    Private messages are constrained to the device they are created on. This is annoying not least because you cannot share access to secure messages between devices, but when multiple devices each create a secure message to the same contact, said contact has no way to differentiate what secure message thread belongs to what device, or even an ability to at least label each secure message uniquely. The whole secure messages use case needs carful revaluation since it has too many usage flaws.
    There has been a bug where secure message at random moments, delete themselves. This has never been fixed since the start. More flexible options in the expandability of the windows that display stickers and gifs etc, needs to be enabled. Currently these times tabulate in a fixed window of only half the screen which can be infuriating.

  6. Chris says:

    Ref Android client > Can we please stop misdirecting the clipboard when copying messages? I copy something I don’t expect telegram to interfere and introduce unexpected behaviour of higher level software layers. Telegram currently adds its own text to anything you copy, this behaviour breaks clipboard expected behaviour and represents a general anti pattern in application design. If you want to give the user the ability to add custom text to any copied text, create a bespoke copy context menu option, do not twist exiting mechanisms. As it happens, this is absolutely infuriating since every time something is copied to clip board it is prefixed with text that has to be manually deleted each time.

    If we have people who think this is a way forward on the design team, this makes me nervous, for what other glaring flaws lurk in the application that relate to aspects of security or reliability.

    Private messages are constrained to the device they are created on. This is annoying not least because you cannot share access to secure messages between devices, but when multiple devices each create a secure message to the same contact, said contact has no way to differentiate what secure message thread belongs to what device, or even an ability to at least label each secure message thread uniquely so as to in a fashion – achieve the same thing. The whole secure messages use-case needs carful revaluation since it has too many usage flaws and does not have parity with all non-secure messaging features either.

    There has been a bug where secure message therads, at random moments, delete themselves. This has never been fixed since the start.

    More flexible options in the expandability of the windows that display stickers and gifs etc are needed. Currently these items tabulate in a fixed window of only half the screen, which can be infuriating.

    Being able to move message threads into custom groupings (tabs / lists ) would be good. Currently there is no grouping functionality, all message threads appear in a single list. The ability to split out message threads into groups of related threads would clean up the UI, and provide better at a glance information. Groups such as family, friends, groups, info, etc etc.

  7. Chris says:

    Better handling of different video/ media formats is needed. Mp4 is the only format that is correctly presented as an in-thread playable object. Other file types present only as files. Same for gifs, which are ultimately converted to MP4 in Telegram but preserve an autoplay feature which is more metadata ensuring gif sources will autoplay in the client, ergo, should autoplay be a feature, not a side effect of the source format?
    Let videos be videos, if the underlying format is always MP4, why should telegram treat them differently within the UI when the underlying format ends up the same? Better to abstract the format such that the issue of file type is no longer a going concern for the end user.
    Simply present videos as videos, If a user drags a gif, an MP4, an MKV, whatever media, Telegram should just deal with it and convert it to, and present as, an in-thread playable object to the recipient, where the underlying format , be it MP4 or x265 or the soon to be successor AV1.
    Since you have associated the ability to auto download and autoplay with source gif images, it perhaps makes sense to enable autoplay for source media that was originally a gif as default, but such metadata should be editable by the sender before submission of said media. Another method would be to offer users the ability to autoplay any video format based on file size instead ?

    When copying images to a thread, provide the ability for the image editor to intercept, as it does with photos taken via the camera.

Leave a Reply

Your email address will not be published. Required fields are marked *