After finding no other products on the market that have an app delivering the same features JuiceBox had when I purchased it (especially delayed charging with a SoC limit), I decided to buy an OpenEVSE and OVMS and then return mine to Costco for a refund.
I plan to write a Shell script wrapped in a Linux service (e.g. run on a RasPi) and/or an Android app that will run in the background, using the RestAPIs detect when OpenEVSE on the network is plugged into a vehicle, read latest SoC from OVMS authenticated account, calculate when charging needs to start to bring up to configured limit (e.g. 80%) by configured time based on day of week and vehicle details, set an internal timer or clock triggered event to act at that start time and also detect when OpenEVSE is plugged/unplugged rapidly to start immediately, then send command to charge to kWh limit. That should allow the most seamless experience without needing to open an app every time.
Also considering writing the app to let you pick the start SoC if you don't have OVMS, pick target SoC with some common level quick buttons, pick start or end charging time and calculate the other, and wipe OpenEVSE schedule, set start and end time schedule for same/next day (so it will only overcharge if you leave it plugged in for a full week). Alternatively do the same to schedule inside the app or click a charge now button and send the charge limit command instead. Charge limit in kWh is much more accurate than calculating the time for high target SoC once charging rate drops off when what you want is a SoC limit.
Don't expect much from me as far as publishing this app quickly, as it's been a long time since I wrote an Android app, but I'll consider publishing it or sharing the Shell script after I've written it in my limited free time and tested thoroughly.
Also I don't own an iOS development environment and have little desire to use an iPhone app for this.
Feel free to use my idea.