@ContestBot is now ready to accept submissions for the Telegram JavaScript Contest.
Build the application, then prepare:
- A ZIP-archive with the following structure:
- A link to the commit on a public GitHub repository, forked from the Telegram Web K repository.
Your repository may stay private until the deadline.
Build the application, then prepare:
- A ZIP-archive with the following structure:
-> public - folder with the build.
-> src - folder with the app's source code.
-> readme.txt β a text file that briefly describes the approach used for each task.
- A link to the commit on a public GitHub repository, forked from the Telegram Web K repository.
Your repository may stay private until the deadline.
We were pleased to see both participants from Round 1 and those who joined the Telegram Contests for the very first time! The Contest Task, which covered multiple areas of the app (implementing a new feature, adding another feature that heavily relies on the existing codebase, and fixing an obscure issue), proved to be particularly challenging for the contestants, with no one completing all three tasks.
Most contestants focused on the Media Editor, so the judges adjusted their evaluation accordingly. After many hours of testing, we are pleased to confirm that Hip Hyena secured
Meet the winners!
1st PLACE β $10,000
2nd PLACE β $3,000
3rd PLACE β $2,000
4th PLACE β $500
β rebuilding penalty (β$100)
β rebuilding penalty (β$100)
β rebuilding penalty (β$100)
β rebuilding penalty (β$100)
β rebuilding penalty (β$100)
β rebuilding penalty (β$100)
β rebuilding penalty (β$100)
β rebuilding penalty (β$100)
P.S. Have a great week and stay tuned for more Telegram Contests in the coming month!
Please open Telegram to view this post
VIEW IN TELEGRAM
Please open Telegram to view this post
VIEW IN TELEGRAM
Forwarded from Telegram Designers
Please open Telegram to view this post
VIEW IN TELEGRAM
Prize fund: $50,000
Deadline: 23:59 on October 25th (Dubai time)
Who can participate: Everyone
Results: November 2024
Telegram is hosting a contest for iOS developers to build a media player from scratch.
The Task:
Implement a media player with support for HLS streaming (for both audio and video) into Telegram for iOS. The player must support both automatic and manual switching between available video streams, with automatic switching based on network bandwidth
Contest Requirements:
β Your media player must replace the AVPlayer currently used in the app.
β The final implementation must not cause any performance issues, app or media playback instabilities.
β Using a web view to render audio or video is prohibited. You may either implement everything in native code or use a hybrid solution, where data management is handled in JavaScript (via a web view or JavaScriptCore) and rendering is performed in native code.
β You may use hls.js as a reference.
For test media samples join @hls_samples.
Evaluation:
During the evaluation stage, we will review your code and test the submission under various conditions with multiple media on a range of iOS devices (iOS 12 β iOS 18).
Winners may be offered a chance to explore further cooperation opportunities with Telegram.
Submissions:
Contestants will be able to submit their entries to @ContestBot at a later date. We will further clarify the submission instructions closer to the deadline.
P.S. We will provide limited guidance for this contest, to request clarification send your questions with #ios2024 in @contests.
Please open Telegram to view this post
VIEW IN TELEGRAM
Telegram Contests
It seems that many contestants misunderstood the task. We are happy to provide clarifications regarding the task requirements, which you will find below.
Q: Can AVFoundation / VideoToolbox / CoreVideo be used?
A: Yes, anything that doesn't use AVPlayer to handle HLS playback is allowed.
Q: Are third party libraries/frameworks allowed (e.g. ffmpeg)?
A: Yes, anything that doesn't use AVPlayer to handle HLS playback is allowed.
Q: What do you mean by "switching between available video streams"?
A: The ability to change between different quality levels or versions of the video based on factors like network bandwidth or user selection. The player should be able to automatically switch to the most appropriate stream depending on the network conditions, or allow the user to manually select a stream which they prefer.
Q: Are there any minimum technical requirements for a video player? Which features are prioritized?
A: Video playback must be hardware-accelerated.
Q: Do we need support for offline playback?
A: No.
Q: Is it necessary to replace something specific in the source code of Telegram iOS from AVPlayer to our self-written player or all?
A: You only need to replace the relevant code in
Q: Which formats and codecs should be supported with HLS and video decoding?
A: fmp4 / H264 / AAC.
Q: Will there be any guidelines on how switching between available qualities should be implemented on the UI/UX part?
A: The UI is already implemented. Quality switching is handled here.
Q: Can AVFoundation / VideoToolbox / CoreVideo be used?
A: Yes, anything that doesn't use AVPlayer to handle HLS playback is allowed.
Q: Are third party libraries/frameworks allowed (e.g. ffmpeg)?
A: Yes, anything that doesn't use AVPlayer to handle HLS playback is allowed.
Q: What do you mean by "switching between available video streams"?
A: The ability to change between different quality levels or versions of the video based on factors like network bandwidth or user selection. The player should be able to automatically switch to the most appropriate stream depending on the network conditions, or allow the user to manually select a stream which they prefer.
Q: Are there any minimum technical requirements for a video player? Which features are prioritized?
A: Video playback must be hardware-accelerated.
Q: Do we need support for offline playback?
A: No.
Q: Is it necessary to replace something specific in the source code of Telegram iOS from AVPlayer to our self-written player or all?
A: You only need to replace the relevant code in
HLSVideoContent.swift
where the AVPlayer is used for handling HLS streamsQ: Which formats and codecs should be supported with HLS and video decoding?
A: fmp4 / H264 / AAC.
Q: Will there be any guidelines on how switching between available qualities should be implemented on the UI/UX part?
A: The UI is already implemented. Quality switching is handled here.
Forwarded from Telegram Designers
ContestBot is now ready to accept submissions for the Design Competition Round 2.
Start the bot, choose βDesign Competition 2024 R2β, answer the botβs questions, then send:
- A link to either private or public channel that serves as a catalog where your videos are uploaded. Provide a table of contents, pin it. You are recommended to use @DesignCompetitionSample as a reference.
- An archive containing all your videos in their original resolution. Optionally, you may also include source files for your project (e.g., .aep files).
Note: Your channel may stay private until the deadline. Make sure you assign it a username after the deadline.
Start the bot, choose βDesign Competition 2024 R2β, answer the botβs questions, then send:
- A link to either private or public channel that serves as a catalog where your videos are uploaded. Provide a table of contents, pin it. You are recommended to use @DesignCompetitionSample as a reference.
- An archive containing all your videos in their original resolution. Optionally, you may also include source files for your project (e.g., .aep files).
Note: Your channel may stay private until the deadline. Make sure you assign it a username after the deadline.
Please open Telegram to view this post
VIEW IN TELEGRAM
Telegram Contests
iOS Contest 2024 Update
Dear contestants,
We apologize for the inconvenience with @hls_samples. Please apply the following patch to continue your development.
Additionally, we have extended the contest deadline by 24 hours.
New Deadline: 23:59 on October 26th (Dubai time)
Dear contestants,
We apologize for the inconvenience with @hls_samples. Please apply the following patch to continue your development.
Additionally, we have extended the contest deadline by 24 hours.
New Deadline: 23:59 on October 26th (Dubai time)
Prize fund: $50,000
Deadline: 23:59 on October 28th (Dubai time)
Who can participate: Everyone
Results: November 2024
Telegram is hosting a contest for Android developers to implement new features into the app.
THE TASK
Implement the features in accordance with the mockups provided in the archive below:
β Add Quick Share for channel posts when you tap and hold the share button.
β Add Chromecast support for media playback.
β Add QR Share button for Invite links.
β Add a tooltip for bots' Start button.
β Introduce new flow for upcoming video chats.
Contest Requirements:
General
β No third-party UI frameworks are allowed.
β The submission must be consistent with the existing Telegram for Android codebase.
β The app's stability and performance must not be affected with the changes you made.
β The app must be free of significant flaws (including crashes, visual glitches, noticeable element blinking, layout errors, and more).
Evaluation:
During the evaluation stage, we will review your code and test the submission on a wide range of Android devices.
Winners may be offered a chance to explore further cooperation opportunities with Telegram.
Submissions:
Contestants will be able to submit their entries to @ContestBot at a later date. We will further clarify the submission instructions closer to the deadline.
Please open Telegram to view this post
VIEW IN TELEGRAM
Telegram Contests
Android Contest 2024.zip
12.2 MB
Telegram Contests
This media is not supported in your browser
VIEW IN TELEGRAM
ContestBot is now ready to accept submissions for the Telegram iOS Contest 2024.
New deadline: 23:59 on October 27th (Dubai time)
Start the bot, choose βTelegram iOS Contest 2024β, answer the botβs questions, then send:
- A link to the commit on a public GitHub repository, cloned from the Telegram-iOS repository.
Note: Your repository may stay private until the deadline. Make sure your code is consistent with the reproducible builds process β we will build each app automatically. Entries failing to do so, will receive a relevant penalty.
New deadline: 23:59 on October 27th (Dubai time)
Start the bot, choose βTelegram iOS Contest 2024β, answer the botβs questions, then send:
- A link to the commit on a public GitHub repository, cloned from the Telegram-iOS repository.
Note: Your repository may stay private until the deadline. Make sure your code is consistent with the reproducible builds process β we will build each app automatically. Entries failing to do so, will receive a relevant penalty.
Forwarded from Telegram Designers
Design Competition 2024, Round 2: Submissions
We received 135 submissions for the Design Competition, Round 2.
Everyone is welcome to view the submissions while the Telegram judges conduct their own checks.
We received 135 submissions for the Design Competition, Round 2.
Everyone is welcome to view the submissions while the Telegram judges conduct their own checks.
ContestBot is now ready to accept submissions for the Android Contest 2024, Round 1.
New deadline: 23:59 on October 29th (Dubai time)
Start the bot, choose βAndroid Contest 2024 R1β, answer the botβs questions, then send:
- An
- A link to the commit on a public GitHub repository, forked from the Telegram-Android repository.
Note: Your repository may stay private until the deadline. Entries that are not using their own package id will be penalized.
New deadline: 23:59 on October 29th (Dubai time)
Start the bot, choose βAndroid Contest 2024 R1β, answer the botβs questions, then send:
- An
.apk
file (release build). Make sure your code is using your own package id. - A link to the commit on a public GitHub repository, forked from the Telegram-Android repository.
Note: Your repository may stay private until the deadline. Entries that are not using their own package id will be penalized.
Dear Contestants,
Here is the results schedule for the recent contests we held:
Design Competition, Round 2: Next Week
(A significant portion of the submitted apps cannot be built as intended and require direct involvement from our side in order to properly assess each contribution. We apologize for the inconvenience and appreciate your understanding. Each of such entries will be disqualified.)
Android Contest, Round 1: Today
Please open Telegram to view this post
VIEW IN TELEGRAM
We were pleased to see many veterans from our previous contests for Android Developers to join us in this round together with several newcomers! We hope this was a fun yet challenging experience for all of you.
In this contest, developers were required to implement several features into the Android app under a tight deadline. While evaluating submissions, we primarily assessed how well each app delivered two core features for this contest: the Quick Share feature in channels and Chromecast support.
Meet the winners!
1st PLACE β $8,000
2nd PLACE β $5,000
3rd PLACE β $3,000
4th PLACE β $1,500
As an exception and a final warning, we have waived the rebuilding penalty this time considering we have several newcomers. Stricter guidelines and more severe penalties will be introduced for future competitions.
We have also decided to award 10 other contestants a bonus of $500 for their contributions, and we hope to see them in the prize-winning spots next time. (More details and check if you are on the list β on contest.com)
That's all for today! More contests are on the way. Have a nice Sunday!
Please open Telegram to view this post
VIEW IN TELEGRAM
Everyone is welcome to participate, even if they didn't join Round 1.
Please open Telegram to view this post
VIEW IN TELEGRAM
Prize fund: $50,000
Deadline: 23:59 on December 21st (Dubai time)
Who can participate: Everyone, even if you didn't join Round 1
Results: December 2024
Telegram is hosting a contest for Android developers to enhance and upgrade the in-chat camera.
THE TASK
Adapt the existing in-chat camera with the camera for Stories, including all its features:
β Collages;
β Dual Camera Mode;
β Front Camera Flash;
β Widgets (for interactive widgets, i.e., reactions or links, your app may just apply a non-interactive entity over the canvas)...
Your implementation must remove any story-related restrictions or controls. Specifically, your app must not impose a limit on video length and should exclude interface controls that are only relevant for stories. Your app must retain the existing in-chat camera interface and flow before user opens the camera (i.e., the preview within the attachment menu).
Contest Requirements:
General
β Your app must provide a consistent and smooth recording experience that aligns with the device's native camera app.
β No third-party UI frameworks are allowed.
β The submission must be consistent with the existing Telegram for Android codebase.
β The app's stability and performance must not be affected with the changes you made.
β The app must be free of significant flaws (including crashes, visual glitches, noticeable element blinking, layout errors, and more).
Note:
Submissions that introduce improvements to video recording are likely to receive higher scores in this contest.
Evaluation:
During the evaluation stage, we will review your code and test the submission on a wide range of Android devices.
Winners may be offered a chance to join the
Submissions:
Contestants will be able to submit their entries to @ContestBot at a later date. We will further clarify the submission instructions closer to the deadline.
Please open Telegram to view this post
VIEW IN TELEGRAM
Telegram Contests
Android Camera Round 2.zip
9.6 MB