Recently, we encountered a problem where we used the out-of-the-box React-SDK to display a customized portal based on the recommendations. However, we believed that the SDK could also help us render the same application on mobile as well, but surprisingly, it did not align properly.
We want to understand this difference on why the given react-sdk kit fails to achieve web responsiveness on mobile to benefit an omnichannel experience, and is there a need to have a mobile version SDK to support mobile-based & another one for web-based!
Hi Kondal,
thank you for your question.
Let’s first handle the difference between SDKs.
React SDK is for web applications that run in a browser (on desktop and mobile).The same is with Angular SDK.
On the other hand the Mobile SDKs from Pega help develop mobile apps. For example if there was an existing Swift UI or JetPack Compose mobile app a new case creation forms could be embedded into that app. It if was a mobile service provider the business process of new eSIM request could be handled through Pega by creating a case from the app.
Answering your question, we would need more information if you want a desktop responsive application that behaves well on small scree (in browser) or mobile native app.
Here is a generic answer. SDK is set of functions and tools to help with implementation of custom design systems. The work to implement custom components is on implementing team. The portal (app) stays responsive and works well on mobile too as long as the provided custom components are responsive and only based on W3C APIs available across the browsers and devices. Regardless of the solution chosen it is up to implementer to implement custom components in a way they are responsive across various screen sizes.
We have developed a React SDK by overriding Material-UI with Tailwind CSS. However, in the mobile view, the alignment is not rendering correctly, as shown in the attached screenshot. We ae facing the same alignment issue in the out-of-the-box React SDK.
Hi Ganseh:
Thank you for the feedback I will pass it to the product team. However, it is important to differentiate between the starter pack and SDK.
Mediaco was created as a sample app and not claimed to be fully responsive per se. As the design system is controlled be the client/partner using SDK it could be configured to be responsive or accessible as per their need.
In other words, MediaCo is a sample, very basic application. It is up to client/partner to implement responsive components.
Please take a look around 26 second of the video to see the responsive behaviour. Source code for this project is open-sourced: GitHub - kamiljaneczek/Sweet-Life-Pega
