App development · Chicago, IL
App development for Chicago companies
Chicago is derivatives and futures trading, heavy manufacturing, and the freight network that connects both to everywhere else. Few metros combine regulated finance and physical logistics as tightly.
Founded
2017, and still independent
Bench
115+ people, 80 Databricks-certified
Experience
Fifteen years average, per engineer
Serving
Chicago, Naperville, Evanston, Schaumburg
Chicago apps tend to sit where finance meets freight: a trading tool, a warehouse handset, a dispatch console that has to agree with both. We build the app and the event log it depends on, because reconciliation is a business function here rather than a bug.
AzureTechFabric is a Databricks partner with an award-winning Databricks engineering team, 80 of them Databricks-certified, and a Temporal partner. Where a system reaches past the workspace we build on Azure, AWS and Google Cloud.
What app development covers
iOS and Android
A shared codebase where it suits the product and native where it does not. It is a per-product decision rather than a house position, and anyone who answers it before hearing what the app does is telling you about themselves.
Web apps
The browser half of the same product, built to be changed safely years after the original team has moved on. Tests that mean something, seams where the business logic can move, a deployment nobody is afraid of.
The backend and API
Built with the app rather than found afterwards. Where you already have an API we will work with it and say plainly if it is the reason the app will feel slow.
Offline behaviour and sync
Decided deliberately at the start. A field app that has to work in a warehouse with no signal is a different design from one that assumes a connection, and retrofitting the difference means rewriting the data layer.
Release and store submission
Staged rollout so a bad build reaches a few hundred people rather than everyone, and the App Store and Play Store process including the rejections, which arrive for reasons that have nothing to do with code quality.
Keeping it alive
Two OS releases a year, certificates that expire while somebody is on holiday, and store policies that change. We stay on a maintenance footing or hand over with the provisioning and the release process written down.
Clients we have done this for
AmTab outgrew the systems underneath it and modernised the estate to match demand rather than throttle it.
B2B ecommerce
AmTab
AmTab grew fast enough to outrun the systems underneath it, and modernised the estate to match the demand rather than throttle it.
The trade has to reconcile
CFTC and SEC recordkeeping expect a reconstructable history, and in a business where reconciliation is a daily function an approximate event log is not usable. The event log has to be the source of truth rather than a derivative of it.
None of that is unusual for Chicago, and none of it is a reason to build slowly. It is a reason to decide where the evidence comes from before the first handler is written, because the alternative is reconstructing it later from logs that were not designed to answer the question.
How an engagement runs
01
A technical conversation
Not a sales call. An engineer, asking what the app has to do, who uses it, what it talks to and what has been tried. Product and design people join the same conversation where the work needs them.
02
Two weeks, fixed fee
A short assessment ending in a written plan with a scope, a sequence and a number, including the decisions that are cheap now and expensive later. You own the document whether or not you carry on with us.
03
Build with your team in the repo
App, backend and release process together, senior throughout. The person in your standup is the person writing the code.
04
Ship, and keep shipping
Staged rollout, store submission, and either a maintenance footing with us or a handover with the provisioning and release process written down. The handover version only works if it was planned before launch.
Two weeks, fixed fee, and a written plan whether or not you build it with us.
Headquarters
1530 E Williams Field Rd, Ste 201Gilbert, AZ 85295
Phone
+1 (480) 681-6806Also
Amsterdam, Dnipro, Hyderabad
Working hours
Chicago business hours, most days
FAQ
App development in Chicago: common questions
Do you work with Chicago companies?
Yes, and with companies across the United States. Arizona does not observe daylight saving, so we are one hour behind you from November to March and two hours behind from March to November. A morning standup on your clock is still early afternoon on ours.
Do you have an office in Chicago?
The office is in Gilbert, Arizona, with teams in Amsterdam, Dnipro and Hyderabad. Delivery is remote or hybrid, and we travel for discovery, workshops and the opening weeks of a build.
Can the event log serve as our reconciliation source?
That is what it is for. The event log is authoritative and read models derive from it, so a projection can be rebuilt by replay rather than reconciled by hand. In a business where reconciliation is a daily function that is the difference between an hour and a week.
Native or cross-platform?
Cross-platform for most business applications, native where the product depends on something the platform does specifically. It is a per-product decision, and we will say which we think applies once we have heard what the app does.
Do you handle App Store and Play Store submission?
Yes, including the rejections. First submissions get rejected for reasons that have nothing to do with code quality, and knowing which ones are coming is most of what makes a launch date real.
App development elsewhere
Other metros we publish this for. The full list is here.