The current Twitter example of Offline Capabilities , although useful, doesn't really offer enough depth to really get into whats required to build full offline capable apps. There are also a fair few community posts about how to acheive this e.g. here and here, and they all help conceptually get your head around what is required for offline capabilities (i.e. needing aspects for creating, editing, deleting, error handling and mutliple changes), none actually offer steps/a process to go about this.
In the Offline Mode idea here, @Darshan mentions that there is going to be a Phase 2 implementation that will (hopefully) expand the abilities and introduce them more as standard, but until that is able to be implemented, then more indepth examples would be greatly appreciated.
Its not so much the type of app that matters in the example, its more that it shows and explains how to handle all the different aspects needed to deal with all the nuances of offline capabilties (and explains why its all needed). Pretty much until PowerApps can deal with CRUD by default, examples could help make your already stellar product (the potential it has is insane), killer.