Feature Request: Increase customizability of UI.

[nrj]

[Aug 9, 2013: issue title made more general (dgoldman-ebay)]

It would be great if we had the option to do this. CardIO is great but it doesn't really "fit" with the rest of my app's design. A big win would be if I could specify a custom UINavigationBar subclass.

For example, UINavigationController offers an API like this:

initWithNavigationBarClass:[MyCustomNavBar class] toolbarClass:[UIToolbar class]]

[tooluser]

This in general - the lack of customizability - is the primary reason we are investigating switching to jumio. If Card.io could support this it would be a major tool in the argument against making that switch. 

On 6 Aug, 2013, at 13:53 , nick jensen notifications@github.com wrote:

It would be great if we had the option to do this. CardIO is great but it doesn't really "fit" with the rest of my app's design. A big win would be if I could specify a custom UINavigationBar subclass.

For example, UINavigationController offers an API like this:
initWithNavigationBarClass:[MyCustomNavBar class] toolbarClass:[UIToolbar class]]

—
Reply to this email directly or view it on GitHub.

[dgoldman-pdx]

Dave from card.io here.

We hear you about the desirability of even more UI customizability. We are evaluating some different approaches toward that end.

[tooluser]

'Even more'? What is customizable beyond the nav bar color, currently? I apologize if I missed a major change, but it's essentially not customizable, right? Tell me I'm wrong...

I think it would be desirable to be able to skip the manual entry screen - we want to use card.io for its primary function, scanning, and customer needs for manual entry vary with their provider's requirements and risk tolerance, besides just having our own view for that already.

The scanning screen is great; the transparent overlay is classy and fits just about anywhere. Love the transparent overlays. It'd be nice to make the 'acquisition' rectangle a custom color, but that would be gravy.

This has been our number one difficulty in justifying usage for some time. We've foregone looking for alternatives because we had other areas of our app to polish, but it's surprising to me that this has been static for so long. Every dev I talk to about card.io says the same thing - awesome tool, painfully rigid usage experience.

I'm looking forward to seeing it customizable, and hoping it's not even too far forward!

On Aug 7, 2013, at 15:22, Dave Goldman notifications@github.com wrote:

Dave from card.io here.

We hear you about the desirability of even more UI customizability. We are evaluating some different approaches toward that end.

—
Reply to this email directly or view it on GitHub.

[dgoldman-pdx]

@tooluser So noted! :)

[tooluser]

Is there any customizability other than the color of the nav bar?

Sent from my iPad

On Aug 9, 2013, at 18:12, Dave Goldman notifications@github.com wrote:

@tooluser So noted! :)

—
Reply to this email directly or view it on GitHub.

[dgoldman-pdx]

Here are the customizable options currently available (see CardIOPaymentViewController.h):

• keepStatusBarStyle
• navigationBarStyle
• your choice of which fields should appear on the manual entry screen in addition to "Number"
• whether to show a first-time alert
• whether to use card.io or PayPal logo
• whether to show the "Manual Entry" button

Additional customizability, including scan-guide color, is definitely under consideration here. Feel free to further enumerate what you'd like to see -- and get those other devs you talk to to do the same. :)

[josharian]

@tooluser if you want to avoid the card.io manual entry screen entirely, you can check +canReadCardWithCamera and only invoke card.io if card scanning is possible.

[tooluser]

Thanks! As I read it, though, this doesn't allow suppressing the manual entry screen selectively; it allows suppressing all of card.io en masse. If card.io is enabled, it displays from the manual entry screen, right? 

// Indicates whether this device supports camera-based card scanning, including
// factors like hardware support and OS version. card.io automatically provides
// manual entry of cards as a fallback, so it is not necessary to check this.

On 12 Aug, 2013, at 10:15 , Josh Bleecher Snyder notifications@github.com wrote:

@tooluser if you want to avoid the card.io manual entry screen entirely, you can check +canReadCardWithCamera and only invoke card.io if card scanning is possible.

—
Reply to this email directly or view it on GitHub.

[josharian]

Thanks! As I read it, though, this doesn't allow suppressing the manual entry screen selectively; it allows suppressing all of card.io en masse. If card.io is enabled, it displays from the manual entry screen, right?

I'm not 100% sure I follow the question. You'd want to do something like:

if ([CardIOViewController canReadCardWithCamera]) {
  // show card.io view controller
} else {
  // show something else, like your custom manual entry view controller
}

You're guaranteed that if +canReadCardWithCamera returns YES, then the user will see the camera, immediately, not manual entry.

[josharian]

(Or use canReadCardWithCamera to control whether a button is hidden, or however else you want to control the flow.)

[josharian]

@nrj @tooluser we'd love to get offline feedback from you on some stuff we're experimenting with on this front. If you're game, please shoot me a quick email at jbleechersnyder [preposition] paypal [punctuation] com at your leisure.

[dgoldman-pdx]

@tooluser re this request:

It'd be nice to make the 'acquisition' rectangle a custom color, but that would be gravy.

The just-released version 3.2.3 now includes this option.

[burnto]

It'd be nice to make the 'acquisition' rectangle a custom color, but that would be gravy.

The just-released version 3.2.3 now includes this option.

Though we heartily recommend guide colors of the "unbearably bright green" variety.

[tooluser]

Heh. I actually don't mind the color, but making the overall experience fit our ux scheme is important to the pixel people.

On Aug 29, 2013, at 12:50, Brent Fitzgerald notifications@github.com wrote:

It'd be nice to make the 'acquisition' rectangle a custom color, but that would be gravy.

The just-released version 3.2.3 now includes this option.

Though we heartily recommend guide colors of the "unbearably bright green" variety.

—
Reply to this email directly or view it on GitHub.

[dgoldman-pdx]

@nrj, @tooluser I hope it's okay with you if I close this issue for now. For one thing, I think we've added to the current API most or all of the customizable elements you've mentioned above. And for another, you're now in email contact with us re our new, experimental stuff.

[tooluser]

Oh, heck yeah. Thanks.

On 4 Sep, 2013, at 17:09 , Dave Goldman notifications@github.com wrote:

@nrj, @tooluser I hope it's okay with you if I close this issue for now. For one thing, I think we've added to the current API most or all of the customizable elements you've mentioned above. And for another, you're now in email contact with us re our new, experimental stuff.

—
Reply to this email directly or view it on GitHub.