여러 개의 Discourse 포럼에서 활동하고 계신다면, 더 빠르고 깔끔하게 연결 상태를 유지할 수 있는 방법을 원하셨을 것입니다. DisCorkie를 통해 바로 그걸 만들고 있습니다. DisCorkie는 여러 포럼을 하나의 앱에서 접근할 수 있게 해주는 현대적인 Discourse 클라이언트로, 모든 플랫폼에서 네이티브 경험을 제공합니다.
DisCorkie는 여러 Discourse 커뮤니티를 한 곳에서 관리할 수 있도록 도와줍니다. 더 이상 브라우저 탭을 오가거나 수동으로 계정을 전환할 필요가 없습니다. DisCorkie는 자신이 관심 있는 포럼에 집중하고 효율적으로 상호작용하기를 원하는 사용자를 위해 만들어졌습니다.
저는 DisCorkie를 적극적으로 개발 중이며, 커뮤니티의 아이디어나 제안에 항상 열려 있습니다. 이는 앱의 미래를 이끌어 나가는 데 도움이 될 것입니다.
주요 기능
다중 포럼 지원: 여러 Discourse 커뮤니티에 연결하고 매끄럽게 전환할 수 있습니다.
포럼 탐색: 주제나 언어별로 공개 포럼을 탐색할 수 있습니다.
네이티브 경험: Compose Multiplatform을 사용하여 빠르고 반응성 좋은 UI를 제공합니다.
Does it apply its own theme on all the instances or will custom theming remain after switching to an instance?
What were the use cases that led you to make this? My way of solving the problem was using PWAs (have each one on my desktop – both Mac and iPhone) and so the switching works on the OS level easily.
Does it apply its own theme on all the instances or will custom theming remain after switching to an instance?
The application theme respects the discourse instance theming. We use the information provided by the API to calculate what would be the best color for the theme that still respects the design system we are adopting. This is the result:
What were the use cases that led you to make this?
Basically the same use cases that led to the creation of the Discourse Hub. However, I’m extending this concept also for Desktop applications
What is the difference to the discourse-hub?
User experience
DisCorkie UI based on Skia(KMP) That give use several benefits when compared with the regular UI in HTML,CSS and JS: Performance, UI Consistency regardless the operating system or browser version, Smoother animations and transitions
Overal performance
Due to the fact DisCorkie does not use Javascript or HTML we can benefit from this architecture:
More robust multithreading support: Used to boost application performance due to parallel processing
The application does not need to load any HTML, CSS or JS file from the network. We only need the JSON payload. Less files to download, which makes it better for use in an unstable internet connection environment.
These reasons associated with caching make the app very resource-light
Comparison
This is the current Discourse Hub experience on an Android device.
The app opens the forum on the browser. So basically it works like a shortcut
This is how the DisCorkie app looks like on an Android Device
I didn’t get the chance to test (or even understand some technical details of) your solution yet, but just focusing on:
This is the behavior only on Android, and to be honest I feel like we could revisit this decision. Maybe the idea is that if you already have it installed as a PWA, it’ll open that instead, but the experience on iOS is so much better that I wonder if we shouldn’t go the same route on Android. /cc @pmusaraj
One big difference between the Hub and PWA on iOS is I can close easily a forum when needed reloading, for example ^[yes, we have a component for reloading, but it isn’t official and not totally 100% reliable]. PWA must be closed using OS-way. And I get urls much easily (not easily, but it is doable) from the Hub. Getting links from PWA is impossible — well, there was now two differences.
Looks really slick! Especially that subtle theming . Something like this would be great for power-users who manage multiple communities on desktop (like a TweetDeck), so might be worth putting a focus on centralized moderation/admin capabilities.
Quick update!
The Android version of DisCorkie is now live on the Google Play Store
Anyone can download it and start exploring their favorite forums right from their phone.
I know there are still a few features missing but I’m actively working on improving it and shipping new updates as soon as they’re ready. Your feedback is always welcome!
Thanks again to everyone who’s followed the journey so far.
Maybe I’m missing something, but after adding two forums all abilities to add a third one become greyed out, both the “add forum” on the left as well as “manage forums” –> “discover new communities”.
Removing one of the two forums enables the button again.
(I’m also unable to remove all forums but obviously that’s not a problem).
You’re not missing anything — the current version limits the number of forums. I’m planning to introduce support for adding more as part of DisCorkie Plus, the upcoming premium tier. That said, everyone who joined the early testing phase will get access to all premium features, including this one, once it’s available.
It would have been nice if it would have said so, since I spent half an hour on trying to figure out what was wrong.
You’ve also asked me and other members of the community to beta test something that turns out to be closed-source and paid. No problem but I would have liked to have known this upfront.
Thanks for your honest feedback and I truly apologize for the confusion and frustration this caused.
It was never my intention to mislead or hide anything from the community. I genuinely appreciate the time and effort you’ve put into testing DisCorkie, and I understand how it must have felt running into that limitation without a clear explanation.
You’re absolutely right that this should have been communicated more clearly from the start, and I’ll make sure to improve how these things are shared moving forward.
As for the paid tier — yes, DisCorkie is closed-source, and I’ve been exploring a small subscription (likely around 1.3 to 1.5 euros/month) as a way to help support ongoing development and cover costs. The app started as a passion project, but it’s grown to the point where sustainability became a consideration. That said, feedback like yours really helps shape how I approach things.
I genuinely value your opinion and would love to hear what you think about the pricing and overall direction. Thanks again for speaking up — I’m listening and learning.
Being the Solo DeV it can be easy to miss a few details. As you said honest feedback is great as it helps not only to find bugs, requested features but also gaps.
Thank you for creating a cool ap. Still early days but you have a great start and progress you have is quite decent.
Working with a company that makes VR headset there big weakness is making half decent release notes. Often they tell you after you identify a bug that it was known.
Worst release notes they had on one version said it improves your Amazon experience.
There after 7 years are finally doing much better and unlike yourself have a team working on their software.
. Something like this would be great for power-users who manage multiple communities on desktop (like a TweetDeck), so might be worth putting a focus on centralized moderation/admin capabilities.
Consider updating the original post to clarify things like this as you get more feedback.