WhereYouAre - Revision history

M at 20:13, 3 March 2010

2010-03-03T20:13:50Z

← Older revision		Revision as of 20:13, 3 March 2010
Line 18:		Line 18:
	== Implementation ==		== Implementation ==

	[http://thedigitalmachine.com/services/recess_git/whereyouare ~~REST~~ API]		[http://thedigitalmachine.com/services/recess_git/whereyouare Current live RESTful API]

	map features:		map features:
			get updated locations
	touch user to open details		touch user to open details
	arrow features:		arrow features:
			get updated locations
	touch user to open details		touch user to open details
	contacts features:		contacts features:
			add friend
			remove friend
			import friends?
	open details...		open details...
	show pic, phone, ip, last timestamp		show pic, phone, ip, last timestamp
Line 46:		Line 51:


	~~Use cases~~		wya PHASE 1 NOTES
	-------------		-----------------
	~~1 user starts app~~
	~~User gets updated friend locations~~
	~~User closes app~~
	~~2 user goes offline (in app, prevents notifications)~~
	~~3 user goes stealthmode~~
	~~4 user changes friends priority (make this easy to do!)~~
	~~5 user changes # tracked friends~~
	~~6 user sets friend to ignore on/off~~
	~~7 user sets friend to meetup on/off~~
	~~8 user sets friend to stealth on/off~~
	~~9 user pings friend~~
	~~10 user adds friend~~
	~~11 user deletes friend~~
	~~12 import friends?~~


	wya API requirements		wya API requirements
	------------------------------------------		------------------------------------------
			https - put - wya/user/123-456-7890/password (need to verify against new app "orders"?! for now, allow new#'s to register?!)
			https w basic auth - put - wya/user/123-456-7890/password (only to change existing users' pwd)
			https w basic auth - put - wya/user/123-456-7890/location
			https w basic auth - put - wya/user/123-456-7890/subscription
			https w basic auth - get - wya/user/123-456-7890/subscription/location_and_age_array


			wya PHASE 2 NOTES
			-----------------
	https put "my friends subscription" (on startup)		https put "my friends subscription" (on startup)
	https put "my location" every 15 seconds (may be "stealthmode") \		https put "my location" every 15 seconds (may be "stealthmode") \

M at 23:17, 24 February 2010

2010-02-24T23:17:28Z

Show changes

M at 22:26, 24 February 2010

2010-02-24T22:26:52Z

← Older revision		Revision as of 22:26, 24 February 2010
Line 18:		Line 18:
	== Implementation ==		== Implementation ==

	[http://thedigitalmachine.com/services/recess_git/~~WhereYouAre~~ REST API]		[http://thedigitalmachine.com/services/recess_git/whereyouare REST API]

	(round4)		(round4)

M at 22:25, 24 February 2010

2010-02-24T22:25:37Z

← Older revision		Revision as of 22:25, 24 February 2010
Line 17:		Line 17:

	== Implementation ==		== Implementation ==

			[http://thedigitalmachine.com/services/recess_git/WhereYouAre REST API]

	(round4)		(round4)

M at 15:05, 24 February 2010

2010-02-24T15:05:45Z

← Older revision		Revision as of 15:05, 24 February 2010
Line 156:		Line 156:

	== REST Examples ==		== REST Examples ==
	#The best example I have to follow is the [http://apiwiki.twitter.com/Twitter-API-Documentation Twitter API]. It obviously scales. It uses Basic Authentication, which sucks (everything is plaintext, holy shit). BETTER force it to use SSL.		#The best example I have to follow is the [http://apiwiki.twitter.com/Twitter-API-Documentation Twitter API]. It obviously scales. It uses Basic Authentication, which sucks (everything is plaintext, holy shit). BETTER force it to use SSL. They are moving towards a more-robust authentication based on OAuth.
	#The other excellent example is the [http://docs.amazonwebservices.com/AmazonS3/latest/index.html?RESTAuthentication.html Amazon S3 API]. Authentication is brilliant - it uses a SHA1 signature of the request, which MUST include a timestamp within the last 15 minutes. There is a set of rules for turning the request URL into the request string that is signed.		#The other excellent example is the [http://docs.amazonwebservices.com/AmazonS3/latest/index.html?RESTAuthentication.html Amazon S3 API]. Authentication is brilliant - it uses a SHA1 signature of the request, which MUST include a timestamp within the last 15 minutes. There is a set of rules for turning the request URL into the request string that is signed.
	Signature = Base64( HMAC-SHA1( UTF-8-Encoding-Of( YourSecretAccessKeyID, StringToSign ) ) );		Signature = Base64( HMAC-SHA1( UTF-8-Encoding-Of( YourSecretAccessKeyID, StringToSign ) ) );

M at 14:57, 24 February 2010

2010-02-24T14:57:07Z

← Older revision		Revision as of 14:57, 24 February 2010
Line 7:		Line 7:
	* Free and easy to configure		* Free and easy to configure
	* Quickly start to track existing friends		* Quickly start to track existing friends
			* Provide tracking for all, one, and groups of friends
	* Make fast privacy and priority adjustments		* Make fast privacy and priority adjustments
	* Obtain best-in-class location information		* Obtain best-in-class location information

M at 02:02, 21 February 2010

2010-02-21T02:02:59Z

← Older revision		Revision as of 02:02, 21 February 2010
Line 2:		Line 2:

	== Analysis ==		== Analysis ==
	It would be ~~nice~~, and should be easy, to provide an app that shows where your friends are. Many of these apps already exist, but they all break down when it comes to reaching critical mass: it's just too much trouble to get all your friends registered and receive their locations when you need them~~, as everyone~~ is not going to run the app at the same time. Can we solve this problem well enough to make an app worth having?		It would be useful, and should be easy, to provide an app that shows where your friends are. Many of these apps already exist, but they all break down when it comes to reaching critical mass: it's just too much trouble to get all your friends registered and receive their locations when you need them. Everyone is not going to run the app at the same time, which just leaves push communication to the phone. Can we solve this problem well enough to make an app worth having?

	== Requirements ==		== Requirements ==

M at 01:52, 21 February 2010

2010-02-21T01:52:31Z

← Older revision		Revision as of 01:52, 21 February 2010
Line 11:		Line 11:

	== Design ==		== Design ==
	Map view for traditional location display		* Map view for traditional location display
	Arrow view for sexy fun location display		* Arrow view for sexy fun location display
	Contacts view for fast privacy/prioritization changes		* Contacts view for fast privacy/prioritization changes

	== Implementation ==		== Implementation ==

M at 01:48, 21 February 2010

2010-02-21T01:48:23Z

← Older revision		Revision as of 01:48, 21 February 2010
Line 2:		Line 2:

	== Analysis ==		== Analysis ==
	It would be nice, and should be easy, to provide an app that shows where your friends are. Many of these apps ~~exit~~, but they all break down when it comes to reaching critical mass - it's just too much trouble to get all your friends registered and receive their locations when you need them~~. Everyone~~ is not going to run the app at the same time. Can we solve this problem well enough to make an app worth having?		It would be nice, and should be easy, to provide an app that shows where your friends are. Many of these apps already exist, but they all break down when it comes to reaching critical mass: it's just too much trouble to get all your friends registered and receive their locations when you need them, as everyone is not going to run the app at the same time. Can we solve this problem well enough to make an app worth having?

	== Requirements ==		== Requirements ==
Line 11:		Line 11:

	== Design ==		== Design ==
			Map view for traditional location display
			Arrow view for sexy fun location display
			Contacts view for fast privacy/prioritization changes

	== Implementation ==		== Implementation ==

M at 01:42, 21 February 2010

2010-02-21T01:42:58Z

@@ Line 1: / Line 1: @@
 == Design ==
 (round4)
      ----