You sign up for a job management tool. You build the briefings, set up the documentation templates, sort out the sign-off capture, and run a couple of your own crew through it. It works. So you roll it out to the subbies who actually do the bulk of your installs.

Then the calls start. Half of them can’t download the app. Not because they’re hopeless with technology, but because they’re on Android, and the software only runs on iPhone.

This is not a rare edge case. In the research I’ve done on field software complaints across the Australian trades market, the single most repeated grievance about one of the most widely used job management tools is exactly this: it is iOS-only, and a large slice of the workforce that needs it is not on iOS, a pattern that recurs consistently across public user reviews of the dominant field app. I want to walk through why this happens, what it really costs you (it is not just annoyance), and how to avoid building your whole field process on a foundation that excludes the people doing the work.

The iOS-only trap

Let me name the problem plainly. A good chunk of the solar and trades job management market grew up on Apple. The dominant field app in this space has been iPhone-only for years, and the demand for an Android version is not a quiet murmur. It is the loudest, most consistent request in its review history. Reviewers have pointed out features requested many years ago that still haven’t shipped, which tells you something about how a single-platform product treats a request that would require a second codebase.

Here is the thing that makes it bite in solar specifically. Your own office staff and maybe your lead installer might be on company iPhones. But subcontractors supply their own gear. They buy what is cheap, what is rugged, and what survives a fall off the back of a ute. A lot of that is Android. Reviewers running field teams have described crews of twenty, thirty or more people where the majority were on Android and the app was simply a non-starter for them.

Android holds a very large share of the Australian smartphone market, enough that you cannot assume any given subbie owns an iPhone (StatCounter, 2026). Rugged, “military-grade” handsets, which is the language tradies themselves use, are far more common on the Android side. So the platform choice that suits a head-office worker is the wrong bet for the field.

The three bad workarounds

When you hit this wall, you get three options, and all of them cost you something.

Option one: buy everyone an iPhone. Fine in theory. In practice you are now handing company phones to people who are not your employees, who work for three other businesses as well, and who may do four jobs for you this quarter and then disappear. The hardware spend and the admin of managing it rarely makes sense for non-exclusive subbies.

Option two: leave the subbies out of the digital workflow. This is what most operators quietly end up doing. The crew on the app gets the clean process. Everyone else goes back to phone calls, texts and WhatsApp. You now run two systems, and the bigger of the two is the messy one.

Option three: switch software. Painful, but at least it solves the root cause. The catch is the disruption: retraining, data migration, and the productivity dip while everyone relearns where things live.

None of these is good. The reason they all hurt is that the platform limitation forces a business decision that has nothing to do with how you actually want to run jobs.

What going back to WhatsApp really costs

Option two feels free because no one writes a cheque for it. That is the trap. The cost shows up later, in places that are harder to see.

A job briefing sent in a group chat is not a briefing. It is a message that scrolls away under the next twenty messages. It does not get read, it does not get acknowledged, and when something goes wrong there is no record that the subbie was ever told.

Install documentation captured in a chat thread is documentation you will never find again. Photos arrive two days late, or not at all. Sign-offs vanish into a conversation that also contains lunch orders and a video of someone’s dog. When you need to reconstruct what happened on a job, you are scrolling through months of chat instead of opening a job file.

Short paragraphs, because that is how this fails: quietly, one missing photo at a time, until the day you actually need the record and it isn’t there.

Where this hits your STC cashflow

Now connect it to the money, because this is where the platform problem stops being an inconvenience and becomes a financial risk.

Small-scale Technology Certificates (STCs) are not a government rebate, even though everyone calls them one. They are tradeable certificates created from an eligible system’s deemed generation, which liable entities must buy and surrender to meet their obligations under the Renewable Energy Target (Clean Energy Regulator, 2026). The customer assigns you the right to create them in exchange for an up-front discount, which is why it feels like a rebate to them but is not one.

To create those certificates, the installation has to meet the documentation requirements tied to the accredited installer, including the right photographic evidence and sign-offs from a Clean Energy Council accredited installer (Clean Energy Council, 2026). The Clean Energy Regulator can and does audit, and incomplete documentation delays or blocks lodgement.

