Instructions for integration into existing app

[djMax]

The forcereact cli provides an easy way to get started if you are generating a new app. It contains some best practices that can be used to figure out how to integrate the SF RN sdk and the native sdk's, but it would be even better if a clearly documented step by step approach would be published about how to integrate the sdk's into an existing React Native app.

[bbirman]

Thanks for the feedback, we'll look into it

[oktalk]

Has anybody successfully done this? I would like to use a RN framework (like ignite) so it would be nice to have some guidance on integrating forcereact into an existing project.

[JFoxUK]

@bbirman is there any documentation you can point us to for this or any rough instructions you can give us while you write the official docs?

[JFoxUK]

@djMax - did you ever manage this?

[djMax]

Nope

[JFoxUK]

@wmathurin any update here? @bbirman ?

[JFoxUK]

@wmathurin @bbirman any updates?

[JFoxUK]

@wmathurin @bbirman - any update?

[galensalesforce]

Hi @JFoxUK -- I'm a new PM on the Mobile SDK team. Thanks for following up on this. I just added this documentation update to our backlog. This documentation update requires more dev work than a typical docs update -- to verify that our instructions are correct, we'll spin up an RN app from scratch and follow our own steps to integrate MSDK into it. I'll keep you in the loop as we make progress.

[marissajmc]

Hi @galensalesforce is there an example in the current documentation of how to implement SFMC mobile app event tracking in React Native?

[JFoxUK]

@galensalesforce - any news?

[vishnudastk2005]

@galensalesforce . Hi galen, any updates.

[JFoxUK]

@galensalesforce its really disappointing that this keeps been ignored.

[galensalesforce]

Thanks all for following up about this -- and we appreciate your patience! MSDK is a small, open-source team that supports multiple platforms.

More info on this topic here. To summarize, we've decided that the best first step is to upgrade Mobile SDK support for React Native so that our forcereact command runs the RN CLI internally. This way, there will be far fewer steps required to add MSDK into an existing RN app to begin with. Our team is currently working on this upgrade for our 12.0 release.

[RohitSyngenta]

Is there anyway to handle the progress percentage with this SDK ?

[wmathurin]

@RohitSyngenta What did you mean by "Is there anyway to handle the progress percentage with this SDK ?"

[JFoxUK]

@galensalesforce @wmathurin - any updates here?

[ivanoikon]

16 months and still no updates? It's absolutely annoying that this SDK doesn't have a way to integrate into an existing RN project.

[JFoxUK]

Yep, @galensalesforce promised to keep us in the loop 5mo ago and never did.

[kqisalesforce]

Hi @JFoxUK, apologies for the delay. Galen has rotated onto a new team and is no longer on Mobile SDK. Here’s an update that was also posted on the Trailblazer Community.

The main reason we cannot provide step-by-step documentation for Mobile SDK integration into an existing RN app is our deep level of integration with the consuming app. We expect the generated app structure to allow these deeper integrations like biometric auth to work out of the box. I will make sure the team responds to any specific integration questions or issues that come up when trying to integrate Mobile SDK into your existing RN app. One thing we recommend is generating a sample app with forcereact then moving the assets into your existing app. One thing we have discussed is having forcereact leverage RN's CLI vs our own. This would have the generated application structure more closely align to RN CLI structure which could help with integrations into existing apps.

I'm curious what type of app are you integrating or how are you wanting to use the Mobile SDK in your RN app. This could help us better understand how to help and possibly evolve the Mobile SDK.

Again, I apologize if we caused you frustration our team is very small and we try to address every issue and question that comes in from our over 3000+ bespoke application teams.