The third and final blog on the series.
After analysing the pros and cons of WordPress Vs DIY, it was only logical to try out the DIY approach; so I tried.
Now I have a fully functional application developed from the scratch. Only razorpay has to be attached to go live .
Here’s a short video clip showing how membership is renewed and policy is bought. The clip is under three minutes including explanations.
Video Link for mobile phone users
Not a single word needs to be typed. The database is fully populated including the details of all beneficiaries. As a member logs in all his particulars are displayed.
Should take just about a minute or two even on a slow internet connection. I feel that’s how it should be.
200-500 users should be able to login and transact in a day.
Of course , there will be always more and more customization and features required. That’s the best part of a DIY approach. Once you have the framework ready , it is easy to customise it to your requirement , as every line of code is your own!
Read all three blogs Murali. Given the SSS experience and your intervention that saved the day provided a rich context to understanding. Liked the part of the balance sheet where the observation was on the “right alignment”. A clear case where major SD was overlooked for a minor SD!
The video example given for policy renewal – was it recorded on YouTube?
Ash, firstly , thanks for reading.
Was just highlighting that
Front end is more visible than the backend , in every field whether a hotel or a web site…all the lipstick is seen in the front end and grime and sweat in the backend.
Anyway that’s the rule, which neither of us have made. Have to live with it.
Coming to the video, it’s a live demo of policy purchase online ; my desktop is recorded using a script I wrote 🙂
It was later uploaded to you tube as you tube optimises it for better viewing on the web.
Otherwise , it doesn’t play on some mobile phones.
So much to learn .
Cheers