Follow the chain. The subbie can’t use your app because they’re on Android. So the photos and sign-offs go into a chat thread, or don’t get captured properly at all. So the documentation pack is incomplete when admin goes to lodge. So the STC lodgement is delayed, and the cash that delivery was supposed to free up stays locked. The platform limitation feeds straight into a documentation gap, and the documentation gap is a cashflow problem. I am framing that as a chain of consequences, not as something a reviewer said directly, but it is the logical end of the same problem.

This is the same discipline failure I keep seeing across trades businesses generally: the back-office work that quietly decides whether you make money gets undermined by a tool that won’t run on half your team’s phones. If you want more on that admin discipline, I’ve written about it elsewhere on the CurrentFlow blog.

Why web-based is the structural fix

Here is the structural answer, and it is not complicated. A mobile-responsive web application runs on anything with a browser. iPhone, Android, an old tablet in the van, a borrowed phone on day one of a job. No app store, no platform lock, no “sorry, that’s iOS-only”.

The honest trade-off is offline capability. A native app can do more when there is no signal. But think about a real install. There is usually wifi at the property, or a hotspot off someone’s phone, often the homeowner’s connection. For the vast majority of residential and commercial jobs, the site has a connection, and the offline gap is a smaller problem than the platform gap it replaces.

This is part of why I’m building CurrentFlow the way I am. I wanted a system where the subbie opens a link, sees the briefing, captures the photos and signs off, all in the browser on whatever phone they own. The idea is that the platform of the person doing the work should never be the thing that breaks your process. It is not live yet, but that design decision is deliberate, and it comes straight out of watching this exact problem play out.

What to look for instead

If you are choosing field software now, here is the short checklist that avoids the trap:

The Australian Taxation Office is clear that subcontractors run their own businesses and supply their own tools, including their phones (Australian Taxation Office, 2026). Your software has to meet them where they are. Picking a tool that assumes everyone is on the same platform as head office is a quiet, expensive mistake, and it is one you can avoid by asking one question before you sign up: does this run in a browser on any phone?

References

Australian Taxation Office. (2026). Employee or independent contractor. https://www.ato.gov.au

Clean Energy Council. (2026). Accreditation for installers and designers. https://www.cleanenergycouncil.org.au

Clean Energy Regulator. (2026). Small-scale Technology Certificates. https://www.cleanenergyregulator.gov.au

StatCounter. (2026). Mobile operating system market share Australia. https://gs.statcounter.com

FAQ

Several of the field tools widely used by Australian trades grew up as Apple-first products, and building and maintaining a second Android version is a significant ongoing investment that some vendors have repeatedly deferred. In the review history of the most-cited tool, Android support has been the most requested feature for years and still has not arrived, based on the public review history of the tool. The result is a product that suits head-office iPhones but excludes a large share of field workers.

Can’t I just buy iPhones for my subcontractors?

You can, but it rarely makes sense. Subcontractors supply their own equipment, work for multiple businesses, and may only do a handful of jobs for you. Issuing and managing company phones for non-exclusive subbies is an expense and an admin burden that usually outweighs the benefit. A browser-based tool that runs on the phone they already own sidesteps the problem entirely.

How does phone software affect my STC lodgement?

If a subcontractor cannot use your documentation app because of their phone, the required photos and sign-offs often end up in a chat thread or don’t get captured properly. Incomplete documentation delays or blocks STC creation, because the certificates depend on meeting the accredited-installer evidence requirements (Clean Energy Regulator, 2026). A delayed lodgement means the cash you expected from the job stays tied up.

Are STCs the same as a government rebate?

No. STCs are tradeable certificates created from an eligible system’s deemed generation, which liable entities buy and surrender under the Renewable Energy Target (Clean Energy Regulator, 2026). The customer assigns you the right to create them for an up-front discount, which is why it feels like a rebate to them, but it is a certificate mechanism, not a government payment.

What should I look for to avoid this problem?

Choose field software that is browser-based rather than native-app-only, has responsive design tested on real Android devices, and allows sign-off and photo capture without installing an app. If a tool only offers an App Store download, confirm exactly what your Android-using subbies will be able to do before you commit your whole workflow to it.