I’d like to see an integration with Curve. There is numerous reasons why I’d like to see Emma integrate with Curve. Altough Emma supports quite a few UK and US banks. As you’re able to add cards from all over the world in Curve, as long as you’re a European citizen, you would get a mucher richer picture of your econemy by pulling in all the transaction data from Curve.
Yes, I agree, but I don’t think they will ever let us in; also an aggregator that aggregates another aggregator is kinda weird. ahaha
I’ve not used the feature, but AFAIK know you can connect Curve with Xero. So I don’t see why you couldn’t technically connect Curve to Emma as well then.
That’s unfortunate. I wasn’t aware that they’ve removed support for Xero as it shows as supported in the app. However, I’ve created a thread on the Curve discussion board about integrating with Emma. Hopefully they’ll respond in a timely matter.
Can we have Curve, Mark’s & Spencer’s credit card and Moneyfarm added?
Curve is not feasible by definition, even though I met with their head of product last week and he proposed it. The issue here is that they wouldn’t return balances and could potentially overlap with other integrations.
Couldn’t curve integrate balances into there app?
We are integrating this card.
A curve integration is out of the question for two reasons 1) they would never allow it 2) it would start conflicting with everything you have added and it would be a nightmare.
I’m very eager for New Day I see what you mean about curve ! Do you have any beta tester spots for any of this stuff or is it all in house ?
I’m not sure if it would conflict with everything if you only used Curve’s data for transactions and auto-discounted the bank copy of the data (since you could identity this through the Crv* prefix on transactions).
But it would be extra work and I don’t know if they would allow it.
I would really like it, though, for cards which would never be supported (like ones issued by banks abroad).
You could also treat Curve like an account, and auto-exclude the duplicate transactions that way, and have a “Curve” account in the list with the balance of your Curve cash. This would work a bit like PayPal. Or you could have Curve as standalone, and only import the transaction list, leaving the analytics feature etc to the copy on other cards. This would leave the transactions through Curve as separate and not analysed, but accessible from the account list. Just a few ideas, I’m sure something would be possible!
But it would need work on both Curve and Emma’s side, so not that likely - I do appreciate that!
Sorry for the double post, but a PS:
There did used to be a Testflight version of Emma a while ago, but this was scrapped in favour of more consistent and regular updates on the App Store release. I would love to have it back! Perhaps Edoardo can elaborate a bit on the thinking behind this, but I believe Emma have built the capability to turn on connections for just certain users instead via a feature-flagging mechanism.
This potentially allows a gradual rollout or testing of new connections with the App Store version of the app. Personally, I would welcome a programme for community members where we could help beta test connections - sort of like Curve has an open beta community where features are tested. Perhaps something for the team to consider?
Yeah we do still use Testflight internally for feature testing - we’ll try it out and then once we’re confident it’s ready to go we’ll release it to all users!
It’s deffo something we can discuss opening back up to users at some point though!
Seeing as I’ve been keeping @edoardomoreni on his toes this week I’d happily be a guinea pig in exchange for one of those Emma hoodies I don’t have enough gummy’s for yet
Gets my vote too. I’ve just got another hoodie from a company in preparation for winter.
@rebekah Thanks for replying!
That’s an interesting insight into your process, and the way you use Testflight now does make sense.
I suppose you could use two-tier Testflight testing, with your internal-only builds (alpha) and public (beta) releases, plus the actual public release. This may be too complicated, though, so I completely understand why you might not want to do that. Personally, I would love to use even the current internal-only builds - it wouldn’t matter to me if they broke things, since you can always just restore to an earlier build in Testflight. But this would create problems for keeping new features under wraps! You could just pause the “public” sharing of builds (which would probably be via a link) and only allow access to invited users (those with an Emma email address) for a short period to get around this.
I hope some kind of solution can be found!
+1 for one of those…