Skip to content

added a doc for native navigation #9784

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: development
Choose a base branch
from

Conversation

karahanharunn
Copy link
Contributor

No description provided.

@ConnorLand
Copy link
Collaborator

Hi @karahanharunn I've slacked you some questions about this. It's targeting Mx8 docs currently, which we don't update anymore, and it feels a bit more like a blog/RN blurb. Let's find the best place for this info together over Slack.


## Key Improvements

By switching to native navigation, you will immediately benefit from:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm going to pare this section down so it's smaller, and fits the docs.mendix voice, but I'll ensure readers understand the benefits of native navigation.

* **⚙️ Optimized View Hierarchy**
The new navigation system reduces the complexity and depth of the view hierarchy. This not only improves performance but also enhances compatibility with automation tools like Appium that can have restrictions on view depth.

## Breaking Changes & Customization Limits
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we have any other docs on our site which discuss these certain JS customizations?

>
> **Workaround:** Most apps already include top padding on their pages, which avoids this issue. We recommend ensuring your page content has adequate padding below the header.
>
> **Solution:** We are developing a native button widget that will resolve this edge case. These will be released in a future update.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@karahanharunn can you please make a note in the JIRA issue you have for this software fix? The note should add a step like "amend docs". That way you'll be reminded to PR this doc so we can announce your improvements to the world.


## Introducing Native Navigation in SP 11

With the release of Service Pack 11, we are excited to introduce a completely revamped native navigation system for all apps. This fundamental change moves navigation from a JavaScript-based implementation to the underlying native platform APIs, delivering significant improvements in performance, user experience, and memory management.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Need to mention the Native Mobile Builder (where these improvements are situated) more, and maybe link to other NMB stuff.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants