https://kotlinlang.org logo
Join Slack
Powered by
Question to people considering using Compose for D...
# compose-desktop
o
Question to people considering using Compose for Desktop in their projects: job, commercial, hobby. How much it will affect you when we reach 1.0 version of Compose for Desktop in terms of ability to use the technology? Update: a bit rephrased question, to emphasize that we all want to reach 1.0, and question is mainly about how important the version for convincing other people. 1️⃣ - critical, blocker 2️⃣ - important, but not blocker 3️⃣ - not important, version is just a number
3️⃣ 36
1️⃣ 5
2️⃣ 17
d
I will expand a bit on why (3) for me. At this point I am really used to 
0.*
software. Especially with everything that is mobile/desktop related. So, version doesn’t matter at all to me. What matters though: amount of documentation, examples and people using technology.
👍 2
s
[2] - Being in 
0.*
or alpha status is fine for hobby projects, but it's hard to sell an immature technology to management/architects. Especially if throughout the project you have pretty much guaranteed additional maintenance costs due to changing API's. (looking at you, 
@Experimental*
annotations)
👍 2
o
(3) for now I only use Compose for Desktop for my side-projects, so I'm OK with unstable versions
j
Personally -> it is just a number, IDC Work -> it isn't just a number, if it is "not stable" I cant convince to use it easily This applies both, Desktop and Android, and even, I have a question here. You can use Jetpack Compose in Android without using AS Canary via JetBrains plugin, so... if Jetpack Compose Desktop reaches 1.0, it means Android is 1.0? This question is more for @jim probably
a
Well, for me being a hobbyist (3). I'm with @Dmitry's opinion.
What matters though: amount of documentation, examples and people using technology.
j
Yes, Compose Desktop would not reach 1.0 before Compose its self reaches 1.0. Obviously this channel is 100% comprised of early adopters who are willing to use Compose despite the lack of a 1.0 version number, but it is interesting to see if a stable version is a blocker for anyone.
c
I’m working on a fairly large hobby project that I would like to distribute eventually. I do plan on waiting until a stable 1.0 before I start distributing it, but being in alpha is not preventing me from being fully committed to this tech stack
a
Currently, my only limitation is the lack of time to try it. I want to try @laht's thee.kt for desktop backend and I think it should be possible to use it with compose.
j
Well, I will go for 1️⃣ because I want to use it in job 🤣
How many milestones will there be? Yesterday I was wondering precisely
a
[1] For job. Mainly because I can't go live with an alpha release.
t
❸ and that includes for professional usage.
c
@olonho my team has built a small application that we're ready to ship internally but our biggest blocker is still generating/signing the application. For us the best improvement would be to signing being built into Gradle in some way/some build and signing wizard.
👍 1
o
Signing for macOS, right?
c
Yeah. We keep trying and failing. We've seen the docs (that were updated twice recently) but it's less friendly than we thought it'd be.
I understand it's pre-alpha so I'm not complaining. But compose desktop has gotten our entire android team excited about building desktop apps and we're so lost on how to distribute.
o
I investigated that couple days ago, will try to provided improved tooling in Gradle plugin.
c
🙏 that would be great. Or maybe even just really straight forward docs for Mac? Apples documentation on it was impossible for us to follow, but it just seems like we're not savy to desktop distribution space.
o
Generally, signing on macOS could be similar to https://www.electronjs.org/docs/tutorial/code-signing
c
Ooh. May have to take a look at that. Thanks
m
Until recently there have been a lot of issues with jpackage and code-signing but according to the JBS they should be fixed by now. A basic description of the process can be found here: https://docs.oracle.com/en/java/javase/15/jpackage/support-application-features.html#GUID-8D9F0607-91F4-4070-8823-02FCAB12238D although a more detailed description of the process would be very helpful 😉
3 Views
Open in Slack
PreviousNext
Powered by