# App development in Houston, TX > Energy and petrochemicals on one side, the Texas Medical Center on the other, and a long tail of companies serving both. If you run one of them, you generate instrumented data at a volume where an AI answer without its source is unusable, and a regulator will eventually ask how a number was reached. Canonical: https://www.techfabric.com/app-development-houston Serving: Houston, Sugar Land, The Woodlands, Pasadena, Galveston, Baytown Headquarters: 1530 E Williams Field Rd, Ste 201, Gilbert, AZ 85295. No office in Houston. --- ## Why Houston work is our work Your app has a launch date and no team to build it, and the version from the pilot slows down once real users and live sensor data arrive. We design and build the iOS, Android and web app and the backend under it as one senior team, working to your date, and keep a record of what each screen showed. In Houston that's a field engineer's tablet on the Ship Channel or a clinician's console in the Texas Medical Center. ## Work a buyer here would recognise Sensor histories and clinical records come from systems that never shared a key, and the pipeline built for Athlinks deals with that shape, stitching more than 400 million athlete records from disparate sources. It runs on Temporal with automated retries and real-time visibility, so a failed step reruns and the run stays observable. ## Two regulators can share one platform Two of Houston's large producers of data answer to different rulebooks. A pipeline operator on the Ship Channel keeps integrity records that PHMSA audits under 49 CFR Parts 192 and 195. A sponsor running trials in the Texas Medical Center keeps electronic records under the FDA's 21 CFR Part 11, with HIPAA over the patient data, and the service firms working for both hold records under each. ## Questions ### We have both energy operations and clinical research. One platform? Yes, and without a fork. Policy is evaluated per action rather than per application, so two regimes with different rules run on the same runtime with different checkpoints enforced. Maintaining two platforms to satisfy two regulators is the expensive way to solve this. ### Do you have an office in Houston? 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. ## 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. ## Working with us from Arizona 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. Most delivery is remote or hybrid. We travel for discovery, workshops and the opening weeks of a build.