Open addyosmani opened 11 years ago
+1 on RSS reader. Here are some notes on OSS implementations and APIs: https://docs.google.com/document/d/1plq3yROJxSaiu6nOj2H5cwiEn-HbVVrBuHHq6rGrO94/edit?usp=sharing
Very useful list. Thanks @passy!
GitHub API client can give more information about the framework.
i’ll probably ask once again: what’s wrong with forum for GitHub projects based on own API — http://ost.io? just hadn’t seen any direct negative responses to that
It's a completely valid question :) Two things:
API limits: I've been heavily using the GitHub API of late and ran into a number of issues with API rate limiting - have you had this issue at all @paulmillr? . As you probably know when you're unauthenticated your limits are fairly low and authenticated it's more around the 5000 request point. This should be fine if we end up not using multiple widgets per view consuming data but if we do, it can get used up quickly (at least it did in my case).
Relying on at third-party API: It's mostly just me, but I have concerns with using third-party APIs which might be subject to change or disappearing at some point in the future. With GitHub the latter is less likely, but I can imagine an API V4 or V5 requiring a number of changes per implementation on our end which might not be easy to get in place. Imagine trying to do this across 20 or 30 apps.
That said, these reservations are my own and we can of course still consider doing a GitHub projects based app using the API. Just making sure concerns are logged :)
@addyosmani for example, http://ost.io caches everything (avatars, user ids etc) and makes API calls to GitHub API only on initial log in and repo sync. So, this should not be a concern at all when backend does caching.
The important point is that the third-party API will not be really third-party. If the main server will shut down, anyone will be able to get it working again on his server just in hours since it is open-source. We will just need to update DNS.
+1 for any app with a dedicated backend (- the RSS reader would be fine). It should demonstrate authentication and authorization (e.g. creating an account, remove an account, forget my password function...) and shouldn't use a 3rd party API for this. (imo)
I did quite a bit of these type of applications internally to train my developers, and the one that resonate the most are:
1) Task Manager 2) Contact manager
While task manager seems to be a boring choice, it does resonate very well with developers, could run only on local (no server) and with server, and offer enough depth to have any capability we want to have (CRUD, Routing, Nested structure, ...).
Here are the ones that I think would be a more challenging fit:
a) RSS Reader: I think it might be too content/browsing centric, and not enough CRUD capabilities.
b) GitHub API Client (chat): Could be too limited in term of CRUD functionality, and will be hard for people to run on their local. Also, it add a all other level of integration API which might be outside of the scope of what need to be demonstrated.
A lot of my professional experience has related to the automotive industry and I thought it would be cool to create a "Build Your Own" type app. Pretty much everytime I've worked on one, a month later I had wished I'd used {{latest and greatest}} instead.
Ideally it would allow for complete customization of a vehicle: color, trim, accessories, options, viewing angles, etc. You could have the ability to pick between different models, save certain configurations and do side-by-side comparisons for saved configurations. Could even go so far as social integration to share a configuration.
There would be a couple of potential issues:
Hey folks,
It's been a few months since we last revisited TasteApp and I'd love for us to get some momentum going on it again :dancer: In order to get the project off the ground a few things need agreement upon:
Thoughts?
do you think you'll have time in the next few months to help if we go down this path (addressing further features etc)
yes! i’m in. all in.
Yes to all this! It has dragged on way to looooooooooooooooooo...ooong. Maybe we should do an Hangout text or video to set some highlevel AI of what needs doing and go through the ost.io app.
maybe this friday or saturday? (i'm free any time tho)
Video.
On Wednesday, October 30, 2013, Sindre Sorhus wrote:
Yes to all this! It has dragged on way to looooooooooooooooooo...ooong. Maybe we should do an Hangout text or video to set some highlevel AI of what needs doing and go through the ost.io app.
— Reply to this email directly or view it on GitHubhttps://github.com/tastejs/TasteApp/issues/2#issuecomment-27443050 .
Forgot that Hangouts just got support for gifs. I'd prefer gifs.
@addyosmani @passy @addyosmani @passy @addyosmani @passy
Hangout tomorrow would work for me, but Addy is still abroad in some crazy timezone isn't he? On Nov 1, 2013 11:53 PM, "Sindre Sorhus" notifications@github.com wrote:
Forgot that Hangouts just got support for gifs. I'd prefer gifs.
@addyosmani https://github.com/addyosmani @passyhttps://github.com/passy @addyosmani https://github.com/addyosmani @passyhttps://github.com/passy @addyosmani https://github.com/addyosmani @passyhttps://github.com/passy
— Reply to this email directly or view it on GitHubhttps://github.com/tastejs/TasteApp/issues/2#issuecomment-27609678 .
Don't let me be a bottleneck :) I'm currently in an airport in Tokyo. Will be back on land tomorrow. Can do Monday / anytime next week if we need to wait, otherwise will catch-up on notes!
On Saturday, November 2, 2013, Pascal Hartig wrote:
Hangout tomorrow would work for me, but Addy is still abroad in some crazy timezone isn't he? On Nov 1, 2013 11:53 PM, "Sindre Sorhus" <notifications@github.com<javascript:_e({}, 'cvml', 'notifications@github.com');>> wrote:
Forgot that Hangouts just got support for gifs. I'd prefer gifs.
@addyosmani https://github.com/addyosmani @passy< https://github.com/passy> @addyosmani https://github.com/addyosmani @passy< https://github.com/passy> @addyosmani https://github.com/addyosmani @passy< https://github.com/passy>
— Reply to this email directly or view it on GitHub< https://github.com/tastejs/TasteApp/issues/2#issuecomment-27609678> .
— Reply to this email directly or view it on GitHubhttps://github.com/tastejs/TasteApp/issues/2#issuecomment-27610521 .
Addy Osmani Phone: +44 7771 334170
Would be nice to have everyone there. Tuesday 13:37 EDT?
Yes
Works for me. :)
(That's 18:37 UTC if WolframAlpha didn't lie to me.)
I do not want to intrude, but if it is ok with everybody, I would love to join as well.
I have been wanting to sample HTML5/Cloud app for a long time to share my approach, and I have some bandwidth to work on it for the next few months.
I assume it will be over Google Hangout.
Jeremy,
On Sat, Nov 2, 2013 at 8:07 AM, Pascal Hartig notifications@github.comwrote:
Works for me. :)
(That's 18:37 UTC if WolframAlpha didn't lie to me.)
— Reply to this email directly or view it on GitHubhttps://github.com/tastejs/TasteApp/issues/2#issuecomment-27623743 .
Jeremy Chone http://britesnow.com/ (415) 699 9912 Building Enterprise HTML5 Applications
Works for me. Does anyone want to send out an invite? :)
Alright, sent out an invite ;)
Here's the Hangout link if anyone else would like to join: https://plus.google.com/hangouts/_/calendar/c2luZHJlc29yaHVzQGdtYWlsLmNvbQ.eo1gh9shbnv5p8n1b58t2pfrus
If it is okay I'll jump on just to listen.
On Tue, Nov 5, 2013 at 5:41 AM, Sindre Sorhus notifications@github.comwrote:
Alright, sent out an invite ;)
Here's the Hangout link if anyone else would like to join:
— Reply to this email directly or view it on GitHubhttps://github.com/tastejs/TasteApp/issues/2#issuecomment-27766231 .
Sure
Thanks for a productive meeting guys.
Meeting notes: http://oksoclap.com/p/tasteapp
:+1: thanks so much for joining us. Appreciate you taking the notes, @sindresorhus!
Ost.io proposal: https://github.com/tastejs/TasteApp/issues/4
Here is an old but good. MediaExplorer by Holly Schinsky http://devgirl.org/files/MediaExplorer/#/ http://devgirl.org/2013/03/21/fun-with-angularjs/
On Tue, Nov 5, 2013 at 1:19 PM, Paul Miller notifications@github.com wrote:
Ost.io proposal: #4
— Reply to this email directly or view it on GitHub.
It's been a while since our last meeting to discuss the app idea we'd like to move ahead with. The choices we came down to were:
Perhaps we could meet again some time mid January to talk about this again?
Yes definitely.
Sorry all, I have been swamped and while I did some work, nothing worth sending a formal update. However, let me use this opportunity to share the work I have done.
First, a question for Addy, do you think we should just take the angular app? or do something more/different. My current take is to do something a little bit more and different.
Here are the current spec and first wireframe.
1) Core objects and relationships: Project 1-* Task; Task - Label; Project 1-* Team; User - Team
2) Privilege system: The application will show the beginning of a extensible priviledge system. At this point, we will just have privileges at the Team level, and constrain Teams to belong to one and only one project. When a user create a project, he will be automatically assigned to a default team "owner" for this project with all the privileges. Then, the owner can create subsequent teams with some privileges and add users to those teams.
3) Routing: This application will support deep-linking/routing for the following screen: project, all sub-tabs of project, and task of a project, and team of a project. Format will be like
team.
4) Table Sorting: The task table will be sortable (and should have a toggle show close -not shown in the wireframe below-).
5) In place [cell] editing: One of the goal of the application is to show the benefit of an MVC model, and for this, the UI will allow the user to edit mostly anything on the screen and see the effect real time. So, all the table cell (beside the checkbox and ID) will be in place editable, and clicking on the "id" of a task will go to the task screen.
6) Task screen as tabs: Another concept that this application will show is how custom the UI can be, especially in the deep-linking and screen management. For example, when opening a task, it will add another tab on the right of the "Tasks" tab with the task id (and first couple of words). In a later stage, task tabs will be pinable.
Here is the first wireframe screen.
[image: Inline image 2]
Feedback welcome, and looking forward to our next Hangout meeting.
Jeremy,
On Tue, Dec 31, 2013 at 12:33 PM, Addy Osmani notifications@github.comwrote:
It's been a while since our last meeting to discuss the app idea we'd like to move ahead with. The choices we came down to were:
Perhaps we could meet again some time mid January to talk about this again?
— Reply to this email directly or view it on GitHubhttps://github.com/tastejs/TasteApp/issues/2#issuecomment-31410273 .
Jeremy Chone http://britesnow.com/ (415) 699 9912 Building Enterprise HTML5 Applications
Let's meet this / next saturday.
Saturdays are tricky for me. I might be able to do it around 10am next sat.
On Fri, Jan 3, 2014 at 1:32 AM, Paul Miller notifications@github.comwrote:
Let's meet this / next saturday.
— Reply to this email directly or view it on GitHubhttps://github.com/tastejs/TasteApp/issues/2#issuecomment-31512739 .
Jeremy Chone http://britesnow.com/ (415) 699 9912 Building Enterprise HTML5 Applications
Would sometime during mon-fri this week or next work? Saturdays tend to be a little tricky for me too.
On Monday, 6 January 2014 00:51:26, Jeremy Chone notifications@github.com wrote:
Saturdays are tricky for me. I might be able to do it around 10am next sat.
On Fri, Jan 3, 2014 at 1:32 AM, Paul Miller notifications@github.comwrote:
Let's meet this / next saturday.
— Reply to this email directly or view it on GitHub< https://github.com/tastejs/TasteApp/issues/2#issuecomment-31512739> .
Jeremy Chone http://britesnow.com/ (415) 699 9912 Building Enterprise HTML5 Applications
—
Reply to this email directly or view it on GitHubhttps://github.com/tastejs/TasteApp/issues/2#issuecomment-31621116 .
absolutely, no problem
I am thinking of building a mini Trello clone. Have the common-utils ready. Will keep you guys posted on the developments. I intend to cover these features. Currently working on a react-example.
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:
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.