Posts

Highlight unintended dependencies between your modules, groups, files or entities with Warnings, so that you can find and fix them easily.

Splitting an app into modules is an essential technique for managing software complexity. Modules allow us developers to focus on smaller parts of the app at a time by hiding away complexity. Although they hide information, a module need to expose some of the code it contains, otherwise other modules couldn’t interact with it. There’s …

Understand your Project with metrics: Module Deepness Read More »

How does Swiftalyzer know which entities belong to which of Apples frameworks? In this article we’ll show you where this information is coming from and how you can get this data yourself.

This metric shows how many of your code entities depend on frameworks. The more of your entities use a framework, the higher is the dependency to that framework. A high dependency is not always bad, but it can increase the maintenance costs and your vulnerability in case of breaking changes in a framework.

Sw!ftalyzer shows you an overview of the lengths of all files in a histogram. This gives you more context than looking at each file individually and helps to spot outliers. Learn more about how Sw!ftalyzer helps you improving your app.

When removing an old and unused feature or refactoring code, it’s easy to miss that some part of the code stays in the project although it’s no longer in usage. Swiftalyzer analyses all dependencies and can find entities without any incoming dependencies.

Sharing code via Target Memberships is easy but has a bunch of disadvantages. Learn more about the problems and how Swiftalyzer helps you identify shared files.

Swiftalyzer automatically analyses the declarations of the classes in your app and knows, which ones don’t have the final keyword. It also sees all inheritances and thus knows, which classes can not be final because of subclasses. Learn more about how to improve your app with Swiftalyzer.

The architecture of a software project is often large and complex. This makes it hard to see if a change in the source code reduces or adds more complexity, making the software harder to maintain in the future. Find out how to measure this complexity with SwiftAlyzer.