We all know how valuable email marketing is and how stable arpReach is. It’s been the backbone for some of the biggest names in internet marketing and other groups for years.
Sure, it doesn’t have the drag and drop ‘ease’ of other popular autoresponder services but it has always had the power and capability to let you do pretty much anything that other services have only recently started introducing. You just needed to learn how to do the ‘smart’ things. But even if you didn’t, it always sends out your emails.
In many respects, arpReach was and still is too good for its own good. It simply works and keeps working.
It filled (and still fills) an important hole in self-hosted email marketing software options. And it’s why smart marketers and business owners still buy arpReach V1 licenses today and will do for many more tomorrows.
When I look back at it, the early ARP3 and arpReach adopters have had an amazing return on their investment with the original developer and owner.
When I took over at the helm and breathed new life into arpReach that value increased further as I added new API’s which allowed you to hook-up with third-party services like Zapier and page or form builders simply (Not to mention all of the other improvements and fixes.).
Not that you always need to use API’s for these services. arpReach has always given you the ability to create unlimited ‘HTML forms’ which you can also ‘drop-in’ to those page builders to capture your leads.
Likewise, coders and programmers who understood and understand the flexibility that arpReach gives them have always been able to create custom functions and trigger them using CURL.
Put in simple terms, that means you can make arpReach do clever things automatically. Both with and to your website.
For all the good stuff though, there has been a downside to the strengths of arpReach and the early adopters’ good fortune. That is …
The speed of introducing even more improvements has been painfully slow.
The main reason for that can’t be ignored. The buy once, lifetime everything payment model does not allow for sustainable ongoing development and introducing improvements. Why?
The software that runs the servers, that any online business tool uses, (not just arpReach,) is continually being updated to cope with changes to the wider internet, web and mobile infrastructure and the way it gets used, plus its ever-growing adoption.
Software updates are the bain of modern life.
I can’t tell you how many people moan to me about Windows 10 updates and the amount of time it takes. I put off updating for as long as possible. I remember when it was Windows 98SE. (It was SOOOO much quicker than 10).
Even my Kids are affected by technology changes. Their world collapsed when SnapChat rolled out a new update that “changed everything”.
My eldest girl’s words were: “Everyone is complaining. It’s all different. *kdhyjdhpl* has moved. I can’t do *syufjem8kl* anymore. Why did they have to change everything?” She’s 13.
sidenote: (*kdhyjdhpl* and *syufjem8kl* are obviously not real names of real functions that do things. Kids (or Snapchat) use totally different language and terms. As I’m not a Snapchat user those ‘features’ sounded unintelligible to me. But there is a point …
I had to tell her gently …
“Someone moved your cheese. I’m sorry but either deal with it or stop using it.” – (she went off and searched Google for “who moved my cheese summary?”. She’s a smart 13 🙂
All software has a shelf life.
Just like Microsoft introduced and ended the lifecycle of it’s “Windows 98” ‘software version’ there have been ‘end of life’ notifications for lots of the PHP and MySQL server versions that arpReach has been able to use over the years.
PHP 7 is the current version lots of servers are being updated automatically to use. And to give arpReach the capability to work with it and use the improvements PHP7 offers, we’ve also had to change the framework that arpReach uses.
I’m not going to get ‘technical’ but I’d like give you a little background context.
A framework is another ‘type’ of software. Think of it as the ‘thing’ (or scaffolding) that allows the dashboard you login to, to talk to the server functions/features you use.
Functions can do or trigger things called ‘actions’. They can also record the result and update your database. like who was sent which email, when and if they opened it or clicked a link.
Once ‘it’ does the important functions and actions stuff you need, you can make it look pretty and simpler to use with ‘skins’ or templates.
PHP7 doesn’t have or use all of the same ‘functions’ earlier versions of PHP do. This means lots of changes had to be made to arpReach which make ‘it’ something new which currently looks like arpReach, but isn’t.
It’s taken lots more time than I’d hoped to get to this stage but all things considered, “#V2” is ready to take shape, change, and become something more than and different to arpReach.
Heres just one of the new features available in #V2. The ability to simply resend to contacts who didn’t open your last (or any) broadcast or click links or any combination of any of the new available options.
#V2 will soon be available for a small group of pilot users, as a hosted service, with different licensing to arpReach.
In the next update, I’ll share more details about what else you can look forward to.