feat: new onboarding step #3686
Conversation
danil-pavlov
force-pushed
the
mpp-explore-project
branch
from
d9aebb7
to
ecb5535
Compare
danil-pavlov
force-pushed
the
mpp-explore-project
branch
from
bea0114
to
1fc00ad
Compare
|
|
||
|  | ||
|
|
||
| ### Writing common declarations |
There was a problem hiding this comment.
Why is Gerund here?
Isn't it better to use "Write" instead of "Writing"?
I'm pretty sure that we should use imperative verbs instead.
| Writing the code only in common Kotlin has obvious limitations because it can't use any platform specifics. | ||
| Using interfaces and the [expect/actual](multiplatform-connect-to-apis.md) mechanism solves this. | ||
|
|
||
| ### Adding platform-specific implementations |
| 2. Switch between the `androidMain` and the `iosMain` modules. | ||
| You'll see that they have different implementations of the same functionality for the Android and the iOS source sets: | ||
|
|
||
| ```kotlin |
There was a problem hiding this comment.
Maybe using two different code blocks makes the different parts easier to read? 🤔
There was a problem hiding this comment.
Totally! we already started to do this in some later drafts as well
| These are both declarative UI frameworks, and you'll see similarities in the UI implementations. In both cases, | ||
| you store the data in the `phrases` variable and later iterate over it to produce a list of `Text` items. | ||
|
|
||
| ### The Android module |
There was a problem hiding this comment.
I expect here a verb. Like "update the android module" or something similar
| <toc-element id="multiplatform-mobile-dependencies.md" toc-title="3. Add dependencies"/> | ||
| <toc-element id="multiplatform-mobile-upgrade-app.md" toc-title="4. Upgrade your app"/> | ||
| <toc-element id="multiplatform-mobile-wrap-up.md" toc-title="5. Wrap up your project"/> | ||
| <toc-element id="multiplatform-mobile-update-ui.md" toc-title="3. Update UI"/> |
There was a problem hiding this comment.
I'm thinking about expanding the toc-title to make it more readable.
In the nav tree the titles should be short (like "Share more logic"), but in the title of the content I'd like to see something like "Share more logic between iOS and Android").
What do you think about this?
There was a problem hiding this comment.
Makes sense, I got rid of the acronym and expanded the header for the 5th step
No description provided.