Need some pointers on comparing spiffy UI with others out there

[Kris...@yahoo.com]

Came across Spiffy UI framework in our search for a light-weight (easy to learn) web UI mechanism.

But then also found few others such as metawidget, swagger etc. and being new to this field got completely lost on which tools is the right one.

Writing this to this forum in the hope that the experts here would help us identify the pros and cons of Spiffy UI against few others we found.

For example, how does Spiffy UI compare against meta-widget? and especially against swagger?

The comparision criteria for us is: 

1. Easy to get started for a newbie

2. Should have solid foundation (no. of projects using it) and should be future-ready

3. Commercial friendly license

For example, how easy it is to create a simple web-site that has a login-page and file-upload feature where users can either upload new file or see the list of files they uploaded till now.

Any one experience in Spiffy UI and these  other frameworks - please share your views, and help us pick the right tool.

Thank you

[Jon Bultmeyer]

At a high level we created SpiffyUI to be an opinion of curated choices of client side tech to go with a general strategy of using GWT on the client and REST/JSON and more recently REST/JSON/OAuth exclusively on the server.  This was about building single page ajax apps efficiently and maintainable at a point in time when we highered GWT to do the job of managing multiple browser incompatibilities.  The macro point was that the server tech could vary independently of the client tech, and there could be multiple clients of various stripes from curl or wget to flash or native mobile to html5/js etc.  Before there was grunt and yeoman and the like you needed a way to house the lint checking and other build steps in a build, so Spiffy encompassed that as well.  We wanted to create something that was harvested from real production code going to global 1000 type customers in commercial products and share the recipe to get outside contributors and bootstrap other developers across our own company. 

Fast forward a number of years and the framework has been very useful to us internally and is used in many commercial products we ship.  In addition this clear delineation of request/response boundary and REST/JSON ajax has served us well in that the GUI we ship has no advantage over a custom built client GUI to the REST api or an automation script.

Since it was created the web side of things has changed probably more rapidly than anyone could have imagined as well as the whole mobile/tablet native/hybrid/html5 landscape both from the browser capabilities and standardization as well as the tooling like chrome dev tools and the various automation frameworks and newer MVC in the glass technologies like AngularJS and Dart Angular ( or pick your other favorite stack).  Most importantly the frontier has changed from incompatibilities that GWT helped us address at scale to new HTML5 capabilities like web components, shadow dom etc ( the things Polymer is addressing ).

We can't recommend you pick SpiffyUI vs. something else, but as to your criteria we think there is a lot of value in the fast time to a full featured single page ajax web stack, using GWT productively and in a REST/JSON/OAuth API client style.  It's proven in commercial products and has a commercial friendly licensing.

Hope this helps,

Jon

--
You received this message because you are subscribed to the Google Groups "Spiffy UI" group.
To unsubscribe from this group and stop receiving emails from it, send an email to spiffy-ui+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.