1
0 Comments

API & UI framework characteristics

Being the only technical person among the co-founders, I didn't want to go with no-code or low-code tools as I was doubtful regarding the flexibility of those tools.

I was in a dilemma of choosing server side rendered application or api only backend and single page frontend application.

Finally settled with Api only backend and Single page frontend application architecture. Reason being in case I want to outsource UI, I can easily get a freelancer to work in case of this architecture.

When choosing the framework and language for Backend, I wanted these characteristics to be present:

  • Easy to productionalise
  • Easy to bring different capabilities like sending mail, coomunicating via sockets etc, As I had these requirements when building Inwisely.com
  • Atleast cover the minimal security, like defending sql injections
  • Good community for help and libraries
  • Easily discoverable online documentation
  • Active online community
    I found all this in Ruby on Rails, adding to these, I was proficient in Ruby On Rails. The Mailbox functionality of RoR framework blew my mind.

When choosing the Frontend framework,

  • I wanted this to have component library by itself, so that any wire frames or designs according to the need of the feature, I can design from choosing the component from the set of available components.
  • I wanted the framework to be less complex, and be manageable without getting into the complexity of state management.
  • I personally hated styling and usually spent lot of time to make css changes, so wanted all the components to be ready to use, with just giving some padding space it should look good.
    I found all this in VuetifyJs, and I had on my previous experiences worked on VueJs, so felt comfortable with Vuetify.

I can confidently say after building the product and seeing it productionalised in a matter of 3 months, The decision was not bad!

on October 17, 2023