04ff8eca4c
I probably created too many similar keyframes |
||
---|---|---|
.github/workflows | ||
compose | ||
design | ||
public | ||
scripts | ||
src | ||
.env | ||
.gitignore | ||
.prettierrc | ||
index.html | ||
package-lock.json | ||
package.json | ||
README.md | ||
vite.config.js |
Phanpy
Minimalistic opinionated Mastodon web client.
This is an alternative web client for Mastodon.
🔗 Production: https://phanpy.social (production
branch)
🔗 Development: https://dev.phanpy.social (main
branch, may break more often)
Everything is designed and engineered for my own use case, following my taste and vision. This is a personal side project for me to learn about Mastodon and experiment with new UI/UX ideas.
🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧
🐘 This is an early ALPHA project. Many features are missing, many bugs are present. Please report issues as detailed as possible. Thanks 🙏
🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧
Features
- 👪 Multiple accounts
- 🪟 Compose window pop-out/in
- 🌗 Light/dark/auto theme
- 🔔 Grouped notifications
Design decisions
- Status actions (reply, boost, favourite, bookmark, etc) are hidden by default.
They only appear in individual status page. This is to reduce clutter and distraction. It may result in lower engagement, but we're not chasing numbers here. - Boost is represented with the rocket icon.
The green double arrow icon (retweet for Twitter) doesn't look right for the term "boost". Green rocket looks weird, so I use purple. - Short usernames (
@username
) are displayed in timelines, instead of the full account username (@username@instance
).
Despite the guideline mentioned that "Decentralization must be transparent to the user", I don't think we should shove it to the face every single time. There are also some screen-reader-related accessibility concerns with the full username, though this web app is unfortunately not accessible yet. - Hash-based URLs.
This web app is not meant to be a full-fledged replacement to Mastodon's existing front-end. There's no SEO, database, serverless or any long-running servers. I could be wrong one day.
Development
Prerequisites: Node.js 18+
npm install
- Install dependenciesnpm run dev
- Start development servernpm run build
- Build for productionnpm run preview
- Preview the production buildnpm run fetch-instances
- Fetch instances list from instances.social, save it tosrc/data/instances.json
- requires
.env.dev
file withINSTANCES_SOCIAL_SECRET_TOKEN
variable set
- requires
Tech stack
- Vite - Build tool
- Preact - UI library
- Valtio - State management
- masto.js - Mastodon API client
- Iconify - Icon library
- Vanilla CSS - Yes, I'm old school.
Some of these may change in the future. The front-end world is ever-changing.
Mascot
Phanpy is a Ground-type Pokémon.
Maintainers
Backstory
I am one of the earliest users of Twitter. Twitter was launched on 15 July 2006. I joined on December 2006 and my first tweet was posted on 18 December 2006.
I know how early Twitter looks like. It was fun.
Back then, I made a Twitter clone called "Twig" written in Python and Google App Engine. I almost made my own Twitter desktop client written in Appcelerator Titanium. I gave one of my best talks about the Twitter client in a mini-conference. I built this thing called "Twitter Columns", a web app that shows your list of followings, your followings' followings, your followers, your followers' followers and so on. In 2009, I wrote a blog post titled "How I got started with Twitter". I created two themes for DestroyTwitter (a desktop client made with Adobe Air by Jonnie Hallman) and one of them is called "Vimeo". In 2013, I wrote my own tweets backup site with a front-end to view my tweets and a CouchDB backend to store them.
It's been more than 15 years.
And here I am. Building a Mastodon web client.
Alternative clients
License
MIT.