We are attaching a breakdown of the Final Results for each submission.

1. Final Results:

Initially, for preliminary testing published on contest.com, we ran each test in a separate process. This allowed us to fully evaluate even solutions that crashed or hung on specific tests. However, this method disrupted many participants' performance optimizations and introduced substantial noise into the results.

Therefore, for the final evaluation, we executed all tests in a single process using a grader closely resembling the provided contest-grader.cpp. Consequently, solutions that crashed or hung on any test received a final score of 0.

2. Post-Contest Corrections:

After announcing preliminary results, several participants submitted bug fixes via comments on contest.com. Although we typically do not accept post-contest corrections, one corrected solution turned out to be significantly faster than any solution submitted during the contest. As an exception, we decided to evaluate all corrected submissions and include them in the final standings. To maintain fairness, these late submissions incurred a 20% penalty on the prize amounts awarded.

@ContestBot is now ready to accept submissions for the JavaScript Contest, Round 2.

New deadline: 23:59 on April 27 (Dubai time)

Build the application, then prepare:

- A ZIP-archive with the following structure:
-> dist - folder with the build.
-> src - folder with the app's source code.
-> contest.md – 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 A repository.

Your repository may stay private until the deadline.

We are pleased to issue the following clarifications regarding the Android Contest.

Q: Do I need to build these screens as a standalone project?
A: You must implement the new screens directly into the Telegram for Android app, fully preserving all existing profile features. To sum up – the new design flow must replace the current one.

Q: How will I submit my work and what will I need to provide?
A: You’ll need to submit both: an .APK file, and a link to your GitHub repository. For reference, here are the submission guidelines from one of our previous Android contests.

Q: Can we get the source files for the design mockups and animated demo?
A: Please use the files that have already been provided.

Q: Can I use X, Y, Z?
A: You must use Java without any third-party UI frameworks – and you should avoid introducing new dependencies into the project. To sum up – any changes you make must remain consistent with the existing codebase.

Q: What are the floating icons that get hidden when a profile is collapsed?
A: These icons come from either the custom profile appearance or from an active gift. For reference, check out @durov.

Q: Can we further utilize the camera cutout position on certain devices?
A: Absolutely.

Q: Do I really need to build the profiles from scratch?
A: We do not impose any restrictions on whether you should build it from scratch or not – focus on the outcome from the user’s perspective. What matters most is the quality and polish of the final result. That said, a from-scratch approach would be more beneficial in the context of eliminating legacy bugs.

Q: Can we have mockups for the Settings screen?
A: Feel free to implement this screen as you see fit. We consider this as a bonus task.

Q: Which link should we send in 'Profile Default 3.png'?
A: If the other party has incoming calls restricted, send them a link via 'Calls' → 'Create Call Link'.

Q: The icons provided earlier have a solid background.
A: We apologize for the inconvenience. We are attaching below the updated icons.