Folks, Can I respectfully suggest Once we have the software platform and the distribution mechanisms in place all that remains is imagination. I have dozens, if not hundreds of ideas for apps and solutions.
Quinoid and Tiddloid are great "wrappers" of tiddlywiki, but they list one or more wikis and they need a wiki installed. This is perfect for TiddlyWiki enthusiasts. It is not what we want for application deployment everytime. Mobiles apps often fit a defined need, this need should be reflected in the name/icon so it is simple to click when needed. A way to package a single wiki (Progressive Wed app is one way), users do not need to know the back story, they need to know what it does, but this will be acknowledged in the apps. I think the current lack of applicability of mobile apps to desktop apps and visa versa is not due to a lack of user need but a lack of imagination or capabilities of the app developers. who would not like to capture ideas for their book on their phone then write a chapter on their desktop or tablet? If you design a good app, and sell it for a few dollars, if that is popular you can start a business. For get the swamp, make a mangrove tree. It is also the period in time where businesses not only need a website but need an app or they do not exist in many peoples mind. Similarly people "understand" apps now they are learning what to ask for in an app, and even bespoke needs can be catered for. Far too often an app solution is hidden in indecipherable code so if you commission one you have to return to the original developer or get a new one, TiddlyWiki allows them not to trust the developer, because they can resort to open source code fixes, curiously they trust developers more who offer them this flexibility. If you do not know what is behind the PWA or Progressive Web App I urge you to find out. It is possibly the most important recent trend and defines what people will expect. If you ask me TiddlyWiki was born to succeed in this. *Progressive web applications (PWAs) <https://en.wikipedia.org/wiki/Progressive_web_applications> are a type of mobile app <https://en.wikipedia.org/wiki/Mobile_app> delivered through the web, built using common web technologies including HTML <https://en.wikipedia.org/wiki/HTML>, CSS <https://en.wikipedia.org/wiki/Cascading_Style_Sheets> and JavaScript <https://en.wikipedia.org/wiki/JavaScript>. They are intended to work on any platform that uses a standards-compliant browser. Functionality includes working offline, push notifications <https://en.wikipedia.org/wiki/Push_technology>, and device hardware access, enabling creating user experiences similar to native applications on mobile devices. Since they are a type of webpage <https://en.wikipedia.org/wiki/Webpage> or website <https://en.wikipedia.org/wiki/Website> known as a web application <https://en.wikipedia.org/wiki/Web_applications>, there is no requirement for developers or users to install the web apps via digital distribution systems like Apple App Store <https://en.wikipedia.org/wiki/App_Store_(iOS)> or Google Play <https://en.wikipedia.org/wiki/Google_Play>.* *While web applications have been available for mobile devices for as long as mobile devices have existed, they had generally lagged behind native apps in terms of speed, features, and user adoption, especially on mobile devices. Direct access to hardware and the ability to work offline, previously only available to native apps, allows PWAs to perform much faster and to provide more features in line with native apps.* *PWAs do not require separate bundling or distribution. Publication of a progressive web app is as it would be for any other web page. PWAs work in any browser, but "app-like" features such as being independent of connectivity, install to home screen and push messaging depend on browser support. As of April 2018, those features are supported to varying degrees by the Microsoft Edge <https://en.wikipedia.org/wiki/Microsoft_Edge>, Google Chrome <https://en.wikipedia.org/wiki/Google_Chrome>, Mozilla Firefox <https://en.wikipedia.org/wiki/Firefox> and Apple Safari <https://en.wikipedia.org/wiki/Safari_(web_browser)> browsers, but more browsers may support the features needed in the future.[1] <https://en.wikipedia.org/wiki/Progressive_web_applications#cite_note-CanIUsePWA-1>[2] <https://en.wikipedia.org/wiki/Progressive_web_applications#cite_note-IsServiceWorkerReady-2>* Regards Tony On Saturday, July 6, 2019 at 5:19:44 AM UTC+10, @TiddlyTweeter wrote: > > Mark S. wrote: > >> ... I can imagine a wrapper kit for Android that would allow any >> mobile-themed TW to be turned into an application. >> The problem is, there are just so many apps already. >> > > I got to thinking about "Quinoid". Its an example of "enabling software." > A wrapper for TW that can give added functions and could potentially be > expanded > > Its, I think, a good example of where the money may be. > > FWIW, amongst the most profitable businesses in the mobile phone sector > are the companies who manufacture the boxes for phones. > > I'm NOT suggesting Quidoid is that, But its an example of you "need a > wrapper" for best presentation. You need Quidoid + the App(s). That's a > product. > > Thoughts > Josiah > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/dfce94bf-dd1a-44a7-b26c-7ed397cbf655%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
