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 🇭🇷.

29/10/2026

Feature flags separate deployment from release. That distinction changes everything.

What feature flags enable:

🚀 Deploy anytime - code is there, but not active
🧪 Gradual rollouts - 1%, 10%, 50%, 100%
🔄 A/B testing - compare variants
🔒 Kill switches - disable features instantly
👥 User targeting - beta users see new features first

Implementation options:

📦 LaunchDarkly, Split.io - managed services
🔧 Unleash, Flagsmith - self-hosted open source
🏠 DIY - database or config based

Flags add complexity. Clean up old flags regularly. Dead flags confuse developers.

Testing with flags requires thought. Test all paths. Feature matrix can explode.

The ability to turn off a feature in production is invaluable during incidents.

How do you use feature flags?

27/10/2026

Building an MVP is one thing. Scaling it to thousands of users is another.

We've helped startups grow from "it works on my laptop" to "it handles millions of requests."

The scaling journey typically includes:

📊 Identifying bottlenecks before they hurt
🏗️ Refactoring for horizontal scaling
💾 Database optimization and sometimes redesign
📦 Caching layers where they matter
⚡ CDNs for static content
🔄 Moving to async processing for heavy tasks

The key is doing this incrementally. You don't need Google-scale architecture for 1,000 users. But you need to know when to evolve.

Each growth phase has its own challenges. We help navigate them.

Where is your product on the growth curve?

22/10/2026

Technical debt isn't bad. Unmanaged technical debt is.

Types of technical debt:

🏃 Deliberate - ship now, clean up later (and actually do it)
😅 Accidental - we didn't know better at the time
🔧 Bit rot - external changes make old code obsolete
📋 Outdated dependencies - security and compatibility risks

Managing debt effectively:

📊 Make it visible - track like any other work
⏰ Budget time - 20% for maintenance isn't unreasonable
🎯 Prioritize by impact - not all debt is equal
🔄 Refactor continuously - small improvements compound

Debt-free codebases don't exist. The goal is manageable debt levels.

The best time to address debt is during related feature work. Context is fresh. Changes are natural.

Ignoring debt doesn't make it disappear.

How does your team handle technical debt?

20/10/2026

We've been distributed since before it was trendy. Here's what 10 years taught us:

🎥 Video on for meetings: faces matter
📝 Write it down: async communication is inclusive
⏰ Core hours overlap: for when sync matters
🎉 In-person gatherings: can't fully replace, but can be intentional
🤝 Trust by default: micromanagement kills remote work

Remote doesn't mean isolated. It means intentionally connected.

We hire the best talent regardless of location. We meet in person when it matters. And we've built systems to keep everyone aligned and engaged.

The result? A team that's been together for years, building great software across borders.

What's the biggest challenge your distributed team faces?

15/10/2026

Performance optimization starts with measurement. Guessing wastes time.

Optimization patterns that work:

📊 Profile first - find actual bottlenecks
🗄️ Caching - the fastest query is one you don't make
📦 Lazy loading - defer what isn't immediately needed
🔄 Connection pooling - reuse expensive connections
📋 Pagination - don't load everything at once
🗜️ Compression - smaller payloads travel faster

Database queries are often the bottleneck. Check ex*****on plans. Add indexes thoughtfully.

Frontend performance matters too. Bundle size, render blocking, layout thrashing - all measurable, all fixable.

Set performance budgets. Measure against them in CI. Catch regressions before production.

Premature optimization is still a problem. Optimize when it matters, not everywhere.

What's your performance optimization approach?

13/10/2026

Java isn't flashy. It doesn't have the hype of newer languages. And that's exactly why it's still everywhere.

For enterprise systems that need to run for years, Java delivers:

☕ Massive ecosystem of battle-tested libraries
🏢 Talent pool that's deep and available
🔧 Tooling that's mature and powerful
📈 Performance that keeps improving (GraalVM, anyone?)
🛡️ Backward compatibility that respects investments

We use Java for backends that power critical business processes. When stability and maintainability matter more than excitement, Java is hard to beat.

It's not about old vs. new. It's about right tool for the job.

Is Java part of your tech stack?

12/10/2026

🚀 A milestone worth celebrating at OpenResearch!

We’re proud to announce that we’ve successfully achieved SIL 1 certification for a mobile application running on both iOS and Android!

Bringing functional safety requirements to mobile platforms is no small feat. It takes rigorous engineering, thorough testing, extensive documentation, and a strong commitment to quality.

This achievement demonstrates that modern mobile technology and demanding safety requirements can go hand in hand.

A big thank you to everyone involved for their dedication, expertise, and persistence throughout the process.

At OpenResearch, we love tackling complex engineering challenges - and this is one we're particularly proud of.

08/10/2026

GraphQL isn't REST's replacement. It's a different tool for different problems.

When GraphQL helps:

✅ Multiple clients need different data shapes
✅ Over-fetching is a real problem
✅ Rapid frontend iteration matters
✅ Strong typing benefits your workflow
✅ Real-time subscriptions are needed

When REST is fine:

✅ Simple CRUD operations
✅ Caching is critical (HTTP caching is simpler with REST)
✅ Team knows REST well
✅ Simple client needs

GraphQL complexity is real. N+1 queries, authorization per field, caching strategies - all need attention.

Tools like Apollo, Hasura, and Relay smooth the path. But understand the fundamentals first.

GraphQL is a powerful option, not a universal answer.

What's your API style preference?

06/10/2026

Three months left.

What will you accomplish? What will you ship? What will you learn?

Q4 is tricky. The holidays are coming, but so are year-end deadlines. Success requires intentional planning.

Our Q4 playbook:

📅 Front-load critical work before December holidays
🎯 Prioritize ruthlessly: not everything will ship
👥 Account for vacation and reduced capacity
📊 Set realistic milestones, not hopeful ones
🔒 Lock scope for anything that must ship this year

We've seen too many teams overpromise in October and scramble in December. Better to commit to less and deliver more.

What's your team's most important Q4 goal?

01/10/2026

As Angular apps grow, state management becomes critical.

Options for managing state:

📦 Services with BehaviorSubjects - simple, often enough
🔄 NgRx - Redux pattern, predictable but verbose
📊 NGXS - less boilerplate than NgRx
🎯 Signals - Angular's new reactive primitive
🔧 Component state - local when possible

NgRx shines when:

✅ State is shared across many components
✅ Complex async operations need coordination
✅ Time-travel debugging helps
✅ Team benefits from enforced patterns

NgRx is overkill when:

❌ State is mostly local
❌ Simple service injection works fine
❌ Team doesn't need the structure

Start simple. Add state management when pain emerges.

How do you manage state in Angular?

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

Website

http://www.openresearch.com/

Benachrichtigungen

Erfahren Sie als Erste/r von Neuigkeiten und Aktionen: Wir schicken Ihnen eine E-Mail, wenn OpenResearch etwas veröffentlicht. Ihre E-Mail-Adresse wird für keinen anderen Zweck verwendet, und Sie können sich jederzeit abmelden.