Cross-platform
app development
in Chicago

Cross-platform frameworks rely on plugins for anything close to the device. Camera, maps, payments, biometric login and push notifications usually come from packages written by someone else. These packages save time at the start and often cause the trouble later.

Each plugin is a dependency on another team. Some are maintained by large companies, others by one volunteer. Before adding a plugin, we check who maintains it, how recently it was updated and how quickly issues are answered.

Both platforms must be covered properly. A plugin may work well on one operating system and poorly on the other. Testing on real devices for each platform, early, shows the gaps before the feature is designed around them.

The number of plugins should stay small. Every extra package increases build time, app size and the chance of a conflict between versions. If a feature needs only a few lines of native code, writing it ourselves can be simpler than adding a package.

Wrapping plugins helps. The app talks to its own small interface, and the plugin sits behind it. If a plugin is abandoned, only the wrapper changes, and the rest of the code does not notice.

Operating system updates break plugins. Each year, new versions of iOS and Android change permissions, background rules or required SDK versions. Plugins that are not updated in time can block a release. We track the plugin list against the platform release calendar.

Licences need checking. Most plugins use permissive licences, but some carry conditions that matter for a commercial app. A short record of each package and its licence avoids surprises during due diligence.

Security reviews apply to plugins as well. A payment or login package handles sensitive data, and its code deserves the same attention as your own.

A plugin inventory is part of the handover. It lists each package, its purpose, its version and the person responsible for keeping it current. Without it, the next team inherits a puzzle.