Roadmap
Suggest a feature or stay on top of what we are working on.
2FA Two-Factor Authentication
Similar to the one implemented in Jetstream, ideally with other options like code by mail or sms.
Sign in with magic links
Allow users to be able to sign in with magic links instead of username/password.
Currency Switcher
Add currency switcher to the checkout page and pricing component to provide ability to display prices in different currencies.
User Wallet
Wallet System module allows the customers to make the purchase products from their Wallet. The customers can select the Wallet System payment method for the admin and seller’s products at the time of the checkout process.
Trial without credit card
Include the feature of offering a trial period without the customer needing to enter a credit card.
List plans on subscription page
If users don't have a subscription, subscription page is empty. I think we list available plans on subscription page if there is no active subscription.
Allow comments on feature requests
Allow other clients to comment on feature requests to provide their input/take on things.
When the user was last-seen in the app?
I think it would be useful (in particular for SaaS application) to collect when the user was logged-in within the app the last time; This could be used, for instance, if we want to track user activity/inactivity, e.g., whether we should send daily/weekly reports, reminder emails, etc. Just went through one of the possible implementations that could be done in Laravel as a reference: https://medium.com/@grmcameron/implementing-last-visited-last-seen-in-laravel-237dbbed9027 Thanks!
Add FAQs as a resource
Add FAQs as a backend resource to be able to add questions/answers from the backend.
Product Tour in Client Panel
Ability to guide the user through their onboarding process
Component to show purchase history
Add the purchase history component that's already showing on SaaSykit's website to SaaSykit to allow users to show latest purchases from their customers.
Offline Documentation
In SaaS projects, continuity is important. Today, you provide your support, but in case you or your site become unreachable in the future, having an offline version of the documentation would be beneficial. Sharing the existing documentation through a GitHub repository would not create additional workload for you. You can update the repository and publish the updated repository on your site.
Proper Terms&Conditions Versioning and Change Management
Since software development is iterative, so are changes to the Terms and Conditions. Currently, this page is static, but in many countries changes to the Terms and Conditions must not only be properly communicated (e.g., by email or in-app notification), but each such change must also be accepted by the user (e.g., by checkbox). Currently, there is no such possibility of properly managing and versioning the ToC, which is needed from the legal point. This should work as a simple CMS, with content, version number (optionally), effective date and email template (an email with the changes should be sent to users every time we change ToC). From the DB point of view, we should track which user accepted which version of the ToCs. Optionally, we should be able to block access to the app if accepting a certain version of ToCs is crucial to using the app.
Show email verified status on user dashboard
After registration there is no information on user dashboard for email verification (also admin dashboard). I think there should be a notification on user dashboard for unverified users and users could request new verification email. Also, system don't send new email verification link when users changed their email.
Support for the VILT (Vue.js, Inertia, Laravel, Tailwind) stack
Please add support for (or migrate to) the VILT (Vue.js, Inertia, Laravel, Tailwind) stack. VILT is more popular than TALL, and comes with many benefits: - the UX is faster to load because of Vue.js, and with Inertia, the front-end and back-end is all in one codebase - Laracasts, Codecourse, etc all use or promote VILT
Add possibility to have a slug for tenant
To be able to have acme.my-domain.app or my-domain.app/acme
Blog has some extra features
We suggest creating some extra features like this blog filament plugin: https://filamentphp.com/plugins/firefly-blog#features It will be very helpful to everyone.
Delete account
User should be able to delete their account, maybe provide a feedback for leaving. The terms and privacy policy can mention that the user can delete all their data whenever they feel to do so as per compliance.
Support setting setup fee for subscription from admin panel
Support setting setup fee for subscription from admin panel
Add extra option to invoice settings for formatting Date
You have some options under the invoice settings like company name, coc number and address and more. Would be helpful to make the the date format dynamic. Would be the same as SETTINGS -> Format date option. This way its more consistent with the rest of the settings.
Add profile picture for users
Add ability for user to upload profile picture and display in the blog post when user posts a blog
Ploi.io (tool like forge) documentation
It would be nice to have some basic instructions about ploi.io deployment also
Who and when created/updated te roadmap item?
It would be cool to know which user created a roadmap item, and when did that. In general, it would be useful to see some columns like created by / created_at/updated_at. At the list of all roadmap items or in a specific one, doesn't really matter I think.
Component to display few words about a person
Like the component displayed on SaaSykit.com showing photo and a few words about founder of SaaSykit.