We published our BeRealFan project on Behance. Thought I'd share a few thoughts on how we approached it.
Designing complex digital products is really about working within constraints. With BeRealFan, the tricky part wasn't making it look good – it was building one coherent interface across a bunch of different systems: microservices, payments, streaming, messaging, analytics. Each of them has its own logic. Design is what ties it all together into something that actually feels seamless.
The visuals are based on patterns people already know from social platforms – clear hierarchy, familiar interactions, consistent navigation. But there's also a bit of personality: subtle details and a lighter tone that make it stand out.
End result – a product where design helps manage complexity, not add to it.
More visuals on Behance.
Designing complex digital products is really about working within constraints. With BeRealFan, the tricky part wasn't making it look good – it was building one coherent interface across a bunch of different systems: microservices, payments, streaming, messaging, analytics. Each of them has its own logic. Design is what ties it all together into something that actually feels seamless.
The visuals are based on patterns people already know from social platforms – clear hierarchy, familiar interactions, consistent navigation. But there's also a bit of personality: subtle details and a lighter tone that make it stand out.
End result – a product where design helps manage complexity, not add to it.
More visuals on Behance.
🔥6❤4👍2
Invariance is something we love. Sometimes you don't need to create a new product to simplify life and optimize the work of an entire team. That's exactly what we did at Evrone when we improved our time tracking workflow – we took an existing system and customized it to fit our needs. That's how Timesheet came to be.
We use Yandex.Tracker for tracking work hours. The system works well and is convenient, but there were nuances we didn't really like. For example, we wanted not just to log time, but to manage entries, edit them, and see the full picture without unnecessary effort. Wait for Tracker's creators to improve it? Not our style. We simply built our own tool inside it.
We built in everything needed for smooth work:
▪️ Detailed reports on tasks and projects broken down by day, week, and month
▪️ The ability to edit time entries
▪️ Automatic loading of active tasks
▪️ Filters by status, queues, and projects
▪️ Support for two languages and time zones
▪️ Input in minutes by default — it really is simpler
And yes, we know: time tracking issues in Tracker aren't something only our team faces. That's why Timesheet is open source – it's open to everyone. Any team can take the code, customize the logic or interface to fit their own workflows.
For us, this project is an example of how customizing existing tools helps build transparent development processes. Sometimes you don't need to reinvent the wheel at all – you can just tweak it a little.
You can learn more about the project here.
We use Yandex.Tracker for tracking work hours. The system works well and is convenient, but there were nuances we didn't really like. For example, we wanted not just to log time, but to manage entries, edit them, and see the full picture without unnecessary effort. Wait for Tracker's creators to improve it? Not our style. We simply built our own tool inside it.
We built in everything needed for smooth work:
And yes, we know: time tracking issues in Tracker aren't something only our team faces. That's why Timesheet is open source – it's open to everyone. Any team can take the code, customize the logic or interface to fit their own workflows.
For us, this project is an example of how customizing existing tools helps build transparent development processes. Sometimes you don't need to reinvent the wheel at all – you can just tweak it a little.
You can learn more about the project here.
Please open Telegram to view this post
VIEW IN TELEGRAM
🔥4👍2
The cost of a wrong tech choice can be higher than you think. Brag House found out the hard way.
They built a platform🎮 for student gamers – not hardcore pros who play 24/7, but casual players spending just a few hours a week gaming. College tournaments, live commentary, post-match interviews, leaderboards, virtual currency. The niche was wide open, and demand was real.
But their AWS Amplify prototype was holding them back. No room to grow – only to rewrite.🧐
We rebuilt the backend with Python Django. Stack: Python3, Django, Celery, AWS (EC2, RDS, S3), Stripe, Twitch API, Expo Push API. Along the way, we added message notifications and a daily free loot box with virtual currency.
The project secured funding, launched private tournaments, and expanded internationally with major partnerships.🔥
If your project is struggling to scale – we know how to fix it. Let’s talk.
👉 More details – here.
They built a platform
But their AWS Amplify prototype was holding them back. No room to grow – only to rewrite.
We rebuilt the backend with Python Django. Stack: Python3, Django, Celery, AWS (EC2, RDS, S3), Stripe, Twitch API, Expo Push API. Along the way, we added message notifications and a daily free loot box with virtual currency.
The project secured funding, launched private tournaments, and expanded internationally with major partnerships.
If your project is struggling to scale – we know how to fix it. Let’s talk.
Please open Telegram to view this post
VIEW IN TELEGRAM
Please open Telegram to view this post
VIEW IN TELEGRAM
🔥5❤2👍2
Vue or React – which one do you choose? We brought together experts to discuss the strengths and weaknesses of both technologies.
Some developers bet on React for its flexibility, scalability, and powerful ecosystem. Others vote for Vue for its simplicity, clean architecture, and easy entry into the profession. So what is the fundamental difference? How do both tools perform in real-world projects? What are their pros and cons? And what ultimately becomes the deciding factor for a team?
📌 Vasily Vanchuk, Lead Expert at T‑Bank
📌 Nikita Zuyanov, Senior UI Developer at Ozon
📌 Denis Chernov, Lead Developer at SM Lab
📌 Ivan Malyugin, Head of Platform Development at Beeline
📌 Semyon Levenson, Head of Client Development at Yandex ID
What you agree or disagree with – find in our cards.
Some developers bet on React for its flexibility, scalability, and powerful ecosystem. Others vote for Vue for its simplicity, clean architecture, and easy entry into the profession. So what is the fundamental difference? How do both tools perform in real-world projects? What are their pros and cons? And what ultimately becomes the deciding factor for a team?
📌 Vasily Vanchuk, Lead Expert at T‑Bank
📌 Nikita Zuyanov, Senior UI Developer at Ozon
📌 Denis Chernov, Lead Developer at SM Lab
📌 Ivan Malyugin, Head of Platform Development at Beeline
📌 Semyon Levenson, Head of Client Development at Yandex ID
What you agree or disagree with – find in our cards.
🔥3❤2👍2