Finalizing the features for the first release
Features that make the app usable will be in the version one.
This is my blueprint on the number of features planned for the first version. I have an ambitious vision of building a huge fortress. To start with, I’m going to establish a foundation and focus on functional features that can be packed for the first release of Quillcaster. It’s challenging to organize yourself when you have numerous features that you believe would make this service operational. I firmly believe a foundation for the application that would accommodate all the feature sets is crucial, and the first version is focused more on building those essential scaffolds.
Features List
- Mastodon will be our inaugural network supported by Quillcaster. The main reason is the ease of creating and managing APIs.
- A simple dialog triggered by either pressing the toolbar icon on Chrome or with a hotkey. This enables content posting to social media accounts.
- Signup for Quillcaster through GitHub, Microsoft and Google login. I haven’t thought about email signup yet. But GitHub will be the first choice for signup/login.
- Features for archiving content for later usage.
- Post scheduling - This is one of my favorites. It might require considerable effort on the backend side of the system. Fingers crossed!
- Settings Page - For managing drafts, scheduled posts and logging out of the application.
- And, of course, a page for connecting to Mastodon social network and managing it.
This might appear straightforward but for the first version, I believe it would help to lay a proper foundation. My target for pre-alpha release is before Christmas 2024. It’s really not my hard deadline :)