StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Home
  2. Companies
  3. iterspace
iterspace

iterspace

iterspace.com

How modern teams share feedback & report bugs in seconds

27tools
2decisions
0followers
OverviewTech Stack27Dev Feed

Tech Stack

View all 27
Stack by Layer
Application & Data14
Utilities3
DevOps5
Business Tools5
Application & Data
14 tools (52%)
Utilities
3 tools (11%)
DevOps
5 tools (19%)
Business Tools
5 tools (19%)

Application & Data

14
JavaScriptReduxReact ReduxAWS AmplifyAWS AppSyncGraphQLAWS Elemental MediaConvertTypeScriptES6HTML5CSS 3Amazon DynamoDBNode.jsAmazon S3

Utilities

3
Amazon API GatewayAmazon SESAmazon SQS

DevOps

5
Azure PipelinesWebpackVisual Studio CodeJiraSentry

Business Tools

5
Azure DevOpsReactstyled-componentsTrelloStorybook

Latest from Engineering

View all
Luca Restagno
Luca Restagno

Co-Founder at iterspace

Jan 30, 2021

DecidedonReactReactStorybookStorybookstyled-componentsstyled-components

Storybook, along with React, styled-components, and Atomic Design, is the perfect tool to boost your front end development productivity. It helps you develop isolated presentational components with a super fast hot reload. It allows to test your props with knobs. Finally you compose, and reuse your components in your app.

You can host your storybook as a static website and share it with the other devs, so they are aware of the components already available in your library, and how to use them.

You can share the same with your UI/UX team, and converge towards a common design system.

You can even run visual regression tests on your library, with storyshots.

Which stack do you use on the Front End?

24.1k views24.1k
Comments
Luca Restagno
Luca Restagno

Co-Founder at iterspace

Jan 30, 2021

ReviewonAWS AppSyncAWS AppSync

I switched from AppSync Resolvers written in VTL to the Lambda Functions invoked from the AppSync Resolver. The decision was made due to higher flexibility, and easier debugging of the Lambda Functions compared to the the VTL code. Moreover, you do not have to learn a new language syntax, and you can still use your preferred language code (python, nodejs and so on). And the most important, you can write tests of your code and run them in your CI pipelines. With this approach, you can delegate the authorization phase to AppSync itself, and leverage the power of the GraphQL schema.

5.21k views5.21k
Comments

Team on StackShare

2
Luca Restagno
Marco Zani