Frequenly Asked Questions
Updates will work like this:
It's not very beginner friendly now, but it will become more so once I have some screencasts using it. I also plan to add a forum, but that may be a ways off.
I'll do what I can to help people out, especially anything that improves the experience in general. I can't promise ongoing support though, since this a one-off purchase product.
It means you can use Phoenix Igniter for one deployed application at a time. You can build unlimited toy projects with it, but publishing a second site will require a second license (or shutting down the first site).
I'll add an unlimited sites license at some point in the future but am still trying to work out pricing that makes sense since the primary consumer of such a license would be a consulting agency.
It will be less than Tailwind UI. Probably on the order of 30-50.
Buttons, pills, forms and alerts.
I don't have any plans for generators. That was something I'd thought about originally but I realized the effort for the value is low compared to just getting one good default built.
For example, many users will probably choose either the OAuth or password-based login and remove the other option. That's a quick process.
I use Amazon SES, but Sendgrid and Mailgun seem to be the most popular options. If there's a lot of interest in the topic, I'll make a screencast tutorial.
It really depends on the customers. A lot of people don't want to be tied into a specific SPA framework and even more have a favorite front-end setup they want to use. Unlike removing an unneeded module, removing LiveView means a full rewrite on the front-end.
If LiveView becomes the more or less "default" way that people build Phoenix apps, Igniter definitely include it. If not, I'll probably err on the side of being front-end agnostic and use something very easy to replace.