Amazon Cognito
131–140 of 166 posts
Re: Amazon Cognito
#132Earlier quoted context omitted.
It's a valid concern. AWS has been around for many years now with numerous services. Has there been a single offering which they retired or stopped supporting? I'm not aware of one. Amazon doesn't just create services, throws them over the wall and see if they stick. Rather, they almost always RESPOND to customer requests. Dr. Werner Vogels, AWS's CTO makes a point about that approach at about any keynote he gives. S…
I am unaware of AWS modules discontinued by amazon, but it is also true that the oldest services are the most popular (S3, EC2) while some of the most recent ones have a (apparently?) smaller user base (SWF, Kinesis, AppStream). I think I remember amazon people saying they are actually dogfooding this stuff so it should stay available for a long time anyway, rather than being a random Google Reader.
AWS's practice of charging people seems to make it pretty easy to justify not pulling a Google on users.
Re: Amazon Cognito
#133The interesting thing about all these services is that they're trying to abstract away the same types of problems that all developers come across: Identity, connectivity, sync/backup (and to some extent, deployment). A different (and more disruptive?) approach to this would be to put more control of these things into the hands of end-users such that they provide the 'backend' into which you (the developer) load your…
Users don't care about. Not worth doing.
Re: Amazon Cognito
#134Amazon and their ambition has no bounds. They really are the grizzly bear in the room of online services.
Re: Amazon Cognito
#135While this (and other similar) Backend-aaS look very appealing at first glance, it seems to suffer from the same problem as most AWS offerings - terrible platform lock-in. Show me that I could move all of this to another provider if I need to, and then we can talk seriously. I also wonder how they "manage[s] the complexity of conflict resolution" without manual intervention.
Is anyone delivering the equivalent with less lock-in? I can understand both sides of the argument but it seems that over time stuff always migrates towards more control (ie, people migrate OFF of Parse, Heroku, AWS, etc). I'd envision a much better set of images, Fabric/Chef recipes, to the point where you get your AWS but with vanilla OSS on generic hosting providers.
Doesn't CouchBase Mobile Sync Gateway do something similar?
Re: Amazon Cognito
#136The interesting thing about all these services is that they're trying to abstract away the same types of problems that all developers come across: Identity, connectivity, sync/backup (and to some extent, deployment). A different (and more disruptive?) approach to this would be to put more control of these things into the hands of end-users such that they provide the 'backend' into which you (the developer) load your…
Do users really care about this? My guess is that 99% don't and don't want to deal with these details. The project sounds cool and like something the HN crowd might want, but my intuition is that most users won't understand the implications. It also adds an extra step in the data storage process within the app, which increases friction and seems like it would be hard to get developers to adopt. All that said, I'd lov…
The problem isn't that users don't care, but that there's no revenue model. As a result none of these decentralized networking or platform companies can get funding.
Without funding, they don't have the resources to build truly compelling products. You can prototype something in your spare time, but to polish something to be truly competitive outside enthusiast circles you need to dedicate serious time to it.
Even if users did care there is no mechanism for them to pay for it, so it doesn't happen.
Re: Amazon Cognito
#137The interesting thing about all these services is that they're trying to abstract away the same types of problems that all developers come across: Identity, connectivity, sync/backup (and to some extent, deployment). A different (and more disruptive?) approach to this would be to put more control of these things into the hands of end-users such that they provide the 'backend' into which you (the developer) load your…
Isn't that what App.net was supposed to be? By most standards that project was a huge failure. It's hard to proposition a user to start managing their own silo.
App.net was centrally hosted and centrally controlled, so it wasn't really all that different from its competitors. It also had execution issues.
Re: Amazon Cognito
#138seems kind of expensive for what it does. imagine a game with 100k DAU (big, but not huge) 2 sessions per user per day say 10 "saves" per session 100,000 * 2 * 10 = 2 million synchs / 10k * $0.15 = $30/day for $900/month you could do FAR better just rolling your own these numbers are all reasonable for a mobile game... so it seems to me that the main use pattern would be for apps that don't need to synch very often.…
Yeah - I think Parse is much cheaper
Re: Amazon Cognito
#139Earlier quoted context omitted.
I thought like this once. Futurists have a tendency to imagine a world of changed human behavior and it's compelling to do so. The reality is that the future rarely arrives as sweeping change, but rather as metaphor and specialization. Whereas you can imagine others adopting new patterns of behavior because you understand the underlying reasons why such behavior is reasonable, the metaphor through which you explain t…
> time and again we've shown that those are not things consumers want or are willing to pay for CITATION please. I think we have never seen such things. We've not had studies that control for all other factors and then conclude that users don't want control and privacy. I think your claim is flat out wrong. You're taking the fact that most users won't sacrifice by using a lower-quality, obscure thing for privacy and…
There have not been any case studies that have empirically demonstrated this to be true. If that is your basis for evaluating my statements then I cannot support my claim in a manner that you would find satisfactory.
I would however, anecdotally highlight the progression of social services from places of privacy to places of publicity. One could argue that sites like "The Well" were the original social networks but they did not grow (whether by choice is of course a matter for debate). Over time, each successive social startup defaulted to a more open stance and scaled an order of magnitude in users with each step. The trend suggests that all things being equal, users will say they want privacy but want the features publishing and syndication provides (voting purely with their registrations and advertising value).
I agree that privacy has value, but I would argue that the anecdotal evidence suggests that users want less private services (and yes I'm aware that correlation is not causation, but I think this observation is apt). This is not law or dogma but rather a thought and I'm sorry if it was communicated poorly previously.
Re: Amazon Cognito
#140I don't know how Amazon comes up with names for its products, but recently they all strike me as weird and stupid names. Do they confer with marketing first? Zocalo, Cognito? Really? These are the kinds of names you invent when you're looking for a cheap domain name for your startup. For Amazon, they don't make a lot of sense. They just seem like some executive out of their marketing depth and out of touch trying to…
Cognito means known, recognized, identified; contrast with incognito. Is that really such a terrible, horrible, no good name for a service that verifies user identities and manages user profile data? It's a shame Amazon can't afford to hire a marketing genius like you, but I think they're doing the best they can with the idiots they have to work with.
But as a user enters cognito, they then become incognito. That does not make sense.