tastejs / tasteapp Goto Github PK

There's going to be a non-trivial amount of work involved in implementing TasteApp for a given framework once #1 and #2 are resolved and the spec is written.

I suggest that we begin by implementing the app using a single framework end-to-end just to help us refine the spec and evaluate how well it can be used.

Thoughts? Perhaps we could ask a member of the community to help with this or use a service like BountySource to kickstart a first implementation.

We will soon put together the draft list of features TasteApp will implement as part of #1.

The time has come for us decide on what the practical application using these features is going to be :)

Some of the ideas suggested:

• RSS reader
• GitHub API client (maybe GitHub projects or chat app)
• Contact manager
• Simple social network client
• Any other ideas?

My personal current preference would be the RSS reader idea with a dedicated backend. Dedicated means we have no reliance on API limits or services going up, down or away.

I propose to use ost.io as a Taste App. Ost.io uses custom open-source backend (http://api.ost.io).

Main selling points:

• Real-world and fun. Ost.io is already used by popular open-source projects. Users can play with real data.
• Useful besides its main purpose.

Features:

• Custom open-source REST API server with CORS and access tokens (server spec)
• Authentication (registration, login, logout — w/o page reload), session management
• State management / routing
• Demonstrates CRUD
• Uses dedicated back-end for data. Can be switched in 1 line to production mode
• Multiple views, Sub-views
• Precompiled templates
• Animations
• Permissions
• Relationships between objects (user -> topic -> repo etc)
• Mobile support

The spec is here: https://github.com/paulmillr/ostio-apps

• First implementation (Chaplin + Brunch + Backbone): https://github.com/paulmillr/ostio

Post your thoughts on what should be also included in this app like "I think there should be modals since they are commonly used".

Taste.js (final name TBD) is the successor to TodoMVC which hopes to offer a more complex sample application. Features we initially feel it should capture:

• Authentication, session management
• Complex routing
• State management
• Demonstrates CRUD
• Uses either a third party API or a dedicated back-end for data
• Multiple views
• Registration, login, logout
• Precompiled templates
• Sub-views
• Mobile support
• Unit testing

Other factors we could consider:

• Navigation transitions and animations
• Form validation for different views
• Nested components
• Offline caching?

@paulmillr's excellent ost.io app already captures these, but let's discuss what else we want the taste app to demonstrate (whether we go for ost.io, a GitHub client, both or something else). Ost.io initial taste spec is located on google docs.

Discussions around:

• What the final app will be
• Whether we will provide a reference template and so on are separate and can be discussed later.

cc @sindresorhus @trek @passy