iOS App redesign?


#22

I’ve moved to Things because the iPad experience was horrible.


#23

I’ve been juggling between tick tick, Todoist, things 3 and OmniFocus and finally settling on things 3. Support for OmniFocus is outstanding but I’m way more productive with a more straightforward app that works fast and seamlessly. I don’t like tapping on a lot of icons to get to places and OmniFocus really needs to show all folders and projects on the main page without needing to create a perspective for them. I see everything I need to see when I load up things and everything just feels so intuitive which makes it such a joy to use. OmniFocus 2 gave me a headache when I tried to use it and 3 is better but still annoying and tedious to use IMO.


#24

I still like my iPad home screen showing perspectives. But I’d like to tap on a perspective in home screen and then the left sidebar switches to show a Projects list or a Tags list. That’s what I’m able to do on my Mac but unable to do it on my iPad.

Hopefully the much discussed UI update for 2019 will remedy this.


#25

I share the frustration on iOS and hope everyone has been mailing the support team. In terms of UI/UX, Things 3 is miles ahead (not so much regarding features). Creating tasks and organising actions in OF3 takes too much time and effort, it hardly earns the term ‘flow’ in workflow.


#26

There’s a rumour that Apple will announce a way for iPad apps to be ported to macOS at WWDC next month. The rumour mill is calling the project Marzipan. Apple supposedly used this last year to get iOS apps like News, Stocks, and Voice Memos to the Mac.

Yesterday I was listening to a podcast and the host said something like “the developers will just have to push a button to generate a macOS version of an iPad app”.

I went into a little bit of a panic thinking what if OmniFocus does this?

I truly hate OmniFocus for iPad. Every time I use it I bump into friction. So many taps to do anything. So hard to see the information I need.

It would be horrible if Omni tried to unify the apps ala iPad. It would actually be amazing if they macOS-ifyed the iPad one though. OmniFocus for mac is a joy. OmniFocus for iPad sucks.


#27

What makes you think they will? There’s obviously hundreds of thousands of lines of code in each version. Throwing that away wouldn’t be an easy decision, and might yield very little in terms of Development benefit.

Plus I trust Omni Group to make good technical decisions; Much of the reason I buy from them.


#28

I don’t think they will.

And I hope they don’t! I was just sharing that the thought crossed my mind when I heard the guys on the podcast say it was “just clicking a button” (who knows if that’s true also) to turn an iPad app into a macOS app. I can see the appeal to developers to unify and develop once. It would be great if it worked the other way around, i.e. easily port the Mac version to iPad.

But yes, I trust Omni will not do that. I love OmniFocus for Mac and I really miss it when I’m on my iPad.


#29

If I had a dollar for every time I’ve heard that down the years, I’d be very well off. Marzipan is real, and has been on the go since last year. It’s work in progress and is. very likely to see significant updates at WWDC next month. It will be a convenient way to ease the development task of porting apps from IOS to Mac OS.

But.

  • It does nothing for the look and feel differences between IOS and Mac apps
  • IOS apps don’t have menus and pull-downs and multiple windows and a whole load of other screen items that are expected on the Mac
  • IOS apps are designed to managed via a touch screen, which. Macs don’t have. You. might be able to emulate elements of the touch experience with a mouse or trackpad, but it’s not the same.
  • Look at any successful app that has both Mac and IOS versions - they’re designs and operational methods are very different
  • The Apple apps that were proved with Marzipan are awful. You can’t even send a News page to Safari.

The Omni guys are smart - they have better things to do with their time than take the version of their app with the least attractive UX and use it to replace the one with the much better UX.


#30

The problem is that we don’t give amnesia a chance – all the subtle processes of selective neural pruning that go on at night are wasted in the morning by the mindlessly obdurate memory of the software.

Perhaps it’s analogous to the problem identified in the Edward Luttwak article on war (https://www.foreignaffairs.com/articles/1999-07-01/give-war-chance) – that imposed ceasefires are very well intentioned, but also have the unintended side-effect of allowing both sides to recover and rearm before the fire has really burned out, and when the cease-fire breaks down, the war is thereby intensified and prolonged.

Similarly, imposed reminders of things that would naturally have been forgotten actually make it much harder to cope with long-run overload.

A radical redesign might well look not unlike a pencil and paper bullet journal, but even that won’t function properly if we’re artificially prevented from forgetting, fail to lose the journal occasionally, or don’t gradually build the muscle-tone required to simply draw a line through a lot of things.

Give forgetfulness a chance – it’s a delicate and sophisticated natural system.


#31

There is no such rumour since Apple has simply announced this feature at last years WWDC where they have explained what it is and which of their own apps are using Marzipan (the ones you mention here).

The only thing that can be seen as a rumour is that this years WWDC will see iOS 13 and macOS 10.15 with this new feature. I must say that this is more an educated guess than a rumour though.

That’s a simplification of what developers need to do. What Apple has pointed out last year is that it is rather easy to create these Marzipan apps. However, that might be different for the developer because they may have to break down their apps (modularise them) which may not be very easy to do (especially those with monolithic apps).

What Marzipan means is rather different from what you think. Marzipan is meant to make things easier for developers. What developers currently have to do is develop a new app for iOS and macOS from the ground up. What Marzipan provides them is that they no longer have to do that when they already have an app on one of the two platforms. You can share certain parts of the app (libraries and such). As Apple has stated, apps for iPhone/iPad have to use a completely different way of interfacing than apps for macOS. This is not going to change. Developers still have to design an interface that works on iOS and one that works on macOS.

It is simply standardising and unifying the foundation of iOS and macOS apps. Currently those are completely different beasts. Car manufacturers have been doing this for some years now (using the same chassis/engine throughout various models of cars) and have stepped it up with electric cars where they are designing an undercarriage where you can put on whatever module you want. By doing so you can skip the development of the undercarriage with each new car you want to design. You only need to focus on the bodywork since the undercarriage is a given. That is exactly what Marzipan is.

This has got nothing to do with it being Marzipan or not. It is simply a matter of not having implemented such functionality. The latter is what is discussed here in this topic thus something like Marzipan is actually offtopic.