Suggest a feature or stay on top of what we are working on.
All sites owned by EU citizens or targeted towards EU citizens must comply with a crazy EU law. This law requires a dialog to be displayed to inform the users when you are using tracking cookies. You can read more info on the legislation on the site of the European Commission. Be aware using cookies for a site/web app that is not used for tracking (for example: session cookies) do not fall under this obligation.
Seat/Quantity based billing with the ability for clients to upgrade/downgrade the seat/quantity on a set plan.
Allow users to be able to sign in with magic links instead of username/password.
Similar to the one implemented in Jetstream, ideally with other options like code by mail or sms.
Add support for usage-based subscriptions (metered subscriptions)
Allow customers to invite users to their dashboard for collaboration and set custom user permissions.
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.
Add currency switcher to the checkout page and pricing component to provide ability to display prices in different currencies.
Split the sidebar to show same links or another info
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.
Seamless integration Tenancy for Laravel to be able to setup & onboard multiple tenants with ease.
Allow other clients to comment on feature requests to provide their input/take on things.
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.
Like the component displayed on SaaSykit.com showing photo and a few words about founder of SaaSykit.
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.
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.
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.
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 setting setup fee for subscription from admin panel
The ability to invite a user to be part of a team of other users for a particular purchased product. readonly for the viewer and read/write for the own that purchased the product
Add FAQs as a backend resource to be able to add questions/answers from the backend.
It would be nice to have some basic instructions about ploi.io deployment also
Ability to guide the user through their onboarding process
Provide teams support with per seat subscriptions billing. A user could be invited to be a team member and should confirm invitation via email.
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.