Are you going to implement the ability for users to specify their own SMTP server? This is a huge negative for Wave as mail gets stuck in spam filters and this will only get worse and worse as more malicious mail circulates, and also clients don't like seeing mail come from some long random Wave email address, I've literally had calls from clients saying I've been hacked because of this.
I think of it as a foundational feature that should be included. Can you share if you feel the same way or if there are/aren't plans to incorporate this? I think this would be a huge factor in retaining your own clients/Wave users and perhaps capturing those who turn away due to something like this (which is a major in my opinion).
December 13th, 2018:
We're delighted to be finally taking the wraps off the first stage of deploying our new GraphQL API. We've created this space within the Wave Community Forum specifically for developers and users of the Wave API to ask questions, share ideas, and give feedback.
Today, we're starting with Business and Customer APIs, and we'll be rolling out more endpoints through 2019. Our API and Partner Integrations Team are looking forward to working alongside the developer community over the coming months to build the Wave APIs into a powerful resource for all users.
You can find documentation and start creating your Application in our Developer Portal now.
We look forward to connecting with you!
I would really like to have the delivery note feature implemented where by am able to just convert all the data from an invoice and provide it to the client for signing or stamping. A delivery note is very key in our country and its hard to get paid without it.
The other feature is an estimate app just the way we have an invoice app where i can be able to give quotations on the go. Many are the times when am just called while on the road to give a quotation to something and i have to tell the client to give me some few minutes/hours till am settled on a computer so as to generate the quote.
The above features would be really great.
Create a Wave API as a service. Allow developers access to an API to be able to use Wave's features in separate applications.
As an application developer I want to build an app that could use some Estimate/Invoice/Payment features. Instead of building all of that out myself it would be nice if I could call Wave APIs to handle that so I can focus on the actual niche problem my application solves and release faster. Wave will still be able to handle all the payment processing to make money, my application has a richer feature set with less code to maintain and users get to enjoy a full-featured application.