Over time, we learned the importance of communicating problems and pushing important issues via bug reports, developer technical support, or WWDC labs. If it doesn’t or there’s a bug – we need our own solution or a workaround. When we started our development of Pixelmator Classic in 2007, we took all Apple frameworks at face value. Along the way, was there anything that took you by surprise - any pros / cons, any insights that you hadn’t been aware of when you started? The month or two before major OS releases is probably too late to report issues that affect your product only. And it’s important for us to report those bugs as soon as we see them, otherwise there’s a possibility that they might slip into the final product. It’s pretty usual for our small team to file tens of bug reports just for regressions. We have to start a very intensive QA cycle with early macOS / iOS betas to spot any regressions that could affect our products. This decision limits our market, but it’s a decision that we made early on when founding the company with the purpose of developing native products, and we’re really happy with the current growth of the platform and continued investment by Apple into the graphics ecosystem.įrom a development perspective, one challenge is that we have to plan our development schedule around the release cycle of major OS updates. The major limitation of choosing native technologies is that we limit ourselves to the Apple ecosystem. Did you encounter any problems or disadvantages connected to those technologies? And by the way, while migrating to Swift, we were forced to migrate to ARC memory management too, which solved a lot of the memory management issues in our legacy non-ARC Objective-C codebase. Optionals are also amazing, making the UI logic of our app much more consistent and avoiding issues that were common in our Objective-C codebase. What’s more, crashes that were common with Objective-C are non-existent in Swift. Pixelmator Classic was created using Objective-C and, comparing that to our Swift-based Pixelmator Pro, we can see that our pace of development is way faster. We depend on pretty much every available framework on the macOS platform. If we need excellent GPU-based gaussian blur – it’s easy thanks to Core Image. If we need optimized, power-efficient, and precise color management – we can use the Accelerate framework. We depend on Apple frameworks to provide solutions to really tough problems in graphics processing, too. It’s so much easier to build a consumer product using relevant and accessible UI frameworks on Apple platforms.
PIXLEMATOR BLUR PRO PRO
The biggest thing is that apps like Pixelmator Pro simply would not be possible without a lot of the foundational technologies provided by Apple frameworks.
Tell us about the good parts: what’s great about those technologies? For developers who focus on being 100 % platform-native, choosing native technologies is pretty much a no-brainer. Why did you choose those particular technologies?īeing platform-native is key for us at the Pixelmator Team – our identity and products are built on bringing the best native experience and it’s something that we invest a lot in. Our main programming language is Swift - we were early adopters of Swift back with version 1.0 and, even though we’ve experienced all the growing pains of transitioning through major versions of it, we learned a lot and we got to work with and meet the amazing Swift team at Apple. For Pixelmator Pro on macOS, we use a ton of Apple frameworks, everything from basics like AppKit, to performance-oriented, hardware-accelerated frameworks like Metal, Core ML, Core Image, and Accelerate. What technologies are you using to develop it?Īll our apps are created using native technologies. All of our apps are designed to make powerful image and photo editing tools accessible to everyone. We also have a photo editing app called Pixelmator Photo, which is currently available on iPad, and Pixelmator for iOS, a layer-based image editor for iPad and iPhone.
PIXLEMATOR BLUR PRO MAC
That app is still available from the Mac App Store, though it has been superseded by the newer Pixelmator Pro, which was released in 2017. The first app we created was Pixelmator, which is a fully Mac-native layer-based image editor released in 2007. Tell us a little bit about your app: what does it do and when did you start working on it?
0 kommentar(er)
