Installation & Setup

This guide will walk you through the process of setting up Aperture, including account creation, application configuration, and deployment preparation.

Why Use Aperture?

• Eliminate App Store Wait Times: Deploy web updates without submitting new native app versions for review
• Targeted Releases: Test features with specific user groups before full rollout
• Consistent Cross-Platform Experience: Maintain feature parity across iOS and Android
• Reduced Development Costs: Leverage your web team’s skills for mobile experiences
• Rapid Iteration: Fix bugs and release improvements with web-speed agility

Setting Up Your Aperture Environment

Follow these steps to create your account and set up your organization in Aperture.

Step 1: Create your account

1. Visit https://aperture.triptech.dev/signup
2. Enter your email, name, and password
3. Verify your email address by clicking the link sent to your inbox

Your Aperture account is the gateway to managing deployments across all your applications and teams. The email you use will receive deployment notifications and alerts.

Step 2: Create your organization

1. Name your organization (typically your company name)
2. Add a brief description
3. Select your primary development region

Organizations in Aperture serve as containers for all your apps, team members, and deployment configurations. Proper naming and structuring simplify management as you scale.

Setting Up Your Web Application

Prepare and configure your web application for deployment through Aperture.

Step 1: Prepare your web application

Ensure your web application meets these requirements:

• Has a clean build process that outputs to a specific directory
• Works properly when hosted on a CDN or static hosting
• Has responsive design for mobile devices

A well-structured build process ensures smooth deployments with predictable results. Aperture works best with standard web applications that use HTML, CSS, and JavaScript and can be built to static assets.

Step 2: Create a new web application in Aperture

1. Navigate to: Your organization → Web Applications → New Web Application
2. Complete the following information:
   • Name: A descriptive name for your application
   • Repository URL: Where your code is hosted
   • Build command: The command that builds your app (e.g., npm run build)
   • Output directory: Where build artifacts are located (e.g., dist or build)
   • Framework: Select your web framework

Step 3: Configure your first build

1. Navigate to: Your web application → Builds → New Build
2. Select:
   • Branch or commit to build from
   • Environment variables (if needed)
   • Build configuration options

Builds in Aperture represent specific versions of your application. Creating explicit builds allows you to test different versions, roll back if needed, and maintain a history of what was deployed when.

Setting Up Your Native Application

Prepare and register your native applications to receive web content.

Step 1: Prepare your native application

Before configuring in Aperture, ensure your native iOS/Android app:

• Has the Aperture SDK integrated
• Has proper permissions for network requests
• Is configured to receive web content

Step 2: Register your native application

1. Navigate to: Your organization → Native Applications → New Native Application
2. Complete the following information:
   • Name: A descriptive name
   • Platform: iOS, Android, or both
   • Bundle ID/Package Name: Your app’s unique identifier
   • Version requirements: Minimum OS version supported
   • SDK version: The version of Aperture SDK integrated

This configuration links your Aperture account with your actual apps in the app stores. The correct bundle ID/package name is crucial for targeting the right applications.

Understanding Deployment Strategies

Before deploying, familiarize yourself with available strategies:

Progressive Rollout

Release to a percentage of users, gradually increasing over time

Available in All Plans

Cohort-based

Target specific user segments based on behavior or characteristics

Available in Pro & Enterprise Plans

Device-based

Target specific device types, OS versions, or hardware capabilities

Available in Pro & Enterprise Plans

Practical How-To Example: Safe Progressive Rollout

For critical updates where stability is paramount:

1. Create a new deployment with Progressive strategy
2. Set initial rollout to 5% of users
3. Configure a 4-hour observation period
4. Set automatic progression to 20% if no errors detected
5. Configure another 8-hour observation period
6. Set final progression to 100% if all remains stable
7. Configure automatic rollback if error rate exceeds 1%

This approach minimizes risk by exposing new code to a small percentage of users initially, allowing you to catch issues before they affect your entire user base.

Common Questions and Troubleshooting

How do I know if my web app is compatible with Aperture?

Aperture works best with standard web applications that:

• Use standard HTML, CSS, and JavaScript
• Don’t rely on server-side rendering for core functionality
• Have responsive design for mobile screens
• Can be built to static assets

How long should I wait between deployment phases?

This depends on your application and user base, but generally:

• Critical applications: 24-48 hours between significant percentage increases
• Less critical applications: 4-8 hours may be sufficient
• Consider your usage patterns—ensure you cover peak usage times before expanding

What metrics should I monitor during deployment?

Key metrics to watch include:

• Error rates (JavaScript errors, API failures)
• Performance metrics (load time, interaction time)
• User engagement (session duration, feature usage)
• Crash reports from native application

Getting Help and Support

• Documentation: docs.aperture.triptech.dev
• Support Email: [email protected]
• Community Forum: community.aperture.triptech.dev
• Office Hours: Join our weekly developer office hours (Pro/Enterprise)
• Dedicated Support: Contact your account manager (Enterprise)