What’s the best practice to Expose Sitecore 9 APIs for Mobile Apps Development? [closed]












3















Currently, I am looking Sitecore CMS solution for native mobile app development.
Mobile App Team is using Swift for IOS and Java for Android.



So we have a limitation to use JSS react native for mobile app development while considering this limitation we need to use Sitecore as a headless CMS (using analytics, tracking, rule engine personalization, control on component rendering on the mobile app through Sitecore)



Note: I am using Sitecore 9



Please share your experience for the same










share|improve this question













closed as too broad by Peter Procházka, Gatogordo, Hishaam Namooya, Anicho, Dawid Rutkowski Feb 7 at 11:48


Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.














  • 1





    For the sake of clarity it is not necessary to use a client framework with JSS, the output is just (personalized) JSON. so react native is optional

    – Jan Bluemink
    Feb 7 at 9:05
















3















Currently, I am looking Sitecore CMS solution for native mobile app development.
Mobile App Team is using Swift for IOS and Java for Android.



So we have a limitation to use JSS react native for mobile app development while considering this limitation we need to use Sitecore as a headless CMS (using analytics, tracking, rule engine personalization, control on component rendering on the mobile app through Sitecore)



Note: I am using Sitecore 9



Please share your experience for the same










share|improve this question













closed as too broad by Peter Procházka, Gatogordo, Hishaam Namooya, Anicho, Dawid Rutkowski Feb 7 at 11:48


Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.














  • 1





    For the sake of clarity it is not necessary to use a client framework with JSS, the output is just (personalized) JSON. so react native is optional

    – Jan Bluemink
    Feb 7 at 9:05














3












3








3








Currently, I am looking Sitecore CMS solution for native mobile app development.
Mobile App Team is using Swift for IOS and Java for Android.



So we have a limitation to use JSS react native for mobile app development while considering this limitation we need to use Sitecore as a headless CMS (using analytics, tracking, rule engine personalization, control on component rendering on the mobile app through Sitecore)



Note: I am using Sitecore 9



Please share your experience for the same










share|improve this question














Currently, I am looking Sitecore CMS solution for native mobile app development.
Mobile App Team is using Swift for IOS and Java for Android.



So we have a limitation to use JSS react native for mobile app development while considering this limitation we need to use Sitecore as a headless CMS (using analytics, tracking, rule engine personalization, control on component rendering on the mobile app through Sitecore)



Note: I am using Sitecore 9



Please share your experience for the same







sitecore-api jss mobile






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Feb 7 at 7:20









Ashish BansalAshish Bansal

1,122316




1,122316




closed as too broad by Peter Procházka, Gatogordo, Hishaam Namooya, Anicho, Dawid Rutkowski Feb 7 at 11:48


Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.









closed as too broad by Peter Procházka, Gatogordo, Hishaam Namooya, Anicho, Dawid Rutkowski Feb 7 at 11:48


Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.










  • 1





    For the sake of clarity it is not necessary to use a client framework with JSS, the output is just (personalized) JSON. so react native is optional

    – Jan Bluemink
    Feb 7 at 9:05














  • 1





    For the sake of clarity it is not necessary to use a client framework with JSS, the output is just (personalized) JSON. so react native is optional

    – Jan Bluemink
    Feb 7 at 9:05








1




1





For the sake of clarity it is not necessary to use a client framework with JSS, the output is just (personalized) JSON. so react native is optional

– Jan Bluemink
Feb 7 at 9:05





For the sake of clarity it is not necessary to use a client framework with JSS, the output is just (personalized) JSON. so react native is optional

– Jan Bluemink
Feb 7 at 9:05










1 Answer
1






active

oldest

votes


















8














Sitecore JSS is pretty match to your requirements in terms you want to use analytics, tracking, rule engine personalization, control on component rendering. But you should't think about JSS in original meaning. JSS is based on the Layout Service which is awesome tool that allows us to retrieve content from Sitecore and still be able to use all features like tracking, personalization and so on.



You can still keep the development in the same way you are now, you just need to use an API provided by JSS to get content.



Please look at the following question and answer for understanding the process:
Share Sitecore content to Native Mobile Apps (IOS swift and Android java)



