Relying on the same code base doesn’t have to mean unifying other aspects of the system, though, does it? If it means developers can more easily put out versions of an app for a family of devices – macOS and iOS, say – ideas like Fuchsia and Marzipan make quite a lot of sense.
-
-
Replying to @alstonebridge @bazzacollins
Say I buy a Mac and apps I need, then later buy an iPhone or iPad for mobile use. It’d be great to know that I’m more likely (in a few years) to get the same apps there if devs’ lives have been made easier by not having to double up (roughly speaking) on learning frameworks/APIs.
1 reply 0 retweets 0 likes -
Replying to @alstonebridge
Perhaps. And things are improving, but IMHO apps that are coded for both mobile and desktop are worse than those that are coded for specific platform.
1 reply 0 retweets 0 likes -
Replying to @bazzacollins
That’s very broad. Are you able to go into pros and cons of either approach when it comes to architecture/maintenance? There’s a lot of stuff out there, purely in the context of Apple, on how having to deal with two different frameworks (AppKit and UIKit) is uncomfortable.
1 reply 0 retweets 0 likes -
Replying to @alstonebridge @bazzacollins
Many of the apps I use on both macOS and iOS are great on both, but there’s a lot of expense of the developer building three versions across iPhone, iPad and Mac, and for the really good apps it’s expensive buying versions for multiple devices, too.
1 reply 0 retweets 0 likes -
Replying to @alstonebridge
Lightroom Classic on desktop infinitely better than Lightroom CC coded to span mobile/desktop. Normally find limitations of mobile hamper the desktop version.
1 reply 0 retweets 0 likes -
Replying to @bazzacollins
That’s one example. H about others from devs other than Adobe? I gather it takes shortcuts by using Java for much crossplatform code; there are (or were in consecutive versions I’ve used) signs of its development choices through poor integration with small aspects of macOS.
1 reply 0 retweets 0 likes -
Replying to @alstonebridge @bazzacollins
For every hampered app like that, I can point out some pretty impressive mobile adaptations. Starting with
@OmniGroup’s iPad versions of apps that it has made for many years on the Mac.1 reply 0 retweets 0 likes -
Replying to @alstonebridge @bazzacollins
Heck, even Apple is patchy on getting all versions to a comfortable place. Take Pages; it only just got paragraph style editing on iOS, years after Apple started over with building up Mac and iOS versions to work similarly.
1 reply 0 retweets 0 likes -
Replying to @alstonebridge @bazzacollins
Good and bad examples all around. But I think nobody is in a position to say unifying (aspects of) development is an outright bad thing; there’s a lot of learning to do, and that can fall apart once products are in customers hands.
1 reply 0 retweets 0 likes
I think it normally fails when an existing desktop app is transferred to mobile/cross platform. When apps are developed from ground up, it normally works better.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.