
I’m building a native Telegram client for Windows Phone in 2026.
It’s called Vianigram, and it’s not a wrapper or a webview — it’s a real client built on top of MTProto.
The UI is still evolving, but the core is already working.
What works today:
• Full login flow (phone, SMS, 2FA, QR, signup)
• Real chats powered by MTProto (no stubs)
• Chat list with pagination and live updates
• Typing indicators, online status and read states
• Chat screen with message bubbles (text, photos, voice, documents, polls)
• Rich text support (bold, italic, spoilers, links, mentions)
• Voice messages with waveform + scrubbing
• Background sync using system tasks (no reliable push required)
• Toast notifications and live tiles generated locally
• Smart coordination between UI and background (single MTProto socket)
• Avatars with preview + HD async loading
• LRU cache for chat pages
What’s different:
Windows Phone push notifications are basically dead in 2026.
So instead of relying on push, Vianigram uses a hybrid background system:
• Periodic maintenance task (~30 min worst-case sync)
• VoIP-based triggers for near real-time wake events
• Local cache used for toasts and tile updates
This means:
You still get notifications, badges and live tiles — even without reliable push.
Limitations (alpha):
• Delays when the app is fully closed
• Calls UI not finished yet
• Proxy settings not wired yet
• Message send is optimistic (ack UI missing)
Why I’m building this:
Because Windows Phone deserved a real Telegram client.
And the platform is still more capable than people think.
Downloads and updates:
Telegram — search for PivoraApps or VianiumApps
☕ Buy me a coffee if you want to support the project
Not affiliated with Telegram.
Windows Phone is not dead yet.