Do’s and Dont’s of Working With Components
Every component in our SDK is represented in the Mobify UI Kit. If you’ve worked with our UI Kit before, you may have noticed that symbols are named to reflect their code counterparts. This is intended to be a guide for the developers who will inherit your designs; by maintaining this naming scheme, they will have a reference of which components you’ve used and therefore which ones they need to include in the build.
Just because we strive to maintain parity with the code doesn’t mean the components can’t be customized. In fact, they should be; the purpose of the UI Kit is not to act as a pre-defined style template for your project.
Customizing the components can be as simple as changing colours and icons — something that will filter through from your established design system — or as complex as rearranging the component’s internal elements or creating alternate views or variants. With the UI Kit, visual customizations can be made with little impact to your development timeline.
Though the default components included in the SDK should work for most situations, there may be occasions that require you to further customize a component to satisfy the needs of the client. In these cases, you may need to include additional elements to the components.
In general, be cautious about the additional costs of developing complex custom components. Before deciding on any custom components, review your designs with your development team to ensure they're feasible, and that they will not threaten your project timelines.