Skip to content
TAA

App development in Adelaide

App development for Adelaide supplier operations

Turn supplier evidence, document revisions and approval handovers into a manageable workflow. Adelaide projects begin with the information that may be shared and the decisions an app must support.

By , software architect · Last updated

Defence SA identifies Osborne, Edinburgh and Technology Park Adelaide as defence precincts. For a supplier serving that environment, I would begin with a bounded administrative workflow and your customer’s information-handling requirements.

Which supplier records are suitable for a first app?

Start with the records your organisation has approved for the proposed hosting and support arrangements. A candidate workflow could track document requests, revision numbers, reviewer comments and outstanding actions. Establish a sample pack before design: an accepted submission, a rejected revision and a late response. Those examples determine whether the app needs a simple checklist or a controlled review process with separate author and approver roles.

How should an approval survive a revised attachment?

An approval should stay attached to the exact revision that was reviewed. The proposed app can create a new review item when a supplier replaces a document, retain the earlier decision and mark downstream actions that need another look. That makes a procurement handover more useful than a folder of similarly named files. It also gives a departing reviewer’s replacement enough context to continue the work without reconstructing an email chain.

Who handles South Australian government privacy?

The state’s Privacy Committee and Information Privacy Principles Instruction are relevant to South Australian government agency work. This should not be described as a general South Australian privacy act applying to every company. Private organisations need their own federal-scope assessment using OAIC guidance. For the app, identify which attachments contain personal details and whether an agency contract imposes additional handling conditions.

How can a remote supplier project be assessed?

Use a written boundary for both functionality and permitted information. The delivery plan should identify who provides sample documents, who accepts a revision workflow and who approves any hosting choice. Remote access, restricted material and customer onboarding conditions must be resolved before such material enters the development environment. A fixed-price milestone can then cover a reviewable administrative slice, with broader integrations quoted after the customer grants the necessary access.

Price, contract and data

  • Every step has a fixed price, set in writing before work starts; extra scope is added only through a change order you approve in writing.
  • The code sits in your repository from day one; with each paid milestone, the rights to everything delivered up to that point pass to you. Third-party components and pre-existing tools keep their own licences.
  • For rescues and new builds, 90 days of free bug-fixing after launch, on top of the 12-month warranty under the Terms. Ongoing operation starts at $1,400 a month.
  • You contract with DigitalFreedom Global LLC, Wyoming, USA. All prices are net; the tax treatment is clarified before contract and stated in the offer.
  • My infrastructure is in the United Kingdom and Europe. Where I process personal data on your behalf, we sign a data processing agreement. The provider overview on digitalfreedom.co.za lists the subprocessors, their locations and the contractual safeguards.

Common questions

Does this service include defence accreditation?

No accreditation or customer approval is implied. Your organisation must establish the conditions for its particular material and supplier relationship; the proposed build can document the controls that are actually delivered.

What should we bring to the first review?

A sanitised submission pack and a description of the approval chain are enough to discuss scope. If an existing portal needs assessment, the App Check is $2,000.

Define a supplier document boundary

Use a sanitised document register to show the information your customer permits in the proposed environment. Select a revision that was returned and identify the reviewer’s exact request. We can work through who supplies the replacement, what happens to the earlier approval and which downstream action must wait. Your procurement or information owner can then review a concrete workflow and its dependencies before any restricted material is introduced.

Free 30-minute call, no obligation

You talk to Marcel directly, the architect who is accountable for the work. No sales rep, no pitch.

The calendar is served by Cal.com. It loads only after you click (data goes to Cal.com, US). Privacy policy

Prefer to write first? Describe your situation, with a link to your app, repository or questionnaire. You get an answer within one business day.