Earlier quoted context omitted.
We don't send frequent emails - we haven't emailed our user base in months - until today about this launch. If users don't have an account, they can't have a consistent experience across platforms. A good user experience is our top priority here.
Look, it's your app, you can do what you want with it, but you're losing potential users with this requirement -- end of story.
Introducing Pulse for Web
21–30 of 39 posts
Re: Introducing Pulse for Web
#22Earlier quoted context omitted.
We don't send frequent emails - we haven't emailed our user base in months - until today about this launch. If users don't have an account, they can't have a consistent experience across platforms. A good user experience is our top priority here.
Congrats on shipping, and thank you for being part of the community. I would also second the feedback that requiring an email is undesirable. I know you are doing it so you can count reach and demographics easier and eventually sell those eyeballs or market research. We all need to eat. I get it. However! There is fatigue from needing to log into free services, especially when there are alternatives racing to the bot…
Re: Introducing Pulse for Web
#23Earlier quoted context omitted.
We don't send frequent emails - we haven't emailed our user base in months - until today about this launch. If users don't have an account, they can't have a consistent experience across platforms. A good user experience is our top priority here.
What about being able to at least preview the service without needing an account? We can do that already on the app version, before we decide to sign up with Pulse. Signing up is an extra step, and a little too much, for a product that I want to field test before I decide I want to use it.
Re: Introducing Pulse for Web
#24I'm sure I'm not the target. The window is - empty? [1] Ghostery informed me that it had to block Facebook Connect, but this surely isn't the intended landing page, even if I _do_ hate Facebook crap? I mean - I could at least use the links above and see the about page, but for a landing page this is kind of baad. 1: https://dl.dropbox.com/u/1194203/Pulse.png
Re: Introducing Pulse for Web
#25Re: Introducing Pulse for Web
#26Requiring facebook connect is a deal breaker. My corporate intranet blocks all facebook request (and I do as well with Ghostly). Please place the facebook connect JavaScript at the bottom of the page.
Re: Introducing Pulse for Web
#27Definetly looks interesting! However the corperate network I am on at the moment does not display the page correctly (could be anything from outdated html5 or just regular blocking). Either way, I really enjoy the iPhone/Android app! I agree though, I don't like the IE logo on the top right of the page. Call my crazy, but I am really fond of the simple, clean, eligant display on the iPhone/Android. Plus I just don't…
Re: Introducing Pulse for Web
#28can I use this product without signing up
Re: Introducing Pulse for Web
#29Earlier quoted context omitted.
Look, it's your app, you can do what you want with it, but you're losing potential users with this requirement -- end of story.
Yes, we agree that there will be some drop-off, but we're taking that chance in order to provide the best experience across platforms.