Why
WikiTok is currently web-only, but the core interaction pattern feels especially suited to mobile. People are already used to discovering content through vertical, swipeable feeds on phones, and a native app could make WikiTok feel much more natural and engaging.
Proposal
Create a mobile app version of WikiTok for iOS and Android, focused on a smooth scroll/swipe experience.
What this could include
- A native-feeling vertical feed for browsing WikiTok content
- Touch-first gestures, including swipe/scroll navigation
- Fast loading and caching for a smoother mobile experience
- Share support for sending interesting pages/videos/articles to friends
- Optional push notifications or saved/favorites support later
- Responsive layouts for different phone sizes
Possible implementation paths
- React Native / Expo for a shared iOS + Android codebase
- Capacitor or similar wrapper if reusing the existing web app is preferred initially
- Progressive Web App improvements as a first step, then native apps later
Expected impact
A mobile app could significantly improve user engagement because the WikiTok concept maps naturally to how people browse content on phones. This could make discovery feel faster, more addictive, and easier to share.
Why
WikiTok is currently web-only, but the core interaction pattern feels especially suited to mobile. People are already used to discovering content through vertical, swipeable feeds on phones, and a native app could make WikiTok feel much more natural and engaging.
Proposal
Create a mobile app version of WikiTok for iOS and Android, focused on a smooth scroll/swipe experience.
What this could include
Possible implementation paths
Expected impact
A mobile app could significantly improve user engagement because the WikiTok concept maps naturally to how people browse content on phones. This could make discovery feel faster, more addictive, and easier to share.