Newton's soup data structure implementation [1], inside a phone OS, with Pimlico's DateBk from PalmOS [2] taking advantage of that soup data structure. DateBk i

Newton's soup data structure implementation [1], inside a phone OS, with Pimlico's DateBk from PalmOS [2] taking advantage of that soup data structure. DateBk isn't abandoned yet even though PalmOS effectively is. That is, DateBk is still actively sold for an essentially abandoned OS, which gives you an idea of how incredibly effective that app is. DateBk has a linking feature that would be ideal for soups interoperating with other applications on the device, without explicit coordination between different app developers. DateBk is the result of a responsive developer listening to lots of users [3], and the kind of PIM that I've yet to find in modern phone OS's. The massive 130-page user manual [4] covers a UI that is relatively discoverable for new users and highly customizable for expert users. Some teams have tried to reproduce the functionality on iOS, but no one has yet to come even faintly close to the smooth workflow I experienced on it. It seems PIMs in general are still stuck in some innovation black hole; there is still so much left unimplemented. [1] https://en.wikipedia.org/wiki/Soup_(Apple) https://en.wikipedia.org/wiki/Soup_(Apple) [2] http://www.pimlicosoftware.com/datebk6.htm http://www.pimlicosoftware.com/datebk6.htm [3] http://www.pimlicosoftware.com/datebk6details.htm http://www.pimlicosoftware.com/datebk6details.htm [4] https://www.pimlicosoftware.com/datebk6-v61a-manual.zip https://www.pimlicosoftware.com/datebk6-v61a-manual.zip