Since we have undertaken to consider not only individual functions, but also invade the architecture of the application, I want to draw the attention of developers to two aspects of a special kind of architecture.
And I will explain the first one by the example of the manufacturer of audio equipment, the company RME. Imagine that LF is a functional part of an iPad as sound card RME BabyFace, designed for professional mobile-marching sound recording. The architecture of this sound card is made in such a way that in the copy purchased by the user (I note that the device itself can not be physically changed from the moment of manufacture), then a PRINCIPLE NEW FUNCTIONS are added with subsequent firmware changes, which were not present when the device was sold!
In most other hardware manufacturers, such improvements are possible only with the release of NEW hardware, but a firmware update only eliminate the detected bugs and improve compatibility with other equipment.
In this example, the developer has the ability to "deliver" to the consumer functions for which the buyer of other manufacturers need to buy another device.
This is to the aspect of frequent updates of iOS for a certain group of different models, and at the last conference Apple focused on the extension of iOS functions for tablets
. Apple opens up more and more features for application interaction. The most striking example in this direction is AudioBus. Do not miss this aspect.
Why not add the ability to get an audio track through the IAA or as an AudioBus3 output point in the project from Cubasis, Auria, etc. directly?
I wish you one of the priorities to look "from the top of the mountain to the entire changing valley".
The second aspect concerns directly the request. The application already has a large set of various effects and transitions. But the aesthetics
of a particular project often requires a one-time transition, which is not always needed and the repository simply clutters up
. Androu already helped with such an example on the forum
Consider allowing users to create their own transitions and effects
. This can be a separate additional application, placing the result in LF, or (as preferable
) a separate sub-system within the application
, using visual sources prepared in other applications (such as Affinity Photo).
And there is still a lack of an option to "unload" the interface by removing unused transitions and effects
. After all, you can always reinstall the application to get them back with a rare need (or just enter the recovery point of the "factory state" in the settings).
Thank you for attention.