Opened 2 years ago

Closed 10 months ago

#740 closed enhancement (fixed)

New WordPress.com signup

Reported by: johnny5 Owned by: daniloercoli
Priority: minor Milestone: 3.1
Component: Add Blog/Site Version:
Keywords: Cc: isaackeyet

Description

I'm not sure if this is a bug or not, but when you signup for a WordPres?.com is loads a remote web page which is really tiny on the iPad, not centred, and not particularly inviting.

As you fill in the form, it behaves very strangely, with cursors that float in odd places, and things that appear for no reason

Attachments (3)

default wpcom signup.jpg (124.5 KB) - added by johnny5 2 years ago.
floaty mystery.jpg (126.6 KB) - added by johnny5 2 years ago.
ticket#740_fix.diff (404.3 KB) - added by irbrad 21 months ago.
switches signups from using web views to xmlrpc calls

Download all attachments as: .zip

Change History (14)

Changed 2 years ago by johnny5

Changed 2 years ago by johnny5

comment:1 Changed 2 years ago by mrroundhill

  • Milestone changed from 2.7-beta to Next Release

comment:2 Changed 21 months ago by irbrad

  • Owner set to irbrad
  • Status changed from new to accepted

comment:3 Changed 21 months ago by irbrad

I attached a patch file to this ticket that switches the iOS app from using the web view for WPcom signups to using XMLRPC. This also should fix ticket #737.

comment:4 Changed 21 months ago by koke

I looked at the patch today and there are a few concerns:

  • Any networking should be done in the background, otherwise the UI freezes until the network call finishes. This might not look like a big deal when your connection is fast and operational, but can lead to trouble on unstable or slow connections. It could even be cause of rejection from the App Store
  • It's still asking me to activate existing blogs. Any blog that was already in the app from a previous version, or that it's just added with an existing account shouldn't need verify activation. Right now all I get is a list of blogs asking for activation, even if they've been there for a while or are self hosted blogs.
  • Since the user is most likely to switch to the mail app after signing up, we should check for activation when the app becomes active. Having tap to check too is nice, but we can anticipate that

comment:5 Changed 21 months ago by isaackeyet

  • Cc isaackeyet added

comment:6 Changed 21 months ago by irbrad

I will address all of these issues this week. I will double check all of the network calls and move any still in the foreground to a background thread. I notice that the tap for activation is still in the foreground and causing a slowdown.

The existing blogs was something I just didn't think about and I'll handle for them accordingly. Since I keep deleting the app and reinstalling I didn't have any legacy data to handle for. :)

Item 3 is already handled for since the activation runs on every load of the blog list. I will add the check when the app is loaded via wordpress:// though.

comment:7 Changed 21 months ago by irbrad

I added a new patch that fixes the items mentioned above.

Changed 21 months ago by irbrad

switches signups from using web views to xmlrpc calls

comment:8 Changed 19 months ago by koke

  • Milestone changed from Next Release to 3.0
  • Summary changed from Signing up for WordPress.com is a bit rough to New WordPress.com signup

Decide if we want to do this native with Brad's patch or use the new optimized web version for 3.0.

Even if we go for the web version, we could use the extra integration to activate via wordpress:// url on the email

comment:9 Changed 11 months ago by daniloercoli

Working on the web version. No activation email, but fallback URL on the last page of the activate flow.

comment:10 Changed 11 months ago by daniloercoli

  • Owner changed from irbrad to daniloercoli
  • Status changed from accepted to assigned

comment:11 Changed 10 months ago by daniloercoli

  • Resolution set to fixed
  • Status changed from assigned to closed

The new signup workflow is available on .COM and the fallback URL seems to work fine.

Note: See TracTickets for help on using tickets.