4 ms·
Thanks for taking the time! That milestone idea is a really great one actually. It minimizes the risk of conflict or dissatisfaction a lot and I really like it.
by dariuscosden 8y ago
Thanks for taking the time! That milestone idea is a really great one actually. It minimizes the risk of conflict or dissatisfaction a lot and I really like it.
They already have a website and want to completely switch over to something new with a brand new design and all. They already have existing clients and it's all on stripe already, so that's good. I just have to set it up on my end via their API.
I looked at Laravel but it's PHP. I know little of PHP. I mean, I could figure it out but there is a deadline for this project and I feel my time would be better spent working with what I already know (especially since I've built payments/subscriptions through stripe specifically using Flask and I didn't find it too complicated).
I am expecting that the extra time it would take me to learn an entire new framework would be more than the time it would take me to figure out how to do it in Flask.
Thanks for the maintenance fee tip. I also wasn't too sure how to structure that but it will be included in the quote for the first year.
- saluki 8y agoDoing milestones prevents them being unhappy with the app when it's complete and you unhappy because you aren't being paid. Stick with what you know, was just throwing it out there. y, it's important to keep the framework updated, and things running properly. Plus gives you a nice recurring fee. Good luck.