You can read more about Layout Service here: Sitecore Layout Service



Also feel free to have a look at an application we built for SUGCON 2018:



Mobile application and JSS



You can see the mobile app in action: (please start from 24th minute): Sitecore xConnect & Marketing Automation omni-channel demo. Our application is build on Xamarin but it doesn't matter as we send a simple HTTP requests via HTTP client. You can do the same using any platform.



Sitecore tree structure is represented below.



Mobile Application JSS - Sitecore Tree



Where "Home" item represents a main screen of mobile application and displays a list of services. Items under the Home are used as datasources for renderings that are set for the Home:



Mobile App JSS - Presentation



Renderings don't have any HTML behind, they are empty, and are used only to set associated content. When we request the Home item in Layout Service, it will return the following output: Home Screen JSON.



When we click on some service, we will call the API to get content for specific service. The output is here: Service Screen JSON



Personalization rules are in place too:



Mobile App JSS - Personalization rules



Finally, you can build any content structure, any navigation structure, use dictionaries and any other things you want and then Layout Service will provide it for you. I found it as a best tool to implement a headless solutions.






share|improve this answer
































    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    8














    Sitecore JSS is pretty match to your requirements in terms you want to use analytics, tracking, rule engine personalization, control on component rendering. But you should't think about JSS in original meaning. JSS is based on the Layout Service which is awesome tool that allows us to retrieve content from Sitecore and still be able to use all features like tracking, personalization and so on.



    You can still keep the development in the same way you are now, you just need to use an API provided by JSS to get content.



    Please look at the following question and answer for understanding the process:
    Share Sitecore content to Native Mobile Apps (IOS swift and Android java)



    You can read more about Layout Service here: Sitecore Layout Service



    Also feel free to have a look at an application we built for SUGCON 2018:



    Mobile application and JSS



    You can see the mobile app in action: (please start from 24th minute): Sitecore xConnect & Marketing Automation omni-channel demo. Our application is build on Xamarin but it doesn't matter as we send a simple HTTP requests via HTTP client. You can do the same using any platform.



    Sitecore tree structure is represented below.



    Mobile Application JSS - Sitecore Tree



    Where "Home" item represents a main screen of mobile application and displays a list of services. Items under the Home are used as datasources for renderings that are set for the Home:



    Mobile App JSS - Presentation



    Renderings don't have any HTML behind, they are empty, and are used only to set associated content. When we request the Home item in Layout Service, it will return the following output: Home Screen JSON.



    When we click on some service, we will call the API to get content for specific service. The output is here: Service Screen JSON



    Personalization rules are in place too:



    Mobile App JSS - Personalization rules



    Finally, you can build any content structure, any navigation structure, use dictionaries and any other things you want and then Layout Service will provide it for you. I found it as a best tool to implement a headless solutions.






    share|improve this answer






























      8














      Sitecore JSS is pretty match to your requirements in terms you want to use analytics, tracking, rule engine personalization, control on component rendering. But you should't think about JSS in original meaning. JSS is based on the Layout Service which is awesome tool that allows us to retrieve content from Sitecore and still be able to use all features like tracking, personalization and so on.



      You can still keep the development in the same way you are now, you just need to use an API provided by JSS to get content.



      Please look at the following question and answer for understanding the process:
      Share Sitecore content to Native Mobile Apps (IOS swift and Android java)



      You can read more about Layout Service here: Sitecore Layout Service



      Also feel free to have a look at an application we built for SUGCON 2018:



      Mobile application and JSS



      You can see the mobile app in action: (please start from 24th minute): Sitecore xConnect & Marketing Automation omni-channel demo. Our application is build on Xamarin but it doesn't matter as we send a simple HTTP requests via HTTP client. You can do the same using any platform.



      Sitecore tree structure is represented below.



      Mobile Application JSS - Sitecore Tree



      Where "Home" item represents a main screen of mobile application and displays a list of services. Items under the Home are used as datasources for renderings that are set for the Home:



      Mobile App JSS - Presentation



      Renderings don't have any HTML behind, they are empty, and are used only to set associated content. When we request the Home item in Layout Service, it will return the following output: Home Screen JSON.



      When we click on some service, we will call the API to get content for specific service. The output is here: Service Screen JSON



      Personalization rules are in place too:



      Mobile App JSS - Personalization rules



      Finally, you can build any content structure, any navigation structure, use dictionaries and any other things you want and then Layout Service will provide it for you. I found it as a best tool to implement a headless solutions.






      share|improve this answer




























        8












        8








        8







        Sitecore JSS is pretty match to your requirements in terms you want to use analytics, tracking, rule engine personalization, control on component rendering. But you should't think about JSS in original meaning. JSS is based on the Layout Service which is awesome tool that allows us to retrieve content from Sitecore and still be able to use all features like tracking, personalization and so on.



        You can still keep the development in the same way you are now, you just need to use an API provided by JSS to get content.



        Please look at the following question and answer for understanding the process:
        Share Sitecore content to Native Mobile Apps (IOS swift and Android java)



        You can read more about Layout Service here: Sitecore Layout Service



        Also feel free to have a look at an application we built for SUGCON 2018:



        Mobile application and JSS



        You can see the mobile app in action: (please start from 24th minute): Sitecore xConnect & Marketing Automation omni-channel demo. Our application is build on Xamarin but it doesn't matter as we send a simple HTTP requests via HTTP client. You can do the same using any platform.



        Sitecore tree structure is represented below.



        Mobile Application JSS - Sitecore Tree



        Where "Home" item represents a main screen of mobile application and displays a list of services. Items under the Home are used as datasources for renderings that are set for the Home:



        Mobile App JSS - Presentation



        Renderings don't have any HTML behind, they are empty, and are used only to set associated content. When we request the Home item in Layout Service, it will return the following output: Home Screen JSON.



        When we click on some service, we will call the API to get content for specific service. The output is here: Service Screen JSON



        Personalization rules are in place too:



        Mobile App JSS - Personalization rules



        Finally, you can build any content structure, any navigation structure, use dictionaries and any other things you want and then Layout Service will provide it for you. I found it as a best tool to implement a headless solutions.






        share|improve this answer















        Sitecore JSS is pretty match to your requirements in terms you want to use analytics, tracking, rule engine personalization, control on component rendering. But you should't think about JSS in original meaning. JSS is based on the Layout Service which is awesome tool that allows us to retrieve content from Sitecore and still be able to use all features like tracking, personalization and so on.



        You can still keep the development in the same way you are now, you just need to use an API provided by JSS to get content.



        Please look at the following question and answer for understanding the process:
        Share Sitecore content to Native Mobile Apps (IOS swift and Android java)



        You can read more about Layout Service here: Sitecore Layout Service



        Also feel free to have a look at an application we built for SUGCON 2018:



        Mobile application and JSS



        You can see the mobile app in action: (please start from 24th minute): Sitecore xConnect & Marketing Automation omni-channel demo. Our application is build on Xamarin but it doesn't matter as we send a simple HTTP requests via HTTP client. You can do the same using any platform.



        Sitecore tree structure is represented below.



        Mobile Application JSS - Sitecore Tree



        Where "Home" item represents a main screen of mobile application and displays a list of services. Items under the Home are used as datasources for renderings that are set for the Home:



        Mobile App JSS - Presentation



        Renderings don't have any HTML behind, they are empty, and are used only to set associated content. When we request the Home item in Layout Service, it will return the following output: Home Screen JSON.



        When we click on some service, we will call the API to get content for specific service. The output is here: Service Screen JSON



        Personalization rules are in place too:



        Mobile App JSS - Personalization rules



        Finally, you can build any content structure, any navigation structure, use dictionaries and any other things you want and then Layout Service will provide it for you. I found it as a best tool to implement a headless solutions.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Feb 7 at 10:17

























        answered Feb 7 at 7:49









        Artsem PrashkovichArtsem Prashkovich

        3,0031625




        3,0031625















            Popular posts from this blog

            Biblatex bibliography style without URLs when DOI exists (in Overleaf with Zotero bibliography)

            ComboBox Display Member on multiple fields

            Is it possible to collect Nectar points via Trainline?