Wie sind die Öffnungszeiten?

Montag 09:00 - 18:00 Dienstag 09:00 - 18:00 Mittwoch 09:00 - 18:00 Donnerstag 09:00 - 18:00 Freitag 09:00 - 18:00

OpenResearch

Name: OpenResearch
Address: Biberstrasse 9/10, Wien, 1010, AT
Telephone: +431253599401

Startseite
österreich
Wien
OpenResearch

We build digital products people love to use. Based in Vienna 🇦🇹, Prishtina 🇽🇰 & Croatia 🇭🇷.

11/08/2026

Cars are becoming computers on wheels. And that creates entirely new challenges.

For over 10 years, we've worked with automotive leaders to build connected vehicle solutions. Here's what we've learned:

🚗 Reliability is non-negotiable
📊 Scale means millions of data points per second
🔐 Security is paramount (vehicles are safety-critical)
⚡ Latency matters for real-time features
🔧 Systems must evolve over decades, not years

Working with companies like Porsche and Volkswagen Group has taught us that automotive-grade software requires a different mindset.

The intersection of automotive and software is one of the most exciting spaces in tech. And we're proud to be part of it.

Are you working on connected mobility solutions?

06/08/2026

Kotlin Multiplatform takes a different approach: share the logic, keep the UI native.

Why KMP is gaining traction:

🔄 Share business logic across Android, iOS, Desktop, Web
📱 Native UI on each platform - no compromise on UX
🛠️ Gradual adoption - start with one shared module
⚡ Native performance - compiles to platform-native code
🧪 Shared tests for shared code

What you typically share:

✅ Networking and API clients
✅ Data models and validation
✅ Business rules and calculations
✅ Local storage and caching
✅ State management

What stays platform-specific:

📱 UI layer - SwiftUI on iOS, Compose on Android
🔧 Platform APIs - camera, sensors, notifications

The sweet spot: teams that know Kotlin and want native UX without duplicating business logic.

JetBrains and Google are investing heavily. The ecosystem is maturing fast.

Have you explored Kotlin Multiplatform?

04/08/2026

The first weeks of a project determine much of its fate.

Rush into coding without proper discovery? You'll pay for it later. That's why we invest heavily in project kickoffs.

Our discovery process:

🎯 Stakeholder alignment sessions
📋 Requirements deep-dive and prioritization
🏗️ Technical architecture decisions
📅 Realistic roadmap creation
🚧 Risk identification and mitigation planning

The goal is clarity. Everyone should know what we're building, why, and how success will be measured.

Yes, this takes time upfront. But it saves exponentially more time during development.

We've seen too many projects fail not because of technical problems, but because expectations weren't aligned from the start.

What's your approach to kicking off new projects?

31/07/2026

New on YouTube 🚨
*Beyond the Apps: Building iOS Experiences with Widgets, Live Activities & App Intents* 📱

Modern iOS apps don't have to stop at the app icon.

In this OpenResearch Mobile Meetup session, Ermal Bujupaj demonstrates how to build seamless experiences that surface your app exactly when users need it - using a real-world EV charging application as an example.

Topics include:
• Interactive Home Screen widgets with WidgetKit
• Live Activities & Lock Screen experiences
• Dynamic Island integration
• Actionable notifications
• App Intents for app-less interactions
• Best practices for combining these technologies in production

If you're building with SwiftUI or looking to make your iOS app more engaging beyond the app itself, this session is full of practical implementation insights.

▶️ Watch the full talk: https://youtu.be/a34OT5XH3dA

What's your favorite iOS feature for creating experiences beyond the app? Let us know in the comments.

30/07/2026

Kafka's basics are straightforward. Its advanced capabilities unlock real power.

Patterns worth mastering:

🔄 Kafka Streams - process events in real-time
📊 Exactly-once semantics - transactions that work
🗂️ Compacted topics - latest state per key
🔗 Kafka Connect - integrate everything
📋 Schema Registry - evolve data safely

Partitioning strategy matters. Key selection determines parallelism and ordering guarantees.

Consumer group rebalancing affects availability. Understand cooperative vs eager rebalancing.

Retention policies need thought. Time-based, size-based, or compaction - each has implications.

Kafka is an event log, not just a queue. That distinction enables event sourcing, replay, and audit trails.

What advanced Kafka patterns do you use?

28/07/2026

Python isn't just for web apps. It's become the lingua franca of data science and automation.

At OpenResearch, we use Python for:

📊 Data analysis and transformation
🤖 Machine learning pipelines
🔧 Automation and scripting
📈 BI and reporting systems
🔗 Glue code between systems

The ecosystem is unmatched. Pandas, NumPy, scikit-learn, TensorFlow - there's a library for almost everything.

Is Python the fastest language? No. Is it the most type-safe? No. But for rapid development and data work, it's hard to beat.

We often use Python alongside our core systems for data science work, reporting, and integrations. Right tool for the right job.

How does Python fit into your tech stack?

23/07/2026

Clicking through cloud consoles doesn't scale. Terraform changes that.

Why Infrastructure as Code matters:

📋 Reproducible environments - dev matches prod
🔄 Version controlled - review changes like code
🔁 Idempotent - apply multiple times safely
📊 State tracking - know what exists
🌍 Multi-cloud - same workflow everywhere

Terraform's declarative approach: describe what you want, let it figure out how.

Modules enable reuse. Remote state enables collaboration. Plan before apply catches mistakes.

The ecosystem is mature. Providers exist for everything. Community modules accelerate common patterns.

Start small. Terraform one resource. Expand as confidence grows.

Infrastructure deserves the same rigor as application code.

How do you manage your infrastructure?

21/07/2026

This year, our team has spoken at conferences about GitOps, connected vehicles, and cloud architecture.

Why do we invest time in speaking?

🎤 Teaching forces deeper understanding
🌐 Connecting with the broader tech community
💡 Sharing what we've learned, and learning from others
🏆 Representing the standards we hold ourselves to

But conferences are just one piece. We also believe in internal knowledge sharing, blog posts, and open source contributions.

The tech industry moves fast. Standing still means falling behind.

We encourage every engineer to find their way of giving back to the community, whether that's speaking, writing, or contributing code.

What's your favorite way to stay current in tech?

16/07/2026

Tests aren't about coverage numbers. They're about confidence to change code.

Testing strategies that actually help:

🔬 Unit tests - fast, isolated, many of them
🔗 Integration tests - verify component interaction
🌐 E2E tests - critical paths only, expensive to maintain
📸 Snapshot tests - catch unintended changes
🔄 Contract tests - verify API compatibility

The testing pyramid matters. Too many E2E tests slow you down. Too few unit tests miss edge cases.

Test behavior, not implementation. Tests that break on refactoring are tests that slow you down.

Make tests fast. Slow tests don't get run.

Write the test first sometimes. TDD isn't dogma, but it clarifies thinking.

What's your testing strategy?

Adresse

Biberstrasse 9/10
Wien
1010

Öffnungszeiten

Montag	09:00 - 18:00
Dienstag	09:00 - 18:00
Mittwoch	09:00 - 18:00
Donnerstag	09:00 - 18:00
Freitag	09:00 - 18:00

Telefon

+431253599401

Webseite

http://www.openresearch.com/

Benachrichtigungen

Lassen Sie sich von uns eine E-Mail senden und seien Sie der erste der Neuigkeiten und Aktionen von OpenResearch erfährt. Ihre E-Mail-Adresse wird nicht für andere Zwecke verwendet und Sie können sich jederzeit abmelden.