| The Following User Says Thank You to benny1967 For This Useful Post: | ||
|
|
2008-11-23
, 15:11
|
|
|
Posts: 1,635 |
Thanked: 1,816 times |
Joined on Apr 2008
@ Manchester, England
|
#22
|
|
|
2008-11-24
, 01:00
|
|
Posts: 1,513 |
Thanked: 2,248 times |
Joined on Mar 2006
@ US
|
#23
|
B]Issue #1: S60 isn't wide-spread enough[/B]
While S60 might be a well-established platform and attractive for developers, it's not popular enough to ensure a group of people who know each other in real life and would be willing to share their locations also own compatible phones. - It's the other way round: Although most people I know own Nokia phones (estimated 60%), not one of them has a S60/3rd Edition device.
While this sounds like a real bummer, in fact it's a minor issue. If Nokia really wants to push such a service, they could try to make it available for other devices after the research period.
Issue #2: Somebody should have done this before
Not Nokia's fault, of course. But it's so obvious that with a clever mixture of existing, well-established technologies (XMPP und RSS), this kind of service would have been possible before. There's no magic to it.
This is exactly the creative input missing from the community, BTW, that people sometimes talk about. And this is the reason why I started ranting about the project in an Internet Tablet forum: The N810 is the perfect device for this service. Friend View by <enter your most admired Maemo developer here> should have been on the N810 from day 1.
Issue #3: They should have used documented technology
From my point of view, this is the main thing. I really don't care if they release a research project as proprietary software on one single platform only... That's not ideal, but it's not such a big deal, either.
The really interesting stuff goes on beyond the application. How data is exchanged, which data, which server, .... all this. The focus should have been on establishing a de facto standard on how to re-use existing, open technology for such a project. This way, it wouldn't matter much that their own client only runs on a few devices. People could toy with the idea and both improve and spread it.
So what I feel is "so 1980s" is the concept that (that's how I interpret it) Nokia thinks they could gain any commercial advantage by not using open standards and tying the service to both their devices and their servers.
A good service would allow me to switch client and service provider and still have the same basic functionality with the same contacts I had before. Like I can change my mail client and my mail server and still write mails to the same people I did before - because mail, in fact, is POP3/IMAP/SMTP, and not Outlook/mx3.isp.net.
Solution to #3
What should they do instead? Well, what do we have? We have XMPP to indicate presence (online/offline) and location (via XEP-0080). That's already half of what Friend View does. The other half is the micro-blogging thing that doesn't fit well into XMPP because of its non-realtime nature. Well, there are microblogging services. Microblogs can be processed as RSS, and RSS has standard ways of including latitude/longitude in machine readable form into feed items.
What we also have is gateways between XMPP and existing microblogging services. They are in productive use and even recommended by Nokia Beta Labs as an additional value for their Nokia Chat service.
So the full functionality of Friend View could be mimicked by a location-aware XMPP-client that posts to and processes RSS from a micro-blog. How exactly this is done and how you handle access control in this case would be the content of this research project.
This would be the 21st century way to do it. And I don't even think Nokia would need to be afraid of the competition if they show them how to do it: They'd still have this advantage of making it work 'out of the box'. So they'd be the gravity center of the community, even if some (who am I according to some people here? Oh yesnerds choose to join in from their GPS-equipped laptops or (even worse) Internet Tablets.
|
|
2008-11-24
, 07:13
|
|
|
Posts: 11,700 |
Thanked: 10,045 times |
Joined on Jun 2006
@ North Texas, USA
|
#24
|
|
|
2008-11-24
, 08:47
|
|
|
Posts: 3,790 |
Thanked: 5,718 times |
Joined on Mar 2006
@ Vienna, Austria
|
#25
|
And a social network app optimally shouldn't be limited to any OS, but your comments fail to recognize that (at least in the US and Canada) there are no open standards in the cellular ecosystem.
Nokia has at least pushed S60 independently of the network operators; and to a large extent that you are apparently ignorant of and certainly unappreciative of.
N810 is not the perfect device for this since: 1) by your own admission, there aren't enough devices; 2) a S60 phone has the right performance match.
See my comments on #1 regarding the cellular ecosystem. A suggestion of someone other than a network operator establishing a "de facto standard" (broader than S60) isn't credible.
The network operators are the gravity center (some would say the black hole) of services innovation in the US.
|
|
2009-01-29
, 09:20
|
|
|
Posts: 3,790 |
Thanked: 5,718 times |
Joined on Mar 2006
@ Vienna, Austria
|
#26
|
|
|
2009-01-29
, 12:14
|
|
|
Posts: 3,790 |
Thanked: 5,718 times |
Joined on Mar 2006
@ Vienna, Austria
|
#28
|
I'm not sure we're talking about the same issue here. In fact, there are several different issues with this Friend View thing, not all of them being under Nokia's control.
Issue #1: S60 isn't wide-spread enough
While S60 might be a well-established platform and attractive for developers, it's not popular enough to ensure a group of people who know each other in real life and would be willing to share their locations also own compatible phones. - It's the other way round: Although most people I know own Nokia phones (estimated 60%), not one of them has a S60/3rd Edition device.
While this sounds like a real bummer, in fact it's a minor issue. If Nokia really wants to push such a service, they could try to make it available for other devices after the research period.
Issue #2: Somebody should have done this before
Not Nokia's fault, of course. But it's so obvious that with a clever mixture of existing, well-established technologies (XMPP und RSS), this kind of service would have been possible before. There's no magic to it.
This is exactly the creative input missing from the community, BTW, that people sometimes talk about. And this is the reason why I started ranting about the project in an Internet Tablet forum: The N810 is the perfect device for this service. Friend View by <enter your most admired Maemo developer here> should have been on the N810 from day 1.
(Don't get me wrong here - I'm not really accusing developers here of missing this opportunity. I know it doesn't work that way. I just sometimes wonder why and how a group/community as a whole could become more creative in inventing new services instead of copying another media player feature from the big guys. The developer can't start to work without the brilliant idea, and the brilliant idea needn't necessarily be his own.)
Issue #3: They should have used documented technology
From my point of view, this is the main thing. I really don't care if they release a research project as proprietary software on one single platform only... That's not ideal, but it's not such a big deal, either.
The really interesting stuff goes on beyond the application. How data is exchanged, which data, which server, .... all this. The focus should have been on establishing a de facto standard on how to re-use existing, open technology for such a project. This way, it wouldn't matter much that their own client only runs on a few devices. People could toy with the idea and both improve and spread it.
So what I feel is "so 1980s" is the concept that (that's how I interpret it) Nokia thinks they could gain any commercial advantage by not using open standards and tying the service to both their devices and their servers.
A good service would allow me to switch client and service provider and still have the same basic functionality with the same contacts I had before. Like I can change my mail client and my mail server and still write mails to the same people I did before - because mail, in fact, is POP3/IMAP/SMTP, and not Outlook/mx3.isp.net.
Solution to #3
What should they do instead? Well, what do we have? We have XMPP to indicate presence (online/offline) and location (via XEP-0080). That's already half of what Friend View does. The other half is the micro-blogging thing that doesn't fit well into XMPP because of its non-realtime nature. Well, there are microblogging services. Microblogs can be processed as RSS, and RSS has standard ways of including latitude/longitude in machine readable form into feed items.
What we also have is gateways between XMPP and existing microblogging services. They are in productive use and even recommended by Nokia Beta Labs as an additional value for their Nokia Chat service.
So the full functionality of Friend View could be mimicked by a location-aware XMPP-client that posts to and processes RSS from a micro-blog. How exactly this is done and how you handle access control in this case would be the content of this research project. The result would be
- a location-aware microblogging service that works with any location-aware XMPP-client people want to write for any platform
- location aware, RSS-processing clients that work with any location-aware microblogging service
This would be the 21st century way to do it. And I don't even think Nokia would need to be afraid of the competition if they show them how to do it: They'd still have this advantage of making it work 'out of the box'. So they'd be the gravity center of the community, even if some (who am I according to some people here? Oh yes:) nerds choose to join in from their GPS-equipped laptops or (even worse) Internet Tablets.