I wanted to explore the idea of a &quot;server-less&quot; app, so I built a tweet scheduler -- like what <a href="https:&#x2F;&#x2F;buffer.com" rel="nofollow">https:&#x2F;&#x2F;buffer.com</a> started their business with -- except I wanted to do it without thinking about a server or managing any processes.<p>It uses Vue.js as the SPA plus AWS Lambda, AWS API Gateway, and AWS DynamoDB for the server-like stuff.  It also uses vue-router and vue-loader, two official Vue.js libraries.<p><a href="https:&#x2F;&#x2F;github.com&#x2F;crcastle&#x2F;serverless-buffer-app-gui" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;crcastle&#x2F;serverless-buffer-app-gui</a><p>I plan to post it to the Vue.js forum <a href="http:&#x2F;&#x2F;forum.vuejs.org" rel="nofollow">http:&#x2F;&#x2F;forum.vuejs.org</a> to ask for feedback on my use of Vue.js -- what I could have implemented more simply.  Waiting until I finish the setup guide before posting it.<p>In general, I&#x27;ve been loving Vue.js.  It&#x27;s really simple and quick to get started, but as you get deeper you find that many subtle design decisions were well thought out.<p>EDIT: This is my first venture in SPA frameworks, having previously been overwhelmed by the learning curve of Angular, Ember, and React.