url stringlengths 11 2.25k | text stringlengths 88 50k | ts timestamp[s]date 2026-01-13 08:47:33 2026-01-13 09:30:40 |
|---|---|---|
https://docs.devcycle.com/integrations/rollbar/ | Rollbar | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up On this page Rollbar Rollbar is a tool used for error logging and real-time performance tracking for your applications. Rollbar provides you with the ability to capture detailed information on errors to help diagnose and resolve issues faster. Enrich your logs further by including DevCycle Feature data into your error logging. The DevCycle Rollbar integration enhances error tracking by adding feature configuration data directly to your Rollbar error logs. By sending DevCycle Feature and Variable data from the DevCycle SDKs to Rollbar, developers can gain valuable insights into the specific feature configuration that was delivered to a user during an error. Configuration Including DevCycle Features in your Rollbar Config Include DevCycle Feature data to the initialization of Rollbar to allow all Rollbar errors to be populated with the specific DevCycle feature configuration at that time of the error. The exact DevCycle data and format that you pass to Rollbar can be easily configured, so feel free to experiment with the data that's available on your SDK. In our example below, we supply all Features and Variables that the user/device received to the Rollbar config. Steps : Get all Features and/or all Variables from the DevCycle SDK. Create a custom field called devCycleSettings within your Rollbar config payload. Add your Features and Variables to the devCycleSettings object. import { Provider , useRollbar } from '@rollbar / react import { useDevCycleClient , useIsDevCycleInitialized , useVariableValue , withDevCycleProvider } from '@devcycle/react-client-sdk' ... function MyComponent ( ) { const devCycleClient = useDevCycleClient ( ) const devCycleFeatures = devCycleClient . allFeatures ( ) const devCycleVariables = devCycleClient . allVariables ( ) const rollbarConfig = { accessToken : 'YOUR_ROLLBAR_CLIENT_ACCESS_TOKEN' , captureUncaught : true , captureUnhandledRejections : true , environment : 'production' , payload : { custom : { devCycleSettings : { features : devCycleFeatures , // this will send all DevCycle features in the error payload to Rollbar variables : devCycleVariables // this will send all DevCycle variables in the error payload to Rollbar } } } } return ( < Provider config = { rollbarConfig } > < TestError /> </ Provider > } function App ( ) { const devcycleReady = useIsDevCycleInitialized ( ) if ( ! devcycleReady ) return < div > < h1 > DevCycle is not ready! Loading State... </ h1 > </ div > return ( < > < div > < Router > < Routes > < Route path = " / " element = { < MyComponent /> } /> </ Routes > </ Router > </ div > </ > ) } export default withDevCycleProvider ( { sdkKey : 'YOUR_DEVCYCLE_SDK_KEY' , user : { user_id : 'USER_ID' , isAnonymous : false } } ) ( App ) Including DevCycle Features on Specific Errors Rollbar allows you to define extra properties for an error. Instead of providing all Feature data on initialization, you may want to supply DevCycle Feature data to specific errors of you choice. In our example below, we're using DevCycle to determine whether a user should receive a new Feature with new behavior or the existing old behavior. If there is an error running any of those behaviors, we're logging an error to Rollbar and supplying all DevCycle Features to the error as an extra property. Steps : Get all Features and/or all Variables from the DevCycle SDK. In your rollbar.error properties, add a custom field (ex: devCycleFeature ) containing your Feature or Variable data. Example: const rollbar = useRollbar ( ) ; const variableValue = useVariableValue ( 'variable_key' , false ) try { if ( variableValue ) { testNewBehavior ( ) } else { oldBehavior ( ) } } catch ( error ) { if ( variableValue ) { const devcycleClient = useDevCycleClient ( ) const features = devcycleClient . allFeatures ( ) rollbar . error ( error , { devCycleFeature : { name : 'New Feature' , id : features [ 'feature-key' ] [ '_id' ] } } ) } } Service Links Rollbar service links allow you to create links that connect directly with DevCycle, to provide easy access to Features and Variables from the Rollbar interface. To learn how to create service links for DevCycle, visit the Rollbar docs here . Edit this page Last updated on Jan 9, 2026 Configuration Including DevCycle Features in your Rollbar Config Including DevCycle Features on Specific Errors Service Links DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:25 |
https://socket.io/docs/v4/migrating-from-2-x-to-3-0/ | Migrating from 2.x to 3.0 | Socket.IO Skip to main content Latest blog post (July 25, 2024): npm package provenance . Socket.IO Docs Guide Tutorial Examples Emit cheatsheet Server API Client API Ecosystem Help Troubleshooting Stack Overflow GitHub Discussions Slack News Blog Twitter Tools CDN Admin UI About FAQ Changelog Roadmap Become a sponsor 4.x 4.x 3.x 2.x Changelog English English Español Français Português (Brasil) 中文（中国） Search Socket.IO Documentation Server Client Events Adapters Advanced Migrations Migrating from 2.x to 3.0 Migrating from 3.x to 4.0 Miscellaneous Migrations Migrating from 2.x to 3.0 Version: 4.x On this page Migrating from 2.x to 3.0 This release should fix most of the inconsistencies of the Socket.IO library and provide a more intuitive behavior for the end users. It is the result of the feedback of the community over the years. A big thanks to everyone involved! TL;DR: due to several breaking changes, a v2 client will not be able to connect to a v3 server (and vice versa) Update: As of Socket.IO 3.1.0 , the v3 server is now able to communicate with v2 clients. More information below . A v3 client is still not be able to connect to a v2 server though. For the low-level details, please see: Engine.IO protocol v4 Socket.IO protocol v5 Here is the complete list of changes: Configuration Saner default values CORS handling No more cookie by default API change io.set() is removed No more implicit connection to the default namespace Namespace.connected is renamed to Namespace.sockets and is now a Map Socket.rooms is now a Set Socket.binary() is removed Socket.join() and Socket.leave() are now synchronous Socket.use() is removed A middleware error will now emit an Error object Add a clear distinction between the Manager query option and the Socket query option The Socket instance will no longer forward the events emitted by its Manager Namespace.clients() is renamed to Namespace.allSockets() and now returns a Promise Client bundles No more "pong" event for retrieving latency ES modules syntax emit() chains are not possible anymore Room names are not coerced to string anymore New features Catch-all listeners Volatile events (client) Official bundle with the msgpack parser Miscellaneous The Socket.IO codebase has been rewritten to TypeScript Support for IE8 and Node.js 8 is officially dropped How to upgrade an existing production deployment Known migration issues Configuration Saner default values the default value of maxHttpBufferSize was decreased from 100MB to 1MB . the WebSocket permessage-deflate extension is now disabled by default you must now explicitly list the domains that are allowed (for CORS, see below ) the withCredentials option now defaults to false on the client side CORS handling In v2, the Socket.IO server automatically added the necessary headers to allow Cross-Origin Resource Sharing (CORS). This behavior, while convenient, was not great in terms of security, because it meant that all domains were allowed to reach your Socket.IO server, unless otherwise specified with the origins option. That's why, as of Socket.IO v3: CORS is now disabled by default the origins option (used to provide a list of authorized domains) and the handlePreflightRequest option (used to edit the Access-Control-Allow-xxx headers) are replaced by the cors option, which will be forwarded to the cors package. The complete list of options can be found here . Before: const io = require ( "socket.io" ) ( httpServer , { origins : [ "https://example.com" ] , // optional, useful for custom headers handlePreflightRequest : ( req , res ) => { res . writeHead ( 200 , { "Access-Control-Allow-Origin" : "https://example.com" , "Access-Control-Allow-Methods" : "GET,POST" , "Access-Control-Allow-Headers" : "my-custom-header" , "Access-Control-Allow-Credentials" : true } ) ; res . end ( ) ; } } ) ; After: const io = require ( "socket.io" ) ( httpServer , { cors : { origin : "https://example.com" , methods : [ "GET" , "POST" ] , allowedHeaders : [ "my-custom-header" ] , credentials : true } } ) ; No more cookie by default In previous versions, an io cookie was sent by default. This cookie can be used to enable sticky-session, which is still required when you have several servers and HTTP long-polling enabled (more information here ). However, this cookie is not needed in some cases (i.e. single server deployment, sticky-session based on IP) so it must now be explicitly enabled. Before: const io = require ( "socket.io" ) ( httpServer , { cookieName : "io" , cookieHttpOnly : false , cookiePath : "/custom" } ) ; After: const io = require ( "socket.io" ) ( httpServer , { cookie : { name : "test" , httpOnly : false , path : "/custom" } } ) ; All other options (domain, maxAge, sameSite, ...) are now supported. Please see here for the complete list of options. API change Below are listed the non backward-compatible changes. io.set() is removed This method was deprecated in the 1.0 release and kept for backward-compatibility. It is now removed. It was replaced by middlewares. Before: io . set ( "authorization" , ( handshakeData , callback ) => { // make sure the handshake data looks good callback ( null , true ) ; // error first, "authorized" boolean second } ) ; After: io . use ( ( socket , next ) => { var handshakeData = socket . request ; // make sure the handshake data looks good as before // if error do this: // next(new Error("not authorized")); // else just call next next ( ) ; } ) ; No more implicit connection to the default namespace This change impacts the users of the multiplexing feature (what we call Namespace in Socket.IO). In previous versions, a client would always connect to the default namespace ( / ), even if it requested access to another namespace. This meant that the middlewares registered for the default namespace were triggered, which may be quite surprising. // client-side const socket = io ( "/admin" ) ; // server-side io . use ( ( socket , next ) => { // not triggered anymore } ) ; io . on ( "connection" , socket => { // not triggered anymore } ) io . of ( "/admin" ) . use ( ( socket , next ) => { // triggered } ) ; Besides, we will now refer to the "main" namespace instead of the "default" namespace. Namespace.connected is renamed to Namespace.sockets and is now a Map The connected object (used to store all the Socket connected to the given Namespace) could be used to retrieve a Socket object from its id. It is now an ES6 Map . Before: // get a socket by ID in the main namespace const socket = io . of ( "/" ) . connected [ socketId ] ; // get a socket by ID in the "admin" namespace const socket = io . of ( "/admin" ) . connected [ socketId ] ; // loop through all sockets const sockets = io . of ( "/" ) . connected ; for ( const id in sockets ) { if ( sockets . hasOwnProperty ( id ) ) { const socket = sockets [ id ] ; // ... } } // get the number of connected sockets const count = Object . keys ( io . of ( "/" ) . connected ) . length ; After: // get a socket by ID in the main namespace const socket = io . of ( "/" ) . sockets . get ( socketId ) ; // get a socket by ID in the "admin" namespace const socket = io . of ( "/admin" ) . sockets . get ( socketId ) ; // loop through all sockets for ( const [ _ , socket ] of io . of ( "/" ) . sockets ) { // ... } // get the number of connected sockets const count = io . of ( "/" ) . sockets . size ; Socket.rooms is now a Set The rooms property contains the list of rooms the Socket is currently in. It was an object, it is now an ES6 Set . Before: io . on ( "connection" , ( socket ) => { console . log ( Object . keys ( socket . rooms ) ) ; // [ <socket.id> ] socket . join ( "room1" ) ; console . log ( Object . keys ( socket . rooms ) ) ; // [ <socket.id>, "room1" ] } ) ; After: io . on ( "connection" , ( socket ) => { console . log ( socket . rooms ) ; // Set { <socket.id> } socket . join ( "room1" ) ; console . log ( socket . rooms ) ; // Set { <socket.id>, "room1" } } ) ; Socket.binary() is removed The binary method could be used to indicate that a given event did not contain any binary data (in order to skip the lookup done by the library and improve performance in certain conditions). It was replaced by the ability to provide your own parser, which was added in Socket.IO 2.0. Before: socket . binary ( false ) . emit ( "hello" , "no binary" ) ; After: const io = require ( "socket.io" ) ( httpServer , { parser : myCustomParser } ) ; Please see socket.io-msgpack-parser for example. Socket.join() and Socket.leave() are now synchronous The asynchronicity was needed for the first versions of the Redis adapter, but this is not the case anymore. For reference, an Adapter is an object that stores the relationships between Sockets and Rooms . There are two official adapters: the in-memory adapter (built-in) and the Redis adapter based on Redis pub-sub mechanism . Before: socket . join ( "room1" , ( ) => { io . to ( "room1" ) . emit ( "hello" ) ; } ) ; socket . leave ( "room2" , ( ) => { io . to ( "room2" ) . emit ( "bye" ) ; } ) ; After: socket . join ( "room1" ) ; io . to ( "room1" ) . emit ( "hello" ) ; socket . leave ( "room2" ) ; io . to ( "room2" ) . emit ( "bye" ) ; Note: custom adapters may return a Promise, so the previous example becomes: await socket . join ( "room1" ) ; io . to ( "room1" ) . emit ( "hello" ) ; Socket.use() is removed socket.use() could be used as a catch-all listener. But its API was not really intuitive. It is replaced by socket.onAny() . UPDATE : the Socket.use() method was restored in socket.io@3.0.5 . Before: socket . use ( ( packet , next ) => { console . log ( packet . data ) ; next ( ) ; } ) ; After: socket . onAny ( ( event , ... args ) => { console . log ( event ) ; } ) ; A middleware error will now emit an Error object The error event is renamed to connect_error and the object emitted is now an actual Error: Before: // server-side io . use ( ( socket , next ) => { next ( new Error ( "not authorized" ) ) ; } ) ; // client-side socket . on ( "error" , err => { console . log ( err ) ; // not authorized } ) ; // or with an object // server-side io . use ( ( socket , next ) => { const err = new Error ( "not authorized" ) ; err . data = { content : "Please retry later" } ; // additional details next ( err ) ; } ) ; // client-side socket . on ( "error" , err => { console . log ( err ) ; // { content: "Please retry later" } } ) ; After: // server-side io . use ( ( socket , next ) => { const err = new Error ( "not authorized" ) ; err . data = { content : "Please retry later" } ; // additional details next ( err ) ; } ) ; // client-side socket . on ( "connect_error" , err => { console . log ( err instanceof Error ) ; // true console . log ( err . message ) ; // not authorized console . log ( err . data ) ; // { content: "Please retry later" } } ) ; Add a clear distinction between the Manager query option and the Socket query option In previous versions, the query option was used in two distinct places: in the query parameters of the HTTP requests ( GET /socket.io/?EIO=3&abc=def ) in the CONNECT packet Let's take the following example: const socket = io ( { query : { token : "abc" } } ) ; Under the hood, here's what happened in the io() method: const { Manager } = require ( "socket.io-client" ) ; // a new Manager is created (which will manage the low-level connection) const manager = new Manager ( { query : { // sent in the query parameters token : "abc" } } ) ; // and then a Socket instance is created for the namespace (here, the main namespace, "/") const socket = manager . socket ( "/" , { query : { // sent in the CONNECT packet token : "abc" } } ) ; This behavior could lead to weird behaviors, for example when the Manager was reused for another namespace (multiplexing): // client-side const socket1 = io ( { query : { token : "abc" } } ) ; const socket2 = io ( "/my-namespace" , { query : { token : "def" } } ) ; // server-side io . on ( "connection" , ( socket ) => { console . log ( socket . handshake . query . token ) ; // abc (ok!) } ) ; io . of ( "/my-namespace" ) . on ( "connection" , ( socket ) => { console . log ( socket . handshake . query . token ) ; // abc (what?) } ) ; That's why the query option of the Socket instance is renamed to auth in Socket.IO v3: // plain object const socket = io ( { auth : { token : "abc" } } ) ; // or with a function const socket = io ( { auth : ( cb ) => { cb ( { token : "abc" } ) ; } } ) ; // server-side io . on ( "connection" , ( socket ) => { console . log ( socket . handshake . auth . token ) ; // abc } ) ; Note: the query option of the Manager can still be used in order to add a specific query parameter to the HTTP requests. The Socket instance will no longer forward the events emitted by its Manager In previous versions, the Socket instance emitted the events related to the state of the underlying connection. This will not be the case anymore. You can still have access to those events on the Manager instance (the io property of the socket) : Before: socket . on ( "reconnect_attempt" , ( ) => { } ) ; After: socket . io . on ( "reconnect_attempt" , ( ) => { } ) ; Here is the updated list of events emitted by the Manager: Name Description Previously (if different) open successful (re)connection - error (re)connection failure or error after a successful connection connect_error close disconnection - ping ping packet - packet data packet - reconnect_attempt reconnection attempt reconnect_attempt & reconnecting reconnect successful reconnection - reconnect_error reconnection failure - reconnect_failed reconnection failure after all attempts - Here is the updated list of events emitted by the Socket: Name Description Previously (if different) connect successful connection to a Namespace - connect_error connection failure error disconnect disconnection - And finally, here's the updated list of reserved events that you cannot use in your application: connect (used on the client-side) connect_error (used on the client-side) disconnect (used on both sides) disconnecting (used on the server-side) newListener and removeListener (EventEmitter reserved events ) socket . emit ( "connect_error" ) ; // will now throw an Error Namespace.clients() is renamed to Namespace.allSockets() and now returns a Promise This function returns the list of socket IDs that are connected to this namespace. Before: // all sockets in default namespace io . clients ( ( error , clients ) => { console . log ( clients ) ; // => [6em3d4TJP8Et9EMNAAAA, G5p55dHhGgUnLUctAAAB] } ) ; // all sockets in the "chat" namespace io . of ( "/chat" ) . clients ( ( error , clients ) => { console . log ( clients ) ; // => [PZDoMHjiu8PYfRiKAAAF, Anw2LatarvGVVXEIAAAD] } ) ; // all sockets in the "chat" namespace and in the "general" room io . of ( "/chat" ) . in ( "general" ) . clients ( ( error , clients ) => { console . log ( clients ) ; // => [Anw2LatarvGVVXEIAAAD] } ) ; After: // all sockets in default namespace const ids = await io . allSockets ( ) ; // all sockets in the "chat" namespace const ids = await io . of ( "/chat" ) . allSockets ( ) ; // all sockets in the "chat" namespace and in the "general" room const ids = await io . of ( "/chat" ) . in ( "general" ) . allSockets ( ) ; Note: this function was (and still is) supported by the Redis adapter, which means that it will return the list of socket IDs across all the Socket.IO servers. Client bundles There are now 3 distinct bundles: Name Size Description socket.io.js 34.7 kB gzip Unminified version, with debug socket.io.min.js 14.7 kB min+gzip Production version, without debug socket.io.msgpack.min.js 15.3 kB min+gzip Production version, without debug and with the msgpack parser By default, all of them are served by the server, at /socket.io/<name> . Before: <!-- note: this bundle was actually minified but included the debug package --> < script src = " /socket.io/socket.io.js " > </ script > After: <!-- during development --> < script src = " /socket.io/socket.io.js " > </ script > <!-- for production --> < script src = " /socket.io/socket.io.min.js " > </ script > No more "pong" event for retrieving latency In Socket.IO v2, you could listen to the pong event on the client-side, which included the duration of the last health check round-trip. Due to the reversal of the heartbeat mechanism (more information here ), this event has been removed. Before: socket . on ( "pong" , ( latency ) => { console . log ( latency ) ; } ) ; After: // server-side io . on ( "connection" , ( socket ) => { socket . on ( "ping" , ( cb ) => { if ( typeof cb === "function" ) cb ( ) ; } ) ; } ) ; // client-side setInterval ( ( ) => { const start = Date . now ( ) ; // volatile, so the packet will be discarded if the socket is not connected socket . volatile . emit ( "ping" , ( ) => { const latency = Date . now ( ) - start ; // ... } ) ; } , 5000 ) ; ES modules syntax The ECMAScript modules syntax is now similar to the Typescript one (see below ). Before (using default import): // server-side import Server from "socket.io" ; const io = new Server ( 8080 ) ; // client-side import io from 'socket.io-client' ; const socket = io ( ) ; After (with named import): // server-side import { Server } from "socket.io" ; const io = new Server ( 8080 ) ; // client-side import { io } from 'socket.io-client' ; const socket = io ( ) ; emit() chains are not possible anymore The emit() method now matches the EventEmitter.emit() method signature, and returns true instead of the current object. Before: socket . emit ( "event1" ) . emit ( "event2" ) ; After: socket . emit ( "event1" ) ; socket . emit ( "event2" ) ; Room names are not coerced to string anymore We are now using Maps and Sets internally instead of plain objects, so the room names are not implicitly coerced to string anymore. Before: // mixed types were possible socket . join ( 42 ) ; io . to ( "42" ) . emit ( "hello" ) ; // also worked socket . join ( "42" ) ; io . to ( 42 ) . emit ( "hello" ) ; After: // one way socket . join ( "42" ) ; io . to ( "42" ) . emit ( "hello" ) ; // or another socket . join ( 42 ) ; io . to ( 42 ) . emit ( "hello" ) ; New features Some of those new features may be backported to the 2.4.x branch, depending on the feedback of the users. Catch-all listeners This feature is inspired from the EventEmitter2 library (which is not used directly in order not to increase the browser bundle size). It is available for both the server and the client sides: // server io . on ( "connection" , ( socket ) => { socket . onAny ( ( event , ... args ) => { } ) ; socket . prependAny ( ( event , ... args ) => { } ) ; socket . offAny ( ) ; // remove all listeners socket . offAny ( listener ) ; const listeners = socket . listenersAny ( ) ; } ) ; // client const socket = io ( ) ; socket . onAny ( ( event , ... args ) => { } ) ; socket . prependAny ( ( event , ... args ) => { } ) ; socket . offAny ( ) ; // remove all listeners socket . offAny ( listener ) ; const listeners = socket . listenersAny ( ) ; Volatile events (client) A volatile event is an event that is allowed to be dropped if the low-level transport is not ready yet (for example when an HTTP POST request is already pending). This feature was already available on the server-side. It might be useful on the client-side as well, for example when the socket is not connected (by default, packets are buffered until reconnection). socket . volatile . emit ( "volatile event" , "might or might not be sent" ) ; Official bundle with the msgpack parser A bundle with the socket.io-msgpack-parser will now be provided (either on the CDN or served by the server at /socket.io/socket.io.msgpack.min.js ). Pros: events with binary content are sent as 1 WebSocket frame (instead of 2+ with the default parser) payloads with lots of numbers should be smaller Cons: no IE9 support ( https://caniuse.com/mdn-javascript_builtins_arraybuffer ) a slightly bigger bundle size // server-side const io = require ( "socket.io" ) ( httpServer , { parser : require ( "socket.io-msgpack-parser" ) } ) ; No additional configuration is needed on the client-side. Miscellaneous The Socket.IO codebase has been rewritten to TypeScript Which means npm i -D @types/socket.io should not be needed anymore. Server: import { Server , Socket } from "socket.io" ; const io = new Server ( 8080 ) ; io . on ( "connection" , ( socket : Socket ) => { console . log ( ` connect ${ socket . id } ` ) ; socket . on ( "disconnect" , ( ) => { console . log ( ` disconnect ${ socket . id } ` ) ; } ) ; } ) ; Client: import { io } from "socket.io-client" ; const socket = io ( "/" ) ; socket . on ( "connect" , ( ) => { console . log ( ` connect ${ socket . id } ` ) ; } ) ; Plain javascript is obviously still fully supported. Support for IE8 and Node.js 8 is officially dropped IE8 is no longer testable on the Sauce Labs platform, and requires a lot of efforts for very few users (if any?), so we are dropping support for it. Besides, Node.js 8 is now EOL . Please upgrade as soon as possible! How to upgrade an existing production deployment first, update the servers with allowEIO3 set to true (added in socket.io@3.1.0 ) const io = require ( "socket.io" ) ( { allowEIO3 : true // false by default } ) ; Note: If you are using the Redis adapter to broadcast packets between nodes , you must use socket.io-redis@5 with socket.io@2 and socket.io-redis@6 with socket.io@3 . Please note that both versions are compatible, so you can update each server one by one (no big bang is needed). then, update the clients This step may actually take some time, as some clients may still have a v2 client in cache. You can check the version of the connection with: io . on ( "connection" , ( socket ) => { const version = socket . conn . protocol ; // either 3 or 4 } ) ; This matches the value of the EIO query parameter in the HTTP requests. and finally, once every client was updated, set allowEIO3 to false (which is the default value) const io = require ( "socket.io" ) ( { allowEIO3 : false } ) ; With allowEIO3 set to false , v2 clients will now receive an HTTP 400 error ( Unsupported protocol version ) when connecting. Known migration issues stream_1.pipeline is not a function TypeError: stream_1.pipeline is not a function at Function.sendFile (.../node_modules/socket.io/dist/index.js:249:26) at Server.serve (.../node_modules/socket.io/dist/index.js:225:16) at Server.srv.on (.../node_modules/socket.io/dist/index.js:186:22) at emitTwo (events.js:126:13) at Server.emit (events.js:214:7) at parserOnIncoming (_http_server.js:602:12) at HTTPParser.parserOnHeadersComplete (_http_common.js:116:23) This error is probably due to your version of Node.js. The pipeline method was introduced in Node.js 10.0.0. error TS2416: Property 'emit' in type 'Namespace' is not assignable to the same property in base type 'EventEmitter'. node_modules/socket.io/dist/namespace.d.ts(89,5): error TS2416: Property 'emit' in type 'Namespace' is not assignable to the same property in base type 'EventEmitter'. Type '(ev: string, ...args: any[]) => Namespace' is not assignable to type '(event: string | symbol, ...args: any[]) => boolean'. Type 'Namespace' is not assignable to type 'boolean'. node_modules/socket.io/dist/socket.d.ts(84,5): error TS2416: Property 'emit' in type 'Socket' is not assignable to the same property in base type 'EventEmitter'. Type '(ev: string, ...args: any[]) => this' is not assignable to type '(event: string | symbol, ...args: any[]) => boolean'. Type 'this' is not assignable to type 'boolean'. Type 'Socket' is not assignable to type 'boolean'. The signature of the emit() method was fixed in version 3.0.1 ( commit ). the client is disconnected when sending a big payload (> 1MB) This is probably due to the fact that the default value of maxHttpBufferSize is now 1MB . When receiving a packet that is larger than this, the server disconnects the client, in order to prevent malicious clients from overloading the server. You can adjust the value when creating the server: const io = require ( "socket.io" ) ( httpServer , { maxHttpBufferSize : 1e8 } ) ; Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at xxx/socket.io/?EIO=4&transport=polling&t=NMnp2WI. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Since Socket.IO v3, you need to explicitly enable Cross-Origin Resource Sharing (CORS). The documentation can be found here . Uncaught TypeError: packet.data is undefined It seems that you are using a v3 client to connect to a v2 server, which is not possible. Please see the following section . Object literal may only specify known properties, and 'extraHeaders' does not exist in type 'ConnectOpts' Since the codebase has been rewritten to TypeScript (more information here ), @types/socket.io-client is no longer needed and will actually conflict with the typings coming from the socket.io-client package. missing cookie in a cross-origin context You now need to explicitly enable cookies if the front is not served from the same domain as the backend: Server import { Server } from "socket.io" ; const io = new Server ( { cors : { origin : [ "https://front.domain.com" ] , credentials : true } } ) ; Client import { io } from "socket.io-client" ; const socket = io ( "https://backend.domain.com" , { withCredentials : true } ) ; Reference: Handling CORS cors option withCredentials option Edit this page Last updated on Nov 15, 2025 Previous Performance tuning Next Migrating from 3.x to 4.0 Configuration Saner default values CORS handling No more cookie by default API change io.set() is removed No more implicit connection to the default namespace Namespace.connected is renamed to Namespace.sockets and is now a Map Socket.rooms is now a Set Socket.binary() is removed Socket.join() and Socket.leave() are now synchronous Socket.use() is removed A middleware error will now emit an Error object Add a clear distinction between the Manager query option and the Socket query option The Socket instance will no longer forward the events emitted by its Manager Namespace.clients() is renamed to Namespace.allSockets() and now returns a Promise Client bundles No more "pong" event for retrieving latency ES modules syntax emit() chains are not possible anymore Room names are not coerced to string anymore New features Catch-all listeners Volatile events (client) Official bundle with the msgpack parser Miscellaneous The Socket.IO codebase has been rewritten to TypeScript Support for IE8 and Node.js 8 is officially dropped How to upgrade an existing production deployment Known migration issues Documentation Guide Tutorial Examples Server API Client API Help Troubleshooting Stack Overflow GitHub Discussions Slack News Blog Twitter Tools CDN Admin UI About FAQ Changelog Roadmap Become a sponsor Copyright © 2026 Socket.IO | 2026-01-13T08:48:25 |
https://www.fine.dev/blog/ai-programming-tips | AI Programming Tips: Make Your Coding Smarter and Easier Home Docs Changelog Pricing Sign in Get started -> Menu Home Docs Changelog Pricing <- Go Back AI Programming Tips: Make Your Coding Smarter and Easier Table of Contents Use AI for Debugging Automate Routine Coding Tasks Use AI to Learn New Programming Languages Get Instant Code Reviews Boost Productivity with AI-Generated Documentation Optimize Your Code with AI Use AI to Get Unstuck Integrate AI for Continuous Learning How to Get Started with AI Programming The Future of AI in Programming Take the Next Step with Fine 1. Use AI for Debugging Debugging can be one of the most time-consuming parts of programming. AI tools are excellent at helping you find and fix bugs faster. By analyzing error patterns, AI can suggest solutions, highlight areas of concern, and even predict issues before they cause major problems. Using AI debugging tools can reduce debugging time significantly and help you avoid future errors by learning from past issues. The key to using AI for debugging lies in context - you'll need a tool that has full access to your codebase for it to spot the errors. Fine syncs with your GitHub, enabling it to search multiple files and save your programmers time in fixing bugs. 2. Automate Routine Coding Tasks Coding often involves repetitive tasks—like writing boilerplate code, testing, or refactoring. AI tools can take care of these mundane tasks, allowing you to focus on more creative aspects of your projects. AI-powered assistants like Fine can generate common functions, automate unit tests, and even refactor code for better readability. This not only saves time but also reduces mental fatigue by eliminating the need to perform repetitive work, ensuring you spend more time solving meaningful problems. 3. Use AI to Learn New Programming Languages Switching to a new programming language can be daunting, but AI can help bridge the gap. AI-based language models, like ChatGPT or language-learning platforms that integrate AI, can help explain syntax differences, translate code snippets from one language to another, and even suggest best practices. Imagine wanting to switch from Python to Go—AI can not only translate your code but also offer context-specific suggestions that reflect best practices in the new language. This helps you get up to speed faster and makes transitioning between languages less stressful. 4. Get Instant Code Reviews Code reviews are a crucial part of any software development process, ensuring that your code meets the quality and style standards of your team. But waiting for a review can be time-consuming, especially in busy teams. AI can help by providing immediate code reviews that highlight potential errors, suggest best practices, and ensure consistency across the board. Tools like Fine’s AI-powered PR review feature can not only catch bugs early but also ensure that your code is clean, efficient, and ready for human review. This is especially helpful when you want to make quick changes without waiting on your team members. We recommend using the PR review feature as an extra layer before the regular review. In addition, when reviewing a PR on GitHub, Fine users can comment /summary to get an instant summary to help them get started, and /revise followed by the change they'd like to make, and the AI will make it for them - saving you from pulling the code to your machine just to make minor edits. 5. Boost Productivity with AI-Generated Documentation Writing documentation is necessary but often neglected because it’s time-consuming and not as fun as coding itself. AI can take the sting out of this task by generating comprehensive documentation from your code automatically. For instance, AI tools like Fine can analyze your functions, understand their purpose, and create the corresponding documentation, making sure that your work is well-documented for future reference. This not only saves time but also makes onboarding new team members easier. Fine excels at generating docs, logstrings and tests, because it matches your existing style, having studied your codebase. 6. Optimize Your Code with AI AI tools can also help you optimize code, making it more efficient and easier to maintain. By analyzing the codebase, AI can suggest better data structures, algorithm improvements, or even highlight sections of the code that may benefit from refactoring. For example, an AI tool might identify that a nested loop could be replaced with a more efficient algorithm, saving processing time and resources. Using these suggestions can help your application run faster and be more scalable. 7. Use AI to Get Unstuck Every programmer hits a roadblock from time to time. Whether it’s a tricky bug, a logic problem, or simply the lack of inspiration, AI can help you move forward. Conversational AI models can answer technical questions, suggest different approaches to solve a problem, or even brainstorm ideas for new features. When you’re stuck, tools like Fine’s integrated AI assistant can be the ally you need to overcome challenges, helping you make progress without wasting time. 8. Integrate AI for Continuous Learning AI isn’t just for the present—it’s also a great tool for continuous learning. By integrating AI into your development process, you’ll learn faster by seeing suggestions, alternative methods, and best practices directly in your workflow. This hands-on learning helps solidify concepts more effectively than reading documentation alone. By using AI tools consistently, you’ll develop a deeper understanding of different programming techniques, helping you grow as a developer over time. How to Get Started with AI Programming Getting started with AI programming is easier than you think. Begin by integrating AI-powered tools into your existing workflow. Fine is the tool that provides AI Programming features for the entire SDLC. Start small. Use AI to assist in debugging, generate test cases, or optimize code snippets—and slowly expand its role as you become more comfortable with it. Don’t try to automate everything at once; instead, focus on how AI can solve a pain point in your process and build from there. The Future of AI in Programming The integration of AI in programming is still evolving, and the opportunities are limitless. From automating entire workflows to creating intelligent bots that can handle code reviews, AI is poised to revolutionize how we build software. Adopting AI today means you’re getting ahead of the competition and building skills that will become essential in the future. Take the Next Step with Fine Ready to take your coding skills to the next level? Fine is here to help you harness the power of AI to boost your productivity, reduce errors, and make coding more enjoyable. With features like AI-powered debugging, automated code reviews, and intelligent documentation, Fine can transform your development workflow. Sign up today and experience the difference AI can make in your programming journey. Sign up for Fine now and start coding smarter! Start building today Try out the smoothest way to build, launch and manage an app Try for Free -> © Fine.dev - All rights reserved. Product Overview AI Workflows Pricing & Plans Changelog Blog Docs Company Press Terms & Conditions Privacy policy | 2026-01-13T08:48:25 |
https://docs.suprsend.com/docs/developer/versioning/sdk-changelog | SDK Changelog - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection Developer Resources Overview Updates and Versioning Versioning and Support Policy SDK Changelog Authentication API Keys and Secrets Service Token Best Practices for Key & Token Management MCP Overview BETA Quickstart Tool List Building with LLMs Security Security SDKs and APIs SDKs Management API REST API Postman Collection Features Validate Trigger Payload Type Safety Testing Testing the Template Test Mode Monitoring and Logging Logs Data Out Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Updates and Versioning SDK Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Updates and Versioning SDK Changelog OpenAI Open in ChatGPT Complete release history for all SuprSend SDKs with detailed release notes, features, fixes, and breaking changes. OpenAI Open in ChatGPT The SuprSend SDK Changelog provides a comprehensive record of all SDK releases, including new features, bug fixes, breaking changes, and security updates across all supported platforms. Release History Server-side SDKs Client-side SDKs Python SDK - v0.15.0 Repository: suprsend-py-sdk Latest Release: v0.15.0 v0.15.0 Aug 30, 2025 Changes: v2 APIs and response fixes v0.14.0 Apr 12, 2025 Changes: Removed cap of 100 from workflow recipients v0.13.0 Feb 26, 2025 Features: User APIs v0.12.0 Nov 4, 2024 Changes: Updated README and renamed $pushvendor to $id_provider Objects implementation methods v0.11.0 Apr 18, 2024 Features: Added support for user’s timezone Added support for workflow trigger API v0.11.0-pre Apr 16, 2024 Features: Workflow trigger API v0.10.0 Jan 29, 2024 Features: Added tenants API v0.9.0 Oct 31, 2023 Features: Added set/setonce/increment method to update subscriber properties v0.8.0 Oct 16, 2023 Features: Added support for Microsoft Teams v0.7.0 Sep 14, 2023 Changes: Increased idempotency key length to 255 v0.6.0 Feb 27, 2023 Features: Support for all outbound Slack messages v0.6.0-pre Feb 27, 2023 Features: Support for all outbound Slack messages v0.5.2 Jan 6, 2023 Features: Support dynamic workflow for transient users v0.5.1-pre Dec 26, 2022 Features: Subscribers List and broadcast APIs v0.5.0 Dec 10, 2022 Features: User operation events v2 schema Faster jsonschema validation for workflows and events v0.4.2-alpha Oct 21, 2022 Features: Expose APIs to add/update/retrieve organization brands v0.4.1 Oct 19, 2022 Features: Support for attachments using URL v0.4.0 Oct 10, 2022 Features: Added user.set_preferred_language() method to enable multi-lingual notifications based on user’s preference v0.3.0 Sep 29, 2022 Features: Support for idempotency-key in workflow and event v0.2.1 Sep 21, 2022 Changes: Minor fixes v0.2.0 Sep 21, 2022 Changes: Terminology changed from Batch to Bulk v0.1.5 Sep 5, 2022 Features: Workflow now supports User channel preference Workflow now supports push tokens with provider v0.1.4 Sep 3, 2022 Features: Batch support for Events, Workflows and Users v0.1.3 Jul 24, 2022 Changes: Updated mandatory channels list in Dynamic workflow trigger v0.1.2 Jul 6, 2022 Features: Added user methods: add_slack_email , add_slack_userid , remove_slack_email , remove_slack_userid v0.1.1 Apr 30, 2022 Initial Release v0.1.0 Apr 28, 2022 Initial Release v0.1.0-pre Apr 13, 2022 Pre-release v0.0.15 Apr 13, 2022 Initial Release Node.js SDK - v1.13.1 Repository: suprsend-node-sdk Latest Release: v1.13.1 v1.13.1 2 weeks ago Bugfix: Fixed error naming issue in users API v1.13.0 May 21, 2025 Changes: Added user APIs Removed validation for user channel methods Request payload size changes v1.12.0 Jan 30, 2025 Features: Object improvement and user methods support v1.11.1 Jan 18, 2025 Bugfix: Added defaults for optional method parameters in objects v1.11.0 Nov 4, 2024 Changes: Updated README Added object implementation methods v1.10.0 May 1, 2024 Features: Added new workflow API Timezone set method in user methods v1.9.1 Mar 13, 2024 Changes: Added preferred_language in workflow schema v1.9.0 Jan 10, 2024 Features: Added tenant APIs Microsoft Teams channel added Syncing list by version methods added User methods: set, set_once, increment added v1.8.2 Nov 9, 2023 Fixes: Fixed GitHub dependabot issues v1.8.1 Jun 13, 2023 Changes: Increased idempotency_key length v1.8.0 Apr 22, 2023 Features: Error handling in bulk API v1.7.1 Mar 31, 2023 Fixes: Fixed error logging related issue in bulk APIs v1.7.0 Mar 16, 2023 Fixes: Fixed dependabot vulnerabilities in json5 and minimatch packages v1.6.0 Mar 2, 2023 Features: Added add_slack , remove_slack methods Deprecated add_slack_email , remove_slack_email , add_slack_userid , remove_slack_userid Workflow.json file minor changes v1.5.1 Feb 20, 2023 Changes: Made config flag optional while initializing SuprSend instance v1.5.0 Feb 16, 2023 Features: Added types in this SDK for TypeScript support v1.4.0 Jan 12, 2023 Features: Broadcast method added List object naming change v1.3.0 Dec 30, 2022 Features: User operations implementation v1.2.0 Dec 24, 2022 Features: Added list API methods v1.1.2 Dec 19, 2022 Features: Added brands API v1.1.1 Oct 23, 2022 Changes: Updated README Implementation of user language preference method v1.1.0 Oct 20, 2022 Features: Implementing remote file URL as attachment v1.0.0 Sep 30, 2022 Features: Bulk APIs implementation for users, events, and workflows Adding an idempotency_key in the event and workflow to ignore duplicate requests v0.1.1 Jul 2, 2022 Changes: Updated axios and babel-core packages versions v0.1.0 May 3, 2022 Features: Send Track events and set user channels through SDK Implemented Success Metrics v0.0.6 May 3, 2022 Features: Initialize SuprSend SDK Create Dynamic Workflows Java SDK - v0.12.0 Repository: suprsend-java-sdk Latest Release: v0.12.0 v0.12.0 Aug 30, 2025 Features: v2 APIs response structure v0.11.0 Jul 5, 2025 Features: HTTP proxy implementation v0.10.0 May 22, 2025 Changes: Changed payload size limit to 800KB v0.9.0 Feb 1, 2025 Features: Added all user APIs v0.8.0 Jan 24, 2025 Features: Added objects implementation methods v0.7.2 Jan 21, 2025 Changes: Upgraded dependencies v0.7.1 Nov 8, 2024 Changes: Renamed $pushvendor to $id_provider Removed regex validation from JSON schema v0.7.0 May 5, 2024 Features: Added API to trigger workflow via slug v0.6.0 Jan 29, 2024 Features: Added subscriber properties List versioning Microsoft Teams support v0.5.0 Mar 6, 2023 Features: Bulk Event, Subscriber & Workflow Support List Support & Broadcast Support v0.4.0 Sep 29, 2022 Features: Added support for idempotency key Accept idempotencyKey as part of event and workflow v0.3.0 May 29, 2022 Changes: Refactored codebase Java 8 compatibility Go SDK - v0.8.0 Repository: suprsend-go Latest Release: v0.8.0 v0.8.0 Sep 1, 2025 Features: Added TikTok and X social links to Brand and Tenant structures Updated response as per event.v2 API & workflow schema v0.7.0 Jul 23, 2025 Features: Added proxy support Added Preferences API methods v0.6.0 May 10, 2025 Changes: Updated README and renamed $pushvendor to $id_provider Bumped golang.org/x/net dependencies Added object and user API methods v0.5.1 Apr 18, 2024 Fixes: Git tag issue with v0.5.0 v0.5.0 Apr 18, 2024 Features: Added support for user’s timezone Added support for workflow trigger API v0.5.0-pre Apr 16, 2024 Features: Workflow trigger API v0.4.0 Jan 28, 2024 Features: Added tenants API List versioning Microsoft Teams support v0.3.1 Oct 12, 2023 Security: Upgraded go/net package as part of security fix v0.3.0 Mar 8, 2023 Features: Include all new features v0.2.0 Jan 6, 2023 Features: Support for transient users in Dynamic workflow v0.1.0 Nov 16, 2022 Features: Added basic README and examples JavaScript SDK - v4.0.3 Repository: suprsend-web-sdk Latest Release: v4.0.3 v4.0.3 11 hours ago Bugfix: Socket connection authentication failed issue after refresh v4.0.2 2 weeks ago Changes: Socket.io connection config changes to support offline mode v4.0.1 Jul 28, 2025 Features: WebPush token update optimization v4.0.0 Jul 24, 2025 Bugfix: Pagination issue while archiving notification v3.1.0 May 24, 2025 Changes: Documentation service worker link version change Added preferences tags v3.0.3 Apr 22, 2025 Changes: Updated documentation Bugfix: Fixed host undefined issue in service worker file v3.0.2 Jan 8, 2025 Changes: Added documentation for in-app feed v3.0.1 Jan 7, 2025 Features: Support for feed v2.0.1 Sep 10, 2024 Changes: Revamp: v2 version of web SDK React SDK - v0.3.2 Repository: suprsend-react-sdk Latest Release: v0.3.2 v0.3.2 11 hours ago Bugfix: Socket connection authentication failed issue after refresh v0.3.1 2 weeks ago Changes: Version updated and Socket.io connection config changes v0.3.0 Aug 19, 2025 Features: Shadow DOM support and custom infinite scroll component v0.2.1 Jul 28, 2025 Features: WebPush add token optimization v0.2.0 Jul 24, 2025 Bugfix: Archive pagination bug fix v0.1.3 May 24, 2025 Changes: Updated @suprsend/react-core version v0.1.2 May 15, 2025 Bugfix: Markdown ESM issue fix v0.1.1 Apr 17, 2025 Changes: Updated core-sdk version v0.1.0 Apr 17, 2025 Features: Language support v0.0.7 Mar 18, 2025 Features: Added disable markdown flag v0.0.6 Feb 18, 2025 Bugfix: Fixed typedef bug related to children v0.0.5 Feb 3, 2025 Bugfix: Scrolling issue in macOS and always show action menu icon in mobile v0.0.4 Jan 16, 2025 Bugfix: Action menu overflow issue fixed v0.0.3 Jan 11, 2025 Bugfix: Improved docs and fixed null case issue of notification card v0.0.2 Jan 8, 2025 Changes: Added documentation Android SDK - 0.1.8 Repository: suprsend-android-sdk Latest Release: 0.1.8 0.1.8 Sep 4, 2022 Bugfix: Notification - Small Icon & Action Icon support If icon does not exist in drawable folder then notification was not getting shown 0.1.4 Jun 17, 2022 Changes: Removed cached flag and added check to verify app launch 0.1Beta9 Apr 24, 2022 Changes: Minor fixes iOS SDK - 1.0.7 Repository: SuprSend-iOS-SDK Latest Release: 1.0.7 1.0.7 Mar 11, 2025 Changes: Link SQLite library 1.0.6 Mar 11, 2025 Changes: Remove bitcode from SuprsendCore 1.0.4 Mar 11, 2025 Changes: Bump pod version 1.0.3 Aug 13, 2024 Features: iOS APNS push delivery status improvements 1.0.2 Feb 4, 2023 Changes: SuprSend SDK changes for unsubscribe push notifications on reset React Native SDK - v2.5.0 Repository: suprsend-rn-sdk Latest Release: v2.5.0 v2.5.0 Mar 13, 2025 Changes: Upgraded native iOS SDK to fix bitcode issue v2.4.0 Sep 3, 2024 Changes: Fixed GitHub dependabot issues Updated iOS native version to fix APNS delivery issue v2.3.1 Sep 25, 2023 Fixes: Fixed GitHub dependabot issues v2.3.0 Mar 21, 2023 Fixes: Fixed GitHub Dependabot vulnerabilities in dependencies v2.2.0 Mar 13, 2023 Changes: Updated Android SDK version to enable sound customization in FCM push v2.1.0 Feb 9, 2023 Features: Added unsubscribe push flag in reset method v2.0.2 Jan 6, 2023 Features: Added enableLogging method Deprecated setLogLevel method v2.0.1 Jan 4, 2023 Bugfix: Reset bugfix in iOS v2.0.0 Dec 29, 2022 Features: Upgraded Android native SDK version Method to ask notification permission for Android version >= 13 Reset method now takes a parameter to remove push tokens on logout v1.0.0 Sep 28, 2022 Changes: Upgraded native iOS SDK version v0.4.3 Sep 17, 2022 Fixes: Fixed track method issue in Android iOS deployment version upgraded to 11 in podspec for iOS v0.4.2 Sep 6, 2022 Changes: Upgraded native Android version v0.4.1 Aug 31, 2022 Changes: Updated native Android version v0.4.0 May 20, 2022 Features: iOS implementation in React Native iOS Push notifications implemented v0.3.14 May 20, 2022 Features: Initial stable release with only Android implementation in this React Native project Flutter SDK - v2.5.0 Repository: suprsend-flutter-sdk Latest Release: v2.5.0 v2.5.0 Jun 7, 2025 Changes: Upgraded native SuprSend Android SDK version v2.4.0 May 10, 2025 Changes: Added namespace changes and removed ask notification permission method v2.3.1 Mar 11, 2025 Bugfix: Upgraded iOS SDK version to fix bitcode v2.3.0 Mar 11, 2025 Changes: Upgraded version of native iOS SDK v2.2.0 Aug 14, 2024 Changes: Fixed iOS delivery issue v2.1.1 Nov 30, 2023 Changes: Native Android SDK version updated Removed debug logs in Android on identify v2.1.0 Feb 9, 2023 Features: Added unsubscribePush flag in reset method v2.0.1 Jan 24, 2023 Changes: Downgraded minimum Dart SDK version to 2.15.0 from 2.16.0 v2.0.0 Jan 6, 2023 Features: Updated native Android version Reset method now accepts unsubscribe_push flag Added permission method to ask for user permission to show notifications for Android 13 v1.0.0 Nov 4, 2022 Changes: Upgraded native iOS SDK version to 1.0.1 Migration Guides For detailed migration instructions between major versions, please refer to our SDK Migration Guide . Support If you encounter any issues during migration or have questions about specific releases, please contact our support team at [email protected] Was this page helpful? Yes No Suggest edits Raise issue Previous API Keys and Secrets Learn the different authentication methods available in SuprSend and how to securely integrate them into your application. Next ⌘ I x github linkedin youtube Powered by On this page Release History Migration Guides Support | 2026-01-13T08:48:25 |
https://docs.devcycle.com/platform/experimentation/feature-experimentation/ | Feature Experimentation | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up Home Getting Started Essentials DevCycle Overview Key Features System Architecture Feature Hierarchy Feature Types Platform Feature Flags Experimentation Feature Experimentation Creating and Managing Metrics How Metrics are Calculated Video Tutorial: Experiment Setup Tutorial: Funnel Experiment Account Management Security and Guardrails Testing and QA Extras Examples Platform Experimentation Feature Experimentation On this page Feature Experimentation Overview At DevCycle we believe that Experimentation should be a part of the natural lifecycle of all Features. So no matter the Feature type selected, can be experimented on. Experiments can be as simple as comparing any target audiences against a Metric, or can be fully randomized A/B tests using statistical methodologies. This article outlines why and how to run and analyze Experiments on your Features within DevCycle. Why Experiment Experimentation is crucial for testing modifications to your product. You may investigate which changes would result in the best outcomes. It's also known as split testing or A/B testing, or comparative analysis depending on who you ask. Experimentation can be used to test new Features, design changes, marketing campaigns, or anything that could potentially impact how a product or service is used. You may want to experiment on any of these things and more: Validate to make sure application performance remains the same or improves. Validate in a controlled way whether code changes increase or decrease error rates. Confirm that a new Feature is driving more conversions or revenue. Measure real impacts of Features on SLAs and SLOs. You've likely been doing "Experimentation" without knowing it. Whenever you release a new feature or service, compare the before and after (and during). When combined with Features, DevCycle can give direct Metrics on a feature's performance during a release, allowing you to react and make changes accordingly. Of course, with this in mind, your team isn't restricted to a simple on or off approach. Using DevCycle, a team can have numerous Variations which are released and tested at the same time, giving an even deeper view with more flexibility. Using Experimentation To run an Experiment on any Feature, all you need is two things: At least two Variations served to your users At least one Metric defined and attached to your Feature Comparing Multiple Variations The primary concept of an Experiment is the need to have at least two different experiences to compare performances. There are several ways in DevCycle to run multiple experiences for users. We go into depth on this in our Targeting documentation . To get started with your first Feature Experiment, it is best to keep it simple and run a basic A/B test comparing two Variations, one control and one treatment Variation, delivered randomly to all your users. To set this up, create a targeting rule in Production that delivers to All Users and serves Variations randomly with percentages set equally at 50% against your first Variation, and 50% against your second Variation. Adding Metrics to Your Feature info Experimentation relies on Custom Events . Experimentation is available to all customers on any plan. However, to perform Experiments, events must be sent to DevCycle to calculate Metrics. These events are added to your existing plan. To learn more, read about our pricing , or contact us. Now that you have two segments receiving different experiences, the only other thing you need to run an Experiment is a Metric to evaluate the comparative performance of those experiences. To add a Metric to your Feature, click “Experiment Results” under the “Data & Results” section on the sidebar of the Feature editing page. Click the “Choose a Metric” dropdown. This will bring up the option to add a Metric that has already been created in the Project or to create a new one. For the creation of new Metrics check out our documentation here . Once you have Metrics in your Project, all you need to do is: Select a Metric you want to use to judge the performance of your Experiment Set the Variation that you want to use as your control Variation Now that you have a Metric added and a control Variation selected, the performance of the Experiment will be tracked over time. The performance of the treatment Variation compared to the control Variation will be tracked by the Difference and Statistical Significance indicator in real-time as the Experiment progresses. Any number of Metrics can be added to a Feature for analysis, keep clicking “Choose a Metric” and add pre-existing or create new Metrics as needed. Determining a Winner The most important part of an Experiment is determining a winner. The length of time an Experiment needs to run to determine a winner varies depending on the overall traffic, the observed conversion rate, and the size of the difference in conversion or values between the Variations. Typically Experiments should be run for a minimum of 1-2 weeks to achieve valid statistical significance with a good amount of time to get a proper cross-section of your user base. Given the time it takes, your team should generally avoid early analysis and create a process by which an Experiment runs with no review of results until a pre-determined amount of time has passed. Once this time has passed, the charts and graphs for any added Metrics can be reviewed to determine which Variation performed best. When Metrics are created, you define if a decrease or an increase is the targeted improvement. Our results graphs take this into account and show clearly if the Metrics have driven either positive or negative results. The charts also provide guidance on if statistical significance has been achieved by displaying the following indicators. Statistical Significance Definition ✅ Positive Significant Result ❌ Negative Significant Result ... Non-Significant Result Positive Results Negative Results Experimentation using a Custom Property for Randomization info For documentation on this functionality outside of the context of experimentation you can check out our documentation dedicated to this topic here . DevCycle typically uses the User ID as the primary key for Feature rollouts and randomization. However, in certain scenarios, Features you release are intended to be rolled out to a cohort of users vs an individual user. For example, a new feature in a B2B platform might impact an entire Organization rather than a single user within that Organization. In such cases, you can randomize and rollout by using a Custom Property. What are Experiments that Randomize Using a Custom Property? When running an Experiment where you randomize using a Custom Property, the Experiment is applied to a set of users (those who possess a Custom Property) rather than individual users. This means that every user who has that Custom Property will experience the same Feature Variation, such as being part of the control or the test variant. This approach allows you to assess the impact of changes on the group as a whole. Groups in DevCycle are defined using Custom Properties. These groups could be companies, tenants, geographic locations, or any set of users sharing common characteristics. How to Randomize Using a Custom Property in Experiments To set this up, create a Targeting Rule that serves a Random Distribution of the Variations. When you select Random Distribution , Randomize Using field will appear at the bottom of the Targeting Rule under the Schedule section. The dropdown will populate with all existing Custom Properties. Select the Custom Property you wish to use for your random distribution. If you are both randomizing distribution and using a gradual rollout of some form, the Custom Property will be used for both forms of randomization, keeping distribution sticky based off of that property. Risks to Experimentation There are several risks to be aware of when randomizing your Experiments in this way: Less Statistical Power: In Experiments with randomization using a Custom Property, each group is treated as a single data point, reducing the overall statistical power of the Experiment. For example, a platform might have millions of users but only a few thousand companies using it. This typically requires running these types of Experiments for a longer period to achieve statistically significant results. Higher Randomization Risk: There's a greater risk of improper randomization when assigning Custom Properties to control or test variants. With fewer data points, any imbalance can significantly skew the results. For example, if a new pricing model is tested across different companies, an imbalance in the distribution of company sizes could lead to inaccurate conclusions about the model’s effectiveness. Fewer User-Level Insights: Custom Property-targeted Experiments provide insights at an aggregate level, potentially obscuring user-level behaviors and preferences. For example, a new feature might increase overall usage within a company, but it might not reveal which specific roles or user types are most engaged with the feature. Randomization Collisions: Our random distribution system works on a murmurhash, where we purposely limit User IDs to less than 200 characters to reduce the risk of collisions. If you randomize off of a Custom Property where the values are over 200 characters there is a potential for collisions that could impact randomization. Regardless of the type of risk, if you are worried about the statistical validity of your Experiment you should make sure that there is both a significant number of groups as well as good balanced stratification across the groups that you're testing against. These two factors protect you against the most substantial risks. Edit this page Last updated on Jan 9, 2026 Previous Stale Feature Notifications Next Creating and Managing Metrics Overview Why Experiment Using Experimentation Comparing Multiple Variations Adding Metrics to Your Feature Determining a Winner Experimentation using a Custom Property for Randomization What are Experiments that Randomize Using a Custom Property? How to Randomize Using a Custom Property in Experiments Risks to Experimentation DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:25 |
https://www.fine.dev/blog/cto-challenges | Top 7 Challenges CTOs Face in Startups (and How to Solve Them) Home Docs Changelog Pricing Sign in Get started -> Menu Home Docs Changelog Pricing <- Go Back Top 7 Challenges CTOs Face in Startups (and How to Solve Them) Being a startup CTO is exhilarating. You’re at the heart of innovation, solving complex technical challenges, and laying the foundations for your company’s growth. But it's not without its unique hurdles. Let's explore the top seven challenges faced by CTOs in startups, along with actionable solutions to navigate them effectively. Table of Contents Scaling Technology Under Limited Resources Balancing Speed with Technical Debt Recruiting Top Talent in a Competitive Market Maintaining Product Quality at High Speed Aligning Business Goals with Technical Strategy Staying on Top of Security and Compliance Managing Team Morale and Burnout 1. Scaling Technology Under Limited Resources Scaling a tech stack is already challenging, but when resources are scarce, the difficulty multiplies. Startups often need to scale quickly, without the luxury of a big budget or large engineering teams. The key is focusing on smart scaling by leveraging cloud services and serverless technologies that grow with your needs without massive upfront investments. Start with solutions like AWS Lambda or Google Cloud Run to minimize costs until your usage justifies a bigger architecture. However, it's also important not to invest too heavily in scaling too early when you have only a few users, as this can waste valuable resources. Instead, focus on keeping your infrastructure lean during the early stages, and optimize for growth only when demand starts to increase. Additionally, consider using managed services to offload maintenance tasks. For example, managed databases like Amazon RDS or Google Cloud SQL can save significant time and effort, allowing your team to focus on core product development rather than infrastructure management. Another strategy is to implement auto-scaling to ensure that your application can handle fluctuating loads efficiently without overspending. Planning for scalability from day one, even with a basic MVP, helps avoid costly re-architectures down the line. Embrace a microservices architecture if feasible, as it allows different parts of the application to scale independently, thus optimizing resource allocation and reducing the risk of bottlenecks. Finally, prioritize monitoring and observability tools to gain insights into performance and resource usage, enabling proactive adjustments and cost control as you scale. 2. Balancing Speed with Technical Debt Startups need to move fast, but speed can lead to shortcuts that accumulate technical debt. Managing this balance requires setting clear priorities. Not every piece of tech debt needs immediate fixing—some can wait. Adopting agile practices and scheduling dedicated tech debt reduction sprints can ensure your team doesn't drown in unresolved issues while maintaining momentum. AI can help by taking on the task of reducing technical debt, allowing developers to maintain their momentum with innovation. Take advantage of tools such as Fine whilst reducing technical debt. If you're identifying redundant code Fine can help search the codebase to make sure it's not needed for something you've missed. Fine can also suggest improvements and even fixing minor issues autonomously. Delegating these tasks to AI ensures that technical debt is addressed continuously without pulling developers away from creative problem-solving and building new features. This way, your team can focus on pushing forward innovative ideas while ensuring that technical debt doesn't stack up and slow progress. When utilizing AI, assigning 5% of developer time to technical debt should be enough to ensure you're moving forwards without dropping the ball. 3. Recruiting Top Talent in a Competitive Market The demand for great developers is fierce. Startups need to attract talent without competing directly on salary with larger corporations. Building a compelling mission, offering meaningful equity, and emphasizing the opportunity for hands-on growth are key levers for startup CTOs. Create a culture where developers feel their impact—highlight how their work drives the company's success. Everyone needs to pay the bills but there are other ways to ensure you're competitive as an employer. Good developers are experts and want to feel as such - if they're not appreciated, making a difference, challenged or listened to, they may move on to other employers. 4. Maintaining Product Quality at High Speed Startups need to iterate quickly to fit market needs, but rapid iteration can lead to quality issues. Implementing automated testing and adopting continuous integration/continuous delivery (CI/CD) pipelines can help maintain quality without slowing down. Tools like Jenkins, GitHub Actions, or CircleCI allow your team to ship often, but with confidence. Combining these tools with an AI such as Fine means you can allow yourself to ship faster, knowing that you've got a robust set of tests in place and can quickly iterate fixes if something fails. 5. Aligning Business Goals with Technical Strategy CTOs must act as the bridge between the business and technical worlds. Early-stage startups need to adapt constantly, which requires a technical roadmap that’s agile enough to change course when needed. Regular cross-functional meetings with product and sales teams ensure alignment between tech decisions and business priorities, reducing the risk of building features that don’t meet market needs. 6. Staying on Top of Security and Compliance Security can be overwhelming for startup CTOs, given the lack of dedicated resources. A good starting point is building security into your development pipeline—adopt practices like regular vulnerability scanning , encryption, and using secure coding standards. Many tools, such as Snyk and Dependabot, can help automate this process, making security a habit rather than an afterthought. 7. Managing Team Morale and Burnout The high-paced startup environment can easily lead to burnout. CTOs need to foster a sustainable culture by encouraging reasonable work hours and focusing on results over hours spent. Offer flexible schedules and create an environment where the team can openly discuss their workload. A culture of empathy, combined with setting realistic goals, helps retain top talent and prevents burnout. Try to strike a balance within your team - so no one developer is just working on endless minor fixes, but nor are they months stuck on one large issue. Many minor tasks that take a developer 15-30 minutes can be delegated to AI and complete in under 10, including a review by a developer. Similarly, large projects can be broken down into tasks suited for AI to complete. Conclusion Navigating the challenges of a startup CTO requires a unique mix of technical and leadership skills. From scaling with limited resources to ensuring your team is motivated and aligned, the key is adaptability and a proactive approach to both people and technology. Stay focused on aligning your technical efforts with the company's evolving needs, and remember: you don’t need to have all the answers, but you need the flexibility to find them quickly. Embrace tools, processes, and a culture that empower your team to grow—that’s how startups succeed. Are you facing these challenges and looking for ways to empower your development team? Fine is here to help streamline development workflows, allowing your team to focus on what truly matters. Discover more about Fine's AI-driven coding solutions . Start building today Try out the smoothest way to build, launch and manage an app Try for Free -> © Fine.dev - All rights reserved. Product Overview AI Workflows Pricing & Plans Changelog Blog Docs Company Press Terms & Conditions Privacy policy | 2026-01-13T08:48:25 |
https://www.linkedin.com/signup/cold-join?session_redirect=https%3A%2F%2Fwww%2Elinkedin%2Ecom%2Fcompany%2Fsuprsend&trk=organization_guest_main-feed-card_social-actions-comments | Sign Up | LinkedIn Join LinkedIn now — it’s free! Not you? Remove photo Join LinkedIn To create a LinkedIn account, you must understand how LinkedIn processes your personal information by selecting learn more for each item listed. Agree to all terms We collect and use personal information. Learn more We share personal information with third parties to provide our services. Learn more Further information is available in our Korea Privacy Addendum . Privacy Policy Addendum 1 of 2 2 of 2 Agree to the term Continue Back Agree to all terms Email Password Show Remember me First name Last name By clicking Agree & Join, you agree to the LinkedIn User Agreement , Privacy Policy , and Cookie Policy . Agree & Join or Security verification Already on LinkedIn? Sign in Looking to create a page for a business? Get help LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language Follow top companies Over 60% of the fortune 100 companies use LinkedIn to hire. Join now Leave | 2026-01-13T08:48:25 |
https://docs.devcycle.com/platform/experimentation/creating-and-managing-metrics/ | Creating and Managing Metrics | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up Home Getting Started Essentials DevCycle Overview Key Features System Architecture Feature Hierarchy Feature Types Platform Feature Flags Experimentation Feature Experimentation Creating and Managing Metrics How Metrics are Calculated Video Tutorial: Experiment Setup Tutorial: Funnel Experiment Account Management Security and Guardrails Testing and QA Extras Examples Platform Experimentation Creating and Managing Metrics On this page Creating and Managing Metrics info Metrics are available to all customers on any plan and rely on Custom Events that must be sent to DevCycle. All plans come with an included amount of free events. When exceeded, additional costs will be incurred. To learn more, read about our pricing , or contact us . This article explains how to create, define, and manage all of the Metrics in a Project. Metrics provide a broad overview of your system. They may be used to quickly assess the health of your Features across environments, visualize how quickly people are visiting your applications, or how much memory is being used by your servers as a Feature rolls out. Metrics may be known as "Goals" on other platforms. Within DevCycle, Metrics are their own items outside of a Feature and thus can be defined once and applied to as many Features as desired. This gives the opportunity to attach and test Metrics with seemingly unrelated Features and find unintended or hidden impacts. Metrics Section To view and create Metrics, first navigate to the Metrics section of the Dashboard This section will contain a list of all of the Metrics on the current Project, all of which are re-usable across any number of Features at any time. This list contains some simple base info. Below is a brief description of each column, with deeper explanations later in this document Name - The name of the Metric. This name is the human-readable format of the Metric for easily discussing the Metrics. As explained later, the key is what will be used within the Management API. Type - The "Type" of Metric which represents the dimension or calculation used for the Metric. It may be a simple count, or a rate, or an average. These type definitions are described below in "Creating a Metric". Event Type - This is the name of the event sent by the SDKs or APIs which is being used for this Metric. Date Modified - Simple date explaining the last time someone made any modifications to a Metric which may have changed anything significant to the calculated results. Creating a Metric Follow the video below from our DevCycle Experiment Setup series or read-along to find out how to create a Metric on DevCycle. To create a Metric, navigate to the Metrics page as noted above, and click "Create a Metric". Metrics can also be created directly within any Feature from the Experimentation panel. Upon clicking create, the following modal will show: To set up a Metric, the following items are needed: Name - This is the name of the Metric. It should be descriptive enough that any team member viewing it understands it and can both get the information necessary, and also decide if they would like to re-use the Metric for other Features. Key - Like other DevCycle keys, this is how this Metric will be referenced in the Management API and all other non-dashboard interactions with this Metric. Event Type - This is the EXACT event name that is sent by the DevCycle Track methods of the SDKs or via the DevCycle APIs. This event will be used in all calculations of the Metric. How it is used specifically is described below in How do Metrics get calculated? Optimize For - DevCycle represents Metrics as a positive or negative depending on the desired optimization. Often times, tools will always assume that an increase is beneficial. However, in most engineering applications, the opposite is true! Things such as latency, load times, server load, and processing times are Metrics that should be decreased. DevCycle will make obvious whether a Metric is improving in the desired direction, and will soon notify you if a significant impact in either direction has been made. Description (optional) - A meaningful description explaining what this Metric is for and why it is being tracked. In conjunction with DevCycle's Jira Integration, this can be useful for managers to get a greater depth of information when understanding Metrics. Type - The type of a Metric defines how and what it is calculating and represented to the user. This "Type" is currently a set of the items defined below and available in the dropdown. Types When making a Metric, the types of Metrics will contain a small definition Count per Unique User - This Metric type calculates the total number of times a unique user (or service) has sent this event. This can be something such as total number of clicks on a new feature, total number of API calls for a new service, total number of of views for a new advertisement, etc. This is also useful for error tracking -- A total count of specific errors is a great Metric to count when monitoring the rollout of a new release of a Feature. Count per Variable Evaluation - This type counts the total number of times this event has been seen ONLY when the actual related Variable has been evaluated. This is a very useful case, as there may be events which already exist within your system which could potentially also be impacted by this Variable. In this case, this type of Metric represents the exact number of times that event has been sent ONLY after the related Variable has since been evaluated for use. Sum per User (numerical) - Each event can carry a numerical value with it, and this Metric will sum up the total number sent with the events per unique user. This type of Metric is great for tracking things such as Revenue, or number of total items purchased or interacted with. From an engineering view, things such as a total number of api calls per unique user may be something intended to decrease (for optimizations) or increase (for increased interaction). Average per User (numerical) - Similar to the sum per user, the average for user also uses the numerical value on each event. This type of Metric is extremely useful for tracking things such as the average latency per API call, or average size of an API call, hoping for a decrease. Load times, server load, api latency, or even your own internal build time can be candidates for a Metric which is re-used across every single Feature for viewing the impact and reacting accordingly. Future Types - If there are any types of Metric you'd like to see, or if your team would like a more flexible view into all of your data, do not hesitate to reach out to [email protected] . We will be increasing the number of types, as well as providing direct calculation control in the future. If such things are desired now, contact us to discuss direct data access, which will provide full access to all events and data for each of your Projects. Metric Details Page After creating a Metric, or by clicking on one from the Metric list, you will be navigated to the Metric Details page. This page has the following sections. Metric Definition The Metric definition allows for modifying the Metric Name, Type, Definition, and Optimization. Metric Testing This section provides the ability to test a Metric against any Feature in any environment and ensure it is working as intended. It is also useful to use this testing section to quickly check a Metric against any given Feature to potentially find any unintended impacts if the Metric is not associated with a specific Feature. When testing a Metric, navigate to the Testing section. To run a test, the following fields must be set: Feature - This is the specific Feature this Metric should be applied to. Any event that has been sent since the creation of this Metric from a user receiving any Variation of this Feature will be part of this Metric. In the event that an error is shown, this means the event has not been seen from this Feature yet. Control - After selecting a Feature, a "control" Variation must be selected. This is what will be used to show a comparative analysis against all other Variations in a Feature. Typically, an "off" or "Baseline" Variation would act as the control. For more information on this, please refer to the Feature Experimentation documentation . Date Range - Select a date range of up to the last 30 days to display results for. This range will default to the last 30 days or to the Feature creation date if the Feature was created within 30 days. Environment - This will calculate the Metric using events from the specified environments. Once these fields are set, the test can be ran by clicking the test button, resulting in a test result. (For these documents, our own internal Metrics testing at this time were used!) The results of this test will show the actual result which would be within a Feature if this Metric was associated with it! Attaching Metrics to Features Tracking Metrics within a Feature is an important aspect of data analysis, as it can provide valuable insights into the performance and behaviour of different Features. Once a Metric has been created, it can be attached to any Feature for use and analysis. Follow the video below from our DevCycle Experiment Setup series or read-along to find out how to add a Metric to a Feature and view Experiment results. Here are the steps you can follow to track Metrics within a Feature: Select the Feature you want to track : Within that Feature, navigate to the Data & Results tab on the Feature Form of the page and click on Experiment Results . Choose the Metric(s) associated with the Feature : Create new Metrics or attach existing ones to the Feature by navigating to the Choose a Metric dropdown. Attach the Metric(s) : Attach the Metric from the dropdown menu by selecting it. For our example, let's use the Metric Metric Testing , which has already been setup within our Project. While the setup has some default values, the Metric requires the following fields to be filled: Control - This is what will be used to show a comparative analysis against all other Variations in a Feature. Typically, an "off" or "Baseline" Variation would act as the control. For more information on this, please refer to the Feature Experimentation documentation . Date Range - Select a date range of up to the last 30 days to display results for. This range will default to the last 30 days or to the Feature creation date if the Feature was created within 30 days. Environment - This will calculate the Metric using events from the specified environments. Calculate results : Once one or more Metrics have been selected, we can then run the Metric calculation to generate insight into how the Feature is doing. View your results : Once calculated, if there is available data for the Feature, the results data will populate within the dashboard. From here, useful information such as trends and patterns in the data can be used to make informed decisions about how to optimize the Feature for performance improvements. How do Metrics get calculated? To calculate Metrics, DevCycle uses the custom events sent via its API or SDKs . Each Event has the information of which user sent it and which Feature and Variation they were in at that time. For optimal Experiments, use Features with Variations randomly distributed across users . To read more on the queries behind the Metrics, see How Metrics Are Calculated Running Experiments With Metrics on a Feature, Experimentation can be easily executed on any Feature. At DevCycle we believe that Experimentation should be a part of the natural lifecycle of all Features. So no matter the Feature type selected, Experimentation will always be available for use. To learn more on how to run Experiments with DevCycle, read Feature Experimentation Edit this page Last updated on Jan 9, 2026 Previous Feature Experimentation Next How Metrics are Calculated Metrics Section Creating a Metric Types Metric Details Page Attaching Metrics to Features How do Metrics get calculated? Running Experiments DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:25 |
https://docs.devcycle.com/integrations/bitbucket/pr-insights-action/ | Bitbucket: Feature Flag Change Insights on Pull Request | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up On this page Bitbucket: Feature Flag Change Insights on Pull Request Get the integration on the Bitbucket Marketplace Bitbucket Pipelines Pipe: DevCycle PR Insights With this Bitbucket pipeline, information on which DevCycle features have been added or removed in a code change will be shown directly on each Pull Request as a comment. Note: This is intended for pull-requests workflow events Example Output YAML Definition Add the following snippet to your bitbucket-pipelines.yml file: pull-requests : '*' : - step : script : - pipe : devcyclehq/devcycle - pr - insights - pipe : 1.2.1 variables : USER_NAME : '<string>' PASSWORD : '<string>' # PROJECT_KEY: '<string>' # Optional. # CLIENT_ID: '<string>' # Optional. # CLIENT_SECRET: '<string>' # Optional. We recommend including your DevCycle API credentials and project token as inputs. If included, the PR comment will be enriched with Feature Flag data from DevCycle. Variables To add variables to be used in the bitbucket-pipelines.yml, an admin must add Repository Variables in Repository Settings > Repository Variables, and then add all necessary variables as secured variables Variable Description USER_NAME (*) Your bitbucket username PASSWORD (*) Your generated app password PROJECT_KEY Your DevCycle project key, see Projects CLIENT_ID Your organization's API client ID, see Organization Settings CLIENT_SECRET Your organization's API client secret, see Organization Settings (*) = required variable. Prerequisites Create a new Project & a new Feature Generate a new App Password Select write permissions under Pull Requests , and create the password Grab your username, can easily find it in Personal Settings Optional Prerequisites Grab the PROJECT_KEY in Projects , and find your specific project name & key Grab the CLIENT_ID in Settings , under API AUTHENTICATION Grab the CLIENT_SECRET in Settings , under API AUTHENTICATION Examples Example: pull-requests : '*' : - step : script : - pipe : devcyclehq/devcycle - pr - insights - pipe : 1.2.1 variables : USER_NAME : $BITBUCKET_USER_NAME PASSWORD : $BITBUCKET_APP_PASSWORD PROJECT_KEY : $DEVCYCLE_PROJECT_KEY CLIENT_ID : $DEVCYCLE_CLIENT_ID CLIENT_SECRET : $DEVCYCLE_CLIENT_SECRET Configuration The patterns used to identify references to variables in your code are fully customizable. This action uses the DevCycle CLI under the hood, for details on how to configure the pattern matcher see the CLI configuration . Support The pipe is maintained by [email protected] . If you are reporting an issue, please include: the version of the pipe relevant logs and error messages steps to reproduce Edit this page Example Output YAML Definition Variables Prerequisites Examples Configuration Support DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:25 |
https://docs.devcycle.com/sdk/#__docusaurus_skipToContent_fallback | SDK Overview | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up SDK Overview SDK Lifecycle SDK Features Client-side SDKS Server-side SDKS SDK Proxy SDK Overview SDK Overview DevCycle has both client-side and server-side SDKs. This page describes the differences between these SDK types. Implementation and usage change depending on which type of SDK is being used. tip Explore our SDK Features and Functionality to discover how to implement your solutions using the DevCycle SDKs. Client Side SDKs DevCycle client-side SDKs are meant for single-user contexts, such as web browsers and mobile apps. These SDKs retrieve their configuration for the current user when they are initialized and any time the user is re-identified. They also receive updates in real time when configuration is changed in the DevCycle platform. The current Client-Side SDKs are: JavaScript SDK React SDK Next.js SDK Angular SDK iOS SDK Android SDK React Native SDK Flutter SDK Roku SDK Server-Side SDKs Server-side SDKs are used in multi-user contexts such as backend services, where each call to the SDK will likely be for a different user. The user's ID and any other targeting information must be passed in on every SDK function call. The current Server-Side SDKs are: NodeJS SDK NestJS SDK Go SDK PHP SDK Python SDK Ruby SDK Java SDK .NET SDK OpenFeature Providers OpenFeature is an open standard that provides a vendor-agnostic, community-driven SDKs for feature flagging that works natively with DevCycle. Client-Side JavaScript React Angular iOS Android Server-Side NodeJS NestJS Go Ruby Java .NET / C# Python PHP Edit this page Last updated on Jan 9, 2026 Next SDK Lifecycle DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:25 |
https://www.linkedin.com/uas/login?fromSignIn=true&session_redirect=https%3A%2F%2Fwww.linkedin.com%2Fcompany%2Fsuprsend&trk=top-card_ellipsis-menu-semaphore-sign-in-redirect&guestReportContentType=COMPANY&_f=guest-reporting | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T08:48:25 |
https://docs.devcycle.com/integrations/terraform | Terraform | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up On this page Terraform DevCycle Terraform Provider is a Terraform provider that provides a way to manage DevCycle projects, features, variables, variations, and environments. It also provides the ability to receive DevCycle Variable values during the apply step, and feature flag the behaviour of other Terraform configuration. Setup Usage Setup Install the Terraform Provider terraform { required_providers { devcycle = { source = "DevCycleHQ/devcycle" version = "1.0.0" } } } provider "devcycle" { client_id = "your-client-id" client_secret = "your-client-secret" server_sdk_token = "project-specific-server-sdk-token" } Set up DevCycle API Credentials All actions by the Terraform provider are scoped at the organization root level. This requires DevCycle API authorization. Your DevCycle organization's client ID and secret must be provided. They can be obtained from the settings page of the DevCycle dashboard. There are several ways to provide these credentials: Directly in the Terraform configuration This is not recommended, as your credentials will be visible in your Terraform state. But if you are securely controlling access to the state file, then this can be used safely. Set the client_id and client_secret fields in the provider.devcycle block in your Terraform configuration to the respective values. These will be used to get an OAuth2 access token at the time of use - this value is not stored in the Terraform state file for security. For the server_sdk_token field, this is scoped to a single DevCycle project. This should be the project you want to control your resources from. The server sdk token can be found in the same settings page as the client id and secret - but you need to select the right project first. Environment Variables Set the following environment variables: $ export DEVCYCLE_CLIENT_ID=<your client id> $ export DEVCYCLE_CLIENT_SECRET=<your client secret> $ export DEVCYCLE_SERVER_TOKEN=<your server token> Terraform will use these as a fallback from the provider passed variables. Meaning the values in the configuration block will take precedence over the environment variables. Usage For more detailed documentation on the DevCycle Terraform provider, see the DevCycle Terraform Provider Documentation After configuration of the provider - let's use the provider to create a DevCycle project. Create a Project resource "devcycle_project" "example" { name = "Example DevCycle Project" key = "example-devcycle-project" description = "Terraform example project" } Running terraform apply will create this project - and you can see it in the DevCycle dashboard. This creates a bare project - with no features or variables. To add those, lets create a feature. Create a Feature resource "devcycle_feature" "example" { project_id = devcycle_project.example.id name = "Example Feature" key = "example-feature" description = "Terraform example feature" type = "experiment" tags = ["terraform"] } This feature takes in the project id as a variable - we're passing in the id exported from the devcycle_project resource to make it simple. But if you wanted to create a feature for an already existing project that isn't managed by terraform - feel free to use the human readable project key instead. Anywhere you see id or key in the configuration, you can use either the human readable key or the id, as the API manages the conversion between the two. The feature resource can create and manage the variations and variables attached to the feature - but it's not recommended to manage the variables if you don't need to in the same block, and to instead use the devcycle_variable resource. Create a Variable resource "devcycle_variable" "example" { name = "Terraform Example Variable" key = "example-variable" description = "Terraform created variable" type = "Boolean" feature_id = devcycle_feature.example.id project_id = devcycle_project.example.id } After creating the variable - you can either read from the existing environments auto-created on project creation: development , staging , production or create a new one. Getting SDK Keys Using the data block - you can read the SDK keys that get generated for the environment to change keys automatically in your Terraform configuration. SDK Keys are prefixed by their type, client , mobile , or server . data "devcycle_environment" "test" { key = "development" project_key = devcycle_project.example.key } output "development_sdk_keys" { value = data.devcycle_environment.test.sdk_keys } Evaluating Variables One of the major features that this provider provides is the ability to evaluate variables. This is done by using the typed data blocks for the type of variable desired. data "devcycle_evaluated_variable_boolean" "create-resource" { default_value = false id = devcycle_variable.example.id user = { id = "user-id" } } This evaluation can then be accessed via data.devcycle_evaluated_variable_boolean.create-resource.value . The default value will be returned if there is no returned value from no matching variation. There is another data block for each type of variable that can be evaluated (JSON, Boolean, String, Number) Each is typed explicitly because a variable type cannot be changed after creation. Contributing to DevCycle or creating a new Integration: If you would like to contribute to an existing integration or tool, all of DevCycle's tools and integrations are open source on the DevCycle github repository. Further, if you'd like to create a new tool or integration, a great starting point is DevCycle's Management API which allows you to modify and interact with features and more within a devcycle project, as well as the DevCycle Bucketing API which is used to give users features and variables (as used within the DevCycle SDKs!) Edit this page Last updated on Jan 9, 2026 Setup Install the Terraform Provider Set up DevCycle API Credentials Usage Create a Project Create a Feature Create a Variable Getting SDK Keys Evaluating Variables DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:25 |
https://www.linkedin.com/login?session_redirect=https%3A%2F%2Fwww%2Elinkedin%2Ecom%2Fcompany%2Fsuprsend&fromSignIn=true&trk=top-card_top-card-secondary-button-top-card-secondary-cta | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T08:48:25 |
https://docs.devcycle.com/sdk/client-side-sdks/react-native | React Native | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up SDK Overview SDK Lifecycle SDK Features Client-side SDKS JavaScript SDK React SDK Next.js SDK Angular SDK iOS SDK Android SDK React Native Installation Expo Installation Getting Started Usage Flutter SDK Roku SDK Server-side SDKS SDK Proxy Client-side SDKS React Native On this page DevCycle React Native The DevCycle React Native SDK lets you easily integrate your React Native web applications with DevCycle. info DevCycle supports React Native Expo. See the React Native Expo SDK installation for more information. caution Extra steps are required to get DevCycle working with React Native Web. See the React Native Web section below for more information. Installation Installing the SDK Expo Installation Installing the Expo SDK Getting Started Initializing the SDK Usage Using the SDK The React Native SDK is available as a package on npm. A separate React Native Expo SDK is available as a package on npm. Both SDKs are also open source and can be viewed on Github. Requirements This SDK is compatible with React Native version 0.64.0 and above. warning If you are using Flipper with React Native versions below 0.75.0 , SSE connections (which power real-time updates) will not work on Android unless Flipper is disabled. See this issue for more information. React Native Web To get your React Native Web working with DevCycle, you will need to change one of the rules in the webpack config to include .cjs files as one of the file types to be transpiled, e.g.: const createExpoWebpackConfigAsync = require ( '@expo/webpack-config' ) module . exports = async function ( env , argv ) { const config = await createExpoWebpackConfigAsync ( env , argv ) config . module . rules = config . module . rules . map ( ( rule ) => { if ( rule . oneOf instanceof Array ) { // add "cjs" as an exclusion to this rule to prevent it from being regarded as an asset rule . oneOf [ rule . oneOf . length - 1 ] . exclude = [ / \. ( js | mjs | jsx | cjs | ts | tsx ) $ / , / \. html $ / , / \. json $ / , ] } return rule } ) return config } For more information, see this Github issue. Edit this page Last updated on Jan 9, 2026 Previous OpenFeature Next Installation Requirements React Native Web DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:25 |
https://www.linkedin.com/posts/suprsend_hiring-activity-7399789920934060032-vC_g | #hiring | SuprSend Agree & Join LinkedIn By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Skip to main content LinkedIn Top Content People Learning Jobs Games Sign in Join now for free SuprSend’s Post SuprSend 19,129 followers 1mo Report this post We're #hiring a new Founders’ Office – Product Marketing in Bengaluru, Karnataka. Apply today or share this post with your network. Product Marketing Manager SuprSend, Bengaluru, Karnataka, India 9 1 Comment Like Comment Share Copy LinkedIn Facebook X Tanisha Sharma 1mo Report this comment Akshita Srivastava Like Reply 1 Reaction 2 Reactions To view or add a comment, sign in 19,129 followers View Profile Connect Explore content categories Career Productivity Finance Soft Skills & Emotional Intelligence Project Management Education Technology Leadership Ecommerce User Experience Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language Sign in to view more content Create your free account or sign in to continue your search Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . | 2026-01-13T08:48:25 |
https://docs.devcycle.com/sdk/#server-side-sdks | SDK Overview | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up SDK Overview SDK Lifecycle SDK Features Client-side SDKS Server-side SDKS SDK Proxy SDK Overview SDK Overview DevCycle has both client-side and server-side SDKs. This page describes the differences between these SDK types. Implementation and usage change depending on which type of SDK is being used. tip Explore our SDK Features and Functionality to discover how to implement your solutions using the DevCycle SDKs. Client Side SDKs DevCycle client-side SDKs are meant for single-user contexts, such as web browsers and mobile apps. These SDKs retrieve their configuration for the current user when they are initialized and any time the user is re-identified. They also receive updates in real time when configuration is changed in the DevCycle platform. The current Client-Side SDKs are: JavaScript SDK React SDK Next.js SDK Angular SDK iOS SDK Android SDK React Native SDK Flutter SDK Roku SDK Server-Side SDKs Server-side SDKs are used in multi-user contexts such as backend services, where each call to the SDK will likely be for a different user. The user's ID and any other targeting information must be passed in on every SDK function call. The current Server-Side SDKs are: NodeJS SDK NestJS SDK Go SDK PHP SDK Python SDK Ruby SDK Java SDK .NET SDK OpenFeature Providers OpenFeature is an open standard that provides a vendor-agnostic, community-driven SDKs for feature flagging that works natively with DevCycle. Client-Side JavaScript React Angular iOS Android Server-Side NodeJS NestJS Go Ruby Java .NET / C# Python PHP Edit this page Last updated on Jan 9, 2026 Next SDK Lifecycle DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:25 |
https://ruul.io/blog/mental-health-promotion-in-the-workplace?7c89d873_page=2 | Blog | For Freelancers, Creators, and Indie Professionals Product Payment Requests Get paid anywhere. Sell Services Make your services buyable Sell Products Create once sell forever Subscriptions Get paid on repeat Ruul Space Your personel storefront. One link for everything you offer. Learn more Pricing Resources Partner Programs Referral Program Get 1% for life. Seriously. Affiliate Program Bring users, get paid Partners Let’s grow together. More Blog About us Support Brand Kit For Customers Log in Sign up For Businesses Login Sign up grow 13 Best Fiverr Alternatives Freelancers Need to Know Read POPULAR ARTICLES How to Accept Online Payments: A Comprehensive Guide for Businesses and Freelancers Learn how to set up and manage secure online payment systems for your business or freelance work. Discover popular payment methods, integration tips, security measures, and best practices to streamline transactions and boost efficiency. Top 15 Digital Nomad Jobs in 2025 Explore the 15 best digital nomad jobs in 2025, from writing to coding—fully remote, high-paying, and travel-friendly. The Ultimate Best AI Tools for Freelancers: Boosting Productivity in 2025 Discover the ultimate AI tools for freelancers in 2025 to enhance productivity and efficiency. From writing and graphic design to project management, explore top AI tools like ChatGPT, Grammarly, Canva, and more. Start optimizing your freelancing. How to Accept Cryptocurrency Payments Find the methods, benefits, and security considerations for accepting crypto payments. Know how cryptocurrencies can open new opportunities for your business. What to Sell as a Digital Product Want to make money while you sleep? From AI art to ebooks and plugins, here’s what actually sells in 2025 and makes your wallet happy! Best 13 Motivational Apps and Techniques You Need As You Work Solo Lack of motivation as an independent? See these motivation apps and techniques. get paid sell grow work news trends get paid sell grow work news trends How to Make Freelance Money I’ve mapped out the freelance income paths that will stick around until 2030. Shared all the pro tips and details in this post. Come check it out! Introducing MiniPay on Ruul: Faster Stablecoin Payment Ruul & MiniPay now bring instant, stablecoin payments with zero withdrawal fee for freelancers. Create virtual USD/EUR accounts, enjoy fast global transfers, and earn up to $275 in bonuses. Best Freelancing Websites Struggling to pick a freelancing website? These 16 categorized freelancing platforms will save your time, energy, and maybe your sanity! How to Get Paid as a Freelancer Don't let payments ruin your business! We've covered everything from the most important steps to the best methods! Designer's Guide to Dribbble All the potential Dribbble has to offer, and all the areas where it leaves you hanging. This Guide gives you all of that and more. Best Freelance Jobs You're looking for the best freelance jobs AI won't wipe out. Safe, in-demand, future-ready, long-lasting work… you'll find it all right here. MORE THAN 120,000 Independents Over 120,000 independents trust Ruul to sell their services, digital products, and securely manage their payments. FROM 190 Countries Truly global coverage: trusted across 190 countries with seamless payouts available in 140 currencies. PROCESSED $200m+ of Transactions Over $200M successfully processed, backed by an 8-year legacy of secure, reliable transactions trusted by independents worldwide. FREQUENTLY ASKED QUESTIONS Everything you need to know. Get clear, straightforward answers to the most common questions about using Ruul. hey@ruul.io What is Ruul? Ruul is a merchant-of-record platform helping freelancers and creators globally sell services, digital products, subscriptions, and easily get paid. Who is Ruul for? Ruul is designed for freelancers, creators, and independent professionals who want a simple way to sell online and get paid globally. How does Ruul work? Open an account, complete a quick verification (KYC), and link your payout account. Then, start selling through your store or send payment requests to customers instantly. How does pricing work? Signing up is free. There are no subscription or hidden fees. Ruul charges a small commission only when you sell or get paid through the platform. What is a Merchant of Record? A merchant of record is the legal seller responsible for processing payments, handling taxes, and managing compliance for each transaction. What can I sell on Ruul? You can sell services, digital products, license keys, online courses, subscriptions, and digital memberships. How do I get paid on Ruul? Add your preferred bank account, digital wallet, or receive payouts in stablecoins as crypto. Funds arrive within 24 hours after a payout is triggered. OPEN AN ACCOUNT START MAKING MONEY TODAY ruul.space/ Thank you! Your submission has been received! Oops! Something went wrong while submitting the form. Trustpilot Product Payment Requests Sell Services Sell Products Subscriptions Ruul Space Pricing For Businesses Resources Blog About Contact Support Referral Program Affiliate Program Partner Program Tools Invoice Generator NDA Generator Service Agreement Generator Freelancer Hourly Rate Calculator All Rights Reserved © 2025 Terms Of Use Privacy Policy | 2026-01-13T08:48:25 |
https://www.youtube.com/watch?v=pQk7wUP4k-U | Avoid the "Undocumented Pipes" problem by slicing your work - YouTube 정보 보도자료 저작권 문의하기 크리에이터 광고 개발자 약관 개인정보처리방침 정책 및 안전 YouTube 작동의 원리 새로운 기능 테스트하기 © 2026 Google LLC, Sundar Pichai, 1600 Amphitheatre Parkway, Mountain View CA 94043, USA, 0807-882-594 (무료), yt-support-solutions-kr@google.com, 호스팅: Google LLC, 사업자정보 , 불법촬영물 신고 크리에이터들이 유튜브 상에 게시, 태그 또는 추천한 상품들은 판매자들의 약관에 따라 판매됩니다. 유튜브는 이러한 제품들을 판매하지 않으며, 그에 대한 책임을 지지 않습니다. var ytInitialData = {"responseContext":{"visitorData":"CgsxRDJUWldualRRcyjVjZjLBjIKCgJLUhIEGgAgQIIB3wIv7w47NzdN0lmksqyIIHSPlOt9m0yB10kxThfpAuMWCA6yVc75sQCwjZ2bGsgehJkL_9YPNymDuGD-zBLDK5lzlp4ldBLLB7KuXMMDrhMwxq1Sneonf-4xVpTttc-0m-yDb0kP3njA2XZpjyLkZjZtLEygnShXulpJsz0-ScbC7Oj10nnn_6D1zF3lzp3sYK2BRe96-VMOnzxXVEn6q80tQgq12G3y0G-C3jrYs-W7bQPUPERjZBy6j_m8dhjBM5N4wVsBvRY3zpyMTurW_hMV2hupqDEc2uk1jlDOwqDw8T2XNC4R3mW1BVyPapFIjsBnwUfiHe5AfQdLWdCipnYk-vap9O4xepWSwJ915U5h4yQ0DQJjP6YyU3kG0TgDaB0hS4Pyb3jeMCZe2DXRo7Byi5xS_sdB231zotJ4tHNXqTNSMA3ONWUtfDT7M-w4Yif7S4adu7wfbtVUs2qsNRw%3D","serviceTrackingParams":[{"service":"CSI","params":[{"key":"c","value":"WEB"},{"key":"cver","value":"2.20260109.01.00"},{"key":"yt_li","value":"0"},{"key":"GetWatchNext_rid","value":"0x50ec338b83ee2c6d"}]},{"service":"GFEEDBACK","params":[{"key":"logged_in","value":"0"},{"key":"visitor_data","value":"CgsxRDJUWldualRRcyjUjZjLBjIKCgJLUhIEGgAgQA%3D%3D"}]},{"service":"GUIDED_HELP","params":[{"key":"logged_in","value":"0"}]},{"service":"ECATCHER","params":[{"key":"client.version","value":"2.20260109"},{"key":"client.name","value":"WEB"}]}],"mainAppWebResponseContext":{"loggedOut":true,"trackingParam":"kx_fmPxhoPZRfCEDwct8wscfv7aVkTyHnSMpPhiN0v83H6HRgkussh7BwOcCE59TDtslLKPQ-SS"},"webResponseContextExtensionData":{"webResponseContextPreloadData":{"preloadMessageNames":["twoColumnWatchNextResults","results","videoPrimaryInfoRenderer","videoViewCountRenderer","menuRenderer","menuServiceItemRenderer","segmentedLikeDislikeButtonViewModel","likeButtonViewModel","toggleButtonViewModel","buttonViewModel","modalWithTitleAndButtonRenderer","buttonRenderer","dislikeButtonViewModel","unifiedSharePanelRenderer","menuFlexibleItemRenderer","videoSecondaryInfoRenderer","videoOwnerRenderer","subscribeButtonRenderer","subscriptionNotificationToggleButtonRenderer","menuPopupRenderer","confirmDialogRenderer","metadataRowContainerRenderer","compositeVideoPrimaryInfoRenderer","itemSectionRenderer","continuationItemRenderer","secondaryResults","lockupViewModel","thumbnailViewModel","thumbnailOverlayBadgeViewModel","thumbnailBadgeViewModel","thumbnailHoverOverlayToggleActionsViewModel","lockupMetadataViewModel","decoratedAvatarViewModel","avatarViewModel","contentMetadataViewModel","sheetViewModel","listViewModel","listItemViewModel","badgeViewModel","avatarStackViewModel","dialogViewModel","dialogHeaderViewModel","autoplay","playerOverlayRenderer","menuNavigationItemRenderer","watchNextEndScreenRenderer","endScreenVideoRenderer","thumbnailOverlayTimeStatusRenderer","thumbnailOverlayNowPlayingRenderer","playerOverlayAutoplayRenderer","playerOverlayVideoDetailsRenderer","autoplaySwitchButtonRenderer","quickActionsViewModel","decoratedPlayerBarRenderer","multiMarkersPlayerBarRenderer","markerRenderer","chapterRenderer","notificationActionRenderer","speedmasterEduViewModel","engagementPanelSectionListRenderer","engagementPanelTitleHeaderRenderer","sortFilterSubMenuRenderer","sectionListRenderer","adsEngagementPanelContentRenderer","chipBarViewModel","chipViewModel","macroMarkersListRenderer","macroMarkersListItemRenderer","toggleButtonRenderer","structuredDescriptionContentRenderer","videoDescriptionHeaderRenderer","factoidRenderer","viewCountFactoidRenderer","expandableVideoDescriptionBodyRenderer","horizontalCardListRenderer","richListHeaderRenderer","videoDescriptionCourseSectionRenderer","structuredDescriptionPlaylistLockupRenderer","thumbnailOverlayBottomPanelRenderer","topicLinkRenderer","videoDescriptionTranscriptSectionRenderer","videoDescriptionInfocardsSectionRenderer","desktopTopbarRenderer","topbarLogoRenderer","fusionSearchboxRenderer","topbarMenuButtonRenderer","multiPageMenuRenderer","hotkeyDialogRenderer","hotkeyDialogSectionRenderer","hotkeyDialogSectionOptionRenderer","voiceSearchDialogRenderer","cinematicContainerRenderer"]},"ytConfigData":{"visitorData":"CgsxRDJUWldualRRcyjUjZjLBjIKCgJLUhIEGgAgQA%3D%3D","rootVisualElementType":3832},"webPrefetchData":{"navigationEndpoints":[{"clickTrackingParams":"CAAQg2ciEwiU0fbtkIiSAxWVQjgFHSOSPGcyDHJlbGF0ZWQtYXV0b0jlp-KflPjOhKUBmgEFCAMQ-B3KAQRT7Yr5","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=yVetSg_l-QI\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"yVetSg_l-QI","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwiU0fbtkIiSAxWVQjgFHSOSPGcyDHJlbGF0ZWQtYXV0b0jlp-KflPjOhKUBmgEFCAMQ-B3KAQRT7Yr5","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=yVetSg_l-QI\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"yVetSg_l-QI","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwiU0fbtkIiSAxWVQjgFHSOSPGcyDHJlbGF0ZWQtYXV0b0jlp-KflPjOhKUBmgEFCAMQ-B3KAQRT7Yr5","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=yVetSg_l-QI\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"yVetSg_l-QI","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}}]},"hasDecorated":true}},"contents":{"twoColumnWatchNextResults":{"results":{"results":{"contents":[{"videoPrimaryInfoRenderer":{"title":{"runs":[{"text":"Avoid the \"Undocumented Pipes\" problem by slicing your work"}]},"viewCount":{"videoViewCountRenderer":{"viewCount":{"simpleText":"조회수 63회"},"shortViewCount":{"simpleText":"조회수 63회"},"originalViewCount":"0"}},"videoActions":{"menuRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"runs":[{"text":"신고"}]},"icon":{"iconType":"FLAG"},"serviceEndpoint":{"clickTrackingParams":"CMkCELW0CRgAIhMIlNH27ZCIkgMVlUI4BR0jkjxnygEEU-2K-Q==","showEngagementPanelEndpoint":{"identifier":{"tag":"PAabuse_report"},"globalConfiguration":{"params":"qgdxCAESC3BRazd3VVA0ay1VGmBFZ3R3VVdzM2QxVlFOR3N0VlVBQldBQjRCWklCTWdvd0VpNW9kSFJ3Y3pvdkwya3VlWFJwYldjdVkyOXRMM1pwTDNCUmF6ZDNWVkEwYXkxVkwyUmxabUYxYkhRdWFuQm4%3D"},"engagementPanelPresentationConfigs":{"engagementPanelPopupPresentationConfig":{"popupType":"PANEL_POPUP_TYPE_DIALOG"}}}},"trackingParams":"CMkCELW0CRgAIhMIlNH27ZCIkgMVlUI4BR0jkjxn"}}],"trackingParams":"CMkCELW0CRgAIhMIlNH27ZCIkgMVlUI4BR0jkjxn","topLevelButtons":[{"segmentedLikeDislikeButtonViewModel":{"likeButtonViewModel":{"likeButtonViewModel":{"toggleButtonViewModel":{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"LIKE","title":"2","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CNQCEKVBIhMIlNH27ZCIkgMVlUI4BR0jkjxn"}},{"innertubeCommand":{"clickTrackingParams":"CNQCEKVBIhMIlNH27ZCIkgMVlUI4BR0jkjxnygEEU-2K-Q==","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"동영상이 마음에 드시나요?"},"content":{"simpleText":"로그인하여 의견을 알려주세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CNUCEPqGBCITCJTR9u2QiJIDFZVCOAUdI5I8Z8oBBFPtivk=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko\u0026ec=66426","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CNUCEPqGBCITCJTR9u2QiJIDFZVCOAUdI5I8Z8oBBFPtivk=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/like"}},"likeEndpoint":{"status":"LIKE","target":{"videoId":"pQk7wUP4k-U"},"likeParams":"Cg0KC3BRazd3VVA0ay1VIAAyDAjVjZjLBhCS7KnyAQ%3D%3D"}},"idamTag":"66426"}},"trackingParams":"CNUCEPqGBCITCJTR9u2QiJIDFZVCOAUdI5I8Zw=="}}}}}}}]}},"accessibilityText":"다른 사용자 2명과 함께 이 동영상에 좋아요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CNQCEKVBIhMIlNH27ZCIkgMVlUI4BR0jkjxn","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.like.button","tooltip":"이 동영상이 마음에 듭니다."}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"LIKE","title":"3","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CNMCEKVBIhMIlNH27ZCIkgMVlUI4BR0jkjxn"}},{"innertubeCommand":{"clickTrackingParams":"CNMCEKVBIhMIlNH27ZCIkgMVlUI4BR0jkjxnygEEU-2K-Q==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/removelike"}},"likeEndpoint":{"status":"INDIFFERENT","target":{"videoId":"pQk7wUP4k-U"},"removeLikeParams":"Cg0KC3BRazd3VVA0ay1VGAAqDAjVjZjLBhDX36ryAQ%3D%3D"}}}]}},"accessibilityText":"다른 사용자 2명과 함께 이 동영상에 좋아요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CNMCEKVBIhMIlNH27ZCIkgMVlUI4BR0jkjxn","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.like.button","tooltip":"좋아요 취소"}},"identifier":"watch-like","trackingParams":"CMkCELW0CRgAIhMIlNH27ZCIkgMVlUI4BR0jkjxn","isTogglingDisabled":true}},"likeStatusEntityKey":"EgtwUWs3d1VQNGstVSA-KAE%3D","likeStatusEntity":{"key":"EgtwUWs3d1VQNGstVSA-KAE%3D","likeStatus":"INDIFFERENT"}}},"dislikeButtonViewModel":{"dislikeButtonViewModel":{"toggleButtonViewModel":{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"DISLIKE","title":"싫어요","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CNECEKiPCSITCJTR9u2QiJIDFZVCOAUdI5I8Zw=="}},{"innertubeCommand":{"clickTrackingParams":"CNECEKiPCSITCJTR9u2QiJIDFZVCOAUdI5I8Z8oBBFPtivk=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"동영상이 마음에 안 드시나요?"},"content":{"simpleText":"로그인하여 의견을 알려주세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CNICEPmGBCITCJTR9u2QiJIDFZVCOAUdI5I8Z8oBBFPtivk=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko\u0026ec=66425","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CNICEPmGBCITCJTR9u2QiJIDFZVCOAUdI5I8Z8oBBFPtivk=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/dislike"}},"likeEndpoint":{"status":"DISLIKE","target":{"videoId":"pQk7wUP4k-U"},"dislikeParams":"Cg0KC3BRazd3VVA0ay1VEAAiDAjVjZjLBhDHrqzyAQ%3D%3D"}},"idamTag":"66425"}},"trackingParams":"CNICEPmGBCITCJTR9u2QiJIDFZVCOAUdI5I8Zw=="}}}}}}}]}},"accessibilityText":"동영상에 싫어요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CNECEKiPCSITCJTR9u2QiJIDFZVCOAUdI5I8Zw==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.dislike.button","tooltip":"이 동영상이 마음에 들지 않습니다."}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"DISLIKE","title":"싫어요","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CNACEKiPCSITCJTR9u2QiJIDFZVCOAUdI5I8Zw=="}},{"innertubeCommand":{"clickTrackingParams":"CNACEKiPCSITCJTR9u2QiJIDFZVCOAUdI5I8Z8oBBFPtivk=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/removelike"}},"likeEndpoint":{"status":"INDIFFERENT","target":{"videoId":"pQk7wUP4k-U"},"removeLikeParams":"Cg0KC3BRazd3VVA0ay1VGAAqDAjVjZjLBhD21KzyAQ%3D%3D"}}}]}},"accessibilityText":"동영상에 싫어요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CNACEKiPCSITCJTR9u2QiJIDFZVCOAUdI5I8Zw==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.dislike.button","tooltip":"이 동영상이 마음에 들지 않습니다."}},"trackingParams":"CMkCELW0CRgAIhMIlNH27ZCIkgMVlUI4BR0jkjxn","isTogglingDisabled":true}},"dislikeEntityKey":"EgtwUWs3d1VQNGstVSA-KAE%3D"}},"iconType":"LIKE_ICON_TYPE_UNKNOWN","likeCountEntity":{"key":"unset_like_count_entity_key"},"dynamicLikeCountUpdateData":{"updateStatusKey":"like_count_update_status_key","placeholderLikeCountValuesKey":"like_count_placeholder_values_key","updateDelayLoopId":"like_count_update_delay_loop_id","updateDelaySec":5},"teasersOrderEntityKey":"EgtwUWs3d1VQNGstVSD8AygB"}},{"buttonViewModel":{"iconName":"SHARE","title":"공유","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CM4CEOWWARgDIhMIlNH27ZCIkgMVlUI4BR0jkjxn"}},{"innertubeCommand":{"clickTrackingParams":"CM4CEOWWARgDIhMIlNH27ZCIkgMVlUI4BR0jkjxnygEEU-2K-Q==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/share/get_share_panel"}},"shareEntityServiceEndpoint":{"serializedShareEntity":"CgtwUWs3d1VQNGstVaABAQ%3D%3D","commands":[{"clickTrackingParams":"CM4CEOWWARgDIhMIlNH27ZCIkgMVlUI4BR0jkjxnygEEU-2K-Q==","openPopupAction":{"popup":{"unifiedSharePanelRenderer":{"trackingParams":"CM8CEI5iIhMIlNH27ZCIkgMVlUI4BR0jkjxn","showLoadingSpinner":true}},"popupType":"DIALOG","beReused":true}}]}}}]}},"accessibilityText":"공유","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CM4CEOWWARgDIhMIlNH27ZCIkgMVlUI4BR0jkjxn","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE","accessibilityId":"id.video.share.button","tooltip":"공유"}}],"accessibility":{"accessibilityData":{"label":"추가 작업"}},"flexibleItems":[{"menuFlexibleItemRenderer":{"menuItem":{"menuServiceItemRenderer":{"text":{"runs":[{"text":"저장"}]},"icon":{"iconType":"PLAYLIST_ADD"},"serviceEndpoint":{"clickTrackingParams":"CMwCEOuQCSITCJTR9u2QiJIDFZVCOAUdI5I8Z8oBBFPtivk=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"runs":[{"text":"나중에 다시 보고 싶으신가요?"}]},"content":{"runs":[{"text":"로그인하여 동영상을 재생목록에 추가하세요."}]},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CM0CEPuGBCITCJTR9u2QiJIDFZVCOAUdI5I8Z8oBBFPtivk=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253DpQk7wUP4k-U\u0026hl=ko\u0026ec=66427","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CM0CEPuGBCITCJTR9u2QiJIDFZVCOAUdI5I8Z8oBBFPtivk=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=pQk7wUP4k-U","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"pQk7wUP4k-U","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr2---sn-ab02a0nfpgxapox-bh2zs.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=a5093bc143f893e5\u0026ip=1.208.108.242\u0026initcwndbps=3783750\u0026mt=1768293662\u0026oweuc="}}}}},"idamTag":"66427"}},"trackingParams":"CM0CEPuGBCITCJTR9u2QiJIDFZVCOAUdI5I8Zw=="}}}}}},"trackingParams":"CMwCEOuQCSITCJTR9u2QiJIDFZVCOAUdI5I8Zw=="}},"topLevelButton":{"buttonViewModel":{"iconName":"PLAYLIST_ADD","title":"저장","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CMoCEOuQCSITCJTR9u2QiJIDFZVCOAUdI5I8Zw=="}},{"innertubeCommand":{"clickTrackingParams":"CMoCEOuQCSITCJTR9u2QiJIDFZVCOAUdI5I8Z8oBBFPtivk=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"runs":[{"text":"나중에 다시 보고 싶으신가요?"}]},"content":{"runs":[{"text":"로그인하여 동영상을 재생목록에 추가하세요."}]},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CMsCEPuGBCITCJTR9u2QiJIDFZVCOAUdI5I8Z8oBBFPtivk=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253DpQk7wUP4k-U\u0026hl=ko\u0026ec=66427","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CMsCEPuGBCITCJTR9u2QiJIDFZVCOAUdI5I8Z8oBBFPtivk=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=pQk7wUP4k-U","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"pQk7wUP4k-U","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr2---sn-ab02a0nfpgxapox-bh2zs.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=a5093bc143f893e5\u0026ip=1.208.108.242\u0026initcwndbps=3783750\u0026mt=1768293662\u0026oweuc="}}}}},"idamTag":"66427"}},"trackingParams":"CMsCEPuGBCITCJTR9u2QiJIDFZVCOAUdI5I8Zw=="}}}}}}}]}},"accessibilityText":"재생목록에 저장","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CMoCEOuQCSITCJTR9u2QiJIDFZVCOAUdI5I8Zw==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","tooltip":"저장"}}}}]}},"trackingParams":"CMkCELW0CRgAIhMIlNH27ZCIkgMVlUI4BR0jkjxn","superTitleLink":{"runs":[{"text":"The Agile in Action Podcast with Bill Raymond","navigationEndpoint":{"clickTrackingParams":"CMkCELW0CRgAIhMIlNH27ZCIkgMVlUI4BR0jkjxnygEEU-2K-Q==","commandMetadata":{"webCommandMetadata":{"url":"/playlist?list=PLWzwUIYZpnJsGnFUCmugOjrxYFOFNF93B","webPageType":"WEB_PAGE_TYPE_PLAYLIST","rootVe":5754,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"VLPLWzwUIYZpnJsGnFUCmugOjrxYFOFNF93B"}}}]},"dateText":{"simpleText":"2024. 3. 12."},"relativeDateText":{"accessibility":{"accessibilityData":{"label":"1년 전"}},"simpleText":"1년 전"}}},{"videoSecondaryInfoRenderer":{"owner":{"videoOwnerRenderer":{"thumbnail":{"thumbnails":[{"url":"https://yt3.ggpht.com/Kx10MJpTTnibt84kypAQ4RQ8f59LH8P4O7c5dWqB6yzXK2gvRvNs6oKWqrVihGUJaXWPBHQITw=s48-c-k-c0x00ffffff-no-rj","width":48,"height":48},{"url":"https://yt3.ggpht.com/Kx10MJpTTnibt84kypAQ4RQ8f59LH8P4O7c5dWqB6yzXK2gvRvNs6oKWqrVihGUJaXWPBHQITw=s88-c-k-c0x00ffffff-no-rj","width":88,"height":88},{"url":"https://yt3.ggpht.com/Kx10MJpTTnibt84kypAQ4RQ8f59LH8P4O7c5dWqB6yzXK2gvRvNs6oKWqrVihGUJaXWPBHQITw=s176-c-k-c0x00ffffff-no-rj","width":176,"height":176}]},"title":{"runs":[{"text":"Bill Raymond","navigationEndpoint":{"clickTrackingParams":"CMgCEOE5IhMIlNH27ZCIkgMVlUI4BR0jkjxnygEEU-2K-Q==","commandMetadata":{"webCommandMetadata":{"url":"/@bill-raymond","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCo63gWfWRfEciJ98mJLIU0Q","canonicalBaseUrl":"/@bill-raymond"}}}]},"subscriptionButton":{"type":"FREE"},"navigationEndpoint":{"clickTrackingParams":"CMgCEOE5IhMIlNH27ZCIkgMVlUI4BR0jkjxnygEEU-2K-Q==","commandMetadata":{"webCommandMetadata":{"url":"/@bill-raymond","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCo63gWfWRfEciJ98mJLIU0Q","canonicalBaseUrl":"/@bill-raymond"}},"subscriberCountText":{"accessibility":{"accessibilityData":{"label":"구독자 7.01천명"}},"simpleText":"구독자 7.01천명"},"trackingParams":"CMgCEOE5IhMIlNH27ZCIkgMVlUI4BR0jkjxn"}},"subscribeButton":{"subscribeButtonRenderer":{"buttonText":{"runs":[{"text":"구독"}]},"subscribed":false,"enabled":true,"type":"FREE","channelId":"UCo63gWfWRfEciJ98mJLIU0Q","showPreferences":false,"subscribedButtonText":{"runs":[{"text":"구독중"}]},"unsubscribedButtonText":{"runs":[{"text":"구독"}]},"trackingParams":"CLkCEJsrIhMIlNH27ZCIkgMVlUI4BR0jkjxnKPgdMgV3YXRjaA==","unsubscribeButtonText":{"runs":[{"text":"구독 취소"}]},"subscribeAccessibility":{"accessibilityData":{"label":"Bill Raymond을(를) 구독합니다."}},"unsubscribeAccessibility":{"accessibilityData":{"label":"Bill Raymond을(를) 구독 취소합니다."}},"notificationPreferenceButton":{"subscriptionNotificationToggleButtonRenderer":{"states":[{"stateId":3,"nextStateId":3,"state":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"icon":{"iconType":"NOTIFICATIONS_NONE"},"accessibility":{"label":"현재 설정은 맞춤설정 알림 수신입니다. Bill Raymond 채널의 알림 설정을 변경하려면 탭하세요."},"trackingParams":"CMcCEPBbIhMIlNH27ZCIkgMVlUI4BR0jkjxn","accessibilityData":{"accessibilityData":{"label":"현재 설정은 맞춤설정 알림 수신입니다. Bill Raymond 채널의 알림 설정을 변경하려면 탭하세요."}}}}},{"stateId":0,"nextStateId":0,"state":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"icon":{"iconType":"NOTIFICATIONS_OFF"},"accessibility":{"label":"현재 설정은 알림 수신 안함입니다. Bill Raymond 채널의 알림 설정을 변경하려면 탭하세요."},"trackingParams":"CMYCEPBbIhMIlNH27ZCIkgMVlUI4BR0jkjxn","accessibilityData":{"accessibilityData":{"label":"현재 설정은 알림 수신 안함입니다. Bill Raymond 채널의 알림 설정을 변경하려면 탭하세요."}}}}}],"currentStateId":3,"trackingParams":"CL8CEJf5ASITCJTR9u2QiJIDFZVCOAUdI5I8Zw==","command":{"clickTrackingParams":"CL8CEJf5ASITCJTR9u2QiJIDFZVCOAUdI5I8Z8oBBFPtivk=","commandExecutorCommand":{"commands":[{"clickTrackingParams":"CL8CEJf5ASITCJTR9u2QiJIDFZVCOAUdI5I8Z8oBBFPtivk=","openPopupAction":{"popup":{"menuPopupRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"simpleText":"맞춤설정"},"icon":{"iconType":"NOTIFICATIONS_NONE"},"serviceEndpoint":{"clickTrackingParams":"CMUCEOy1BBgDIhMIlNH27ZCIkgMVlUI4BR0jkjxnMhJQUkVGRVJFTkNFX0RFRkFVTFTKAQRT7Yr5","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/notification/modify_channel_preference"}},"modifyChannelNotificationPreferenceEndpoint":{"params":"ChhVQ282M2dXZldSZkVjaUo5OG1KTElVMFESAggBGAAgBFITCgIIAxILcFFrN3dVUDRrLVUYAA%3D%3D"}},"trackingParams":"CMUCEOy1BBgDIhMIlNH27ZCIkgMVlUI4BR0jkjxn","isSelected":true}},{"menuServiceItemRenderer":{"text":{"simpleText":"없음"},"icon":{"iconType":"NOTIFICATIONS_OFF"},"serviceEndpoint":{"clickTrackingParams":"CMQCEO21BBgEIhMIlNH27ZCIkgMVlUI4BR0jkjxnMhtQUkVGRVJFTkNFX05PX05PVElGSUNBVElPTlPKAQRT7Yr5","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/notification/modify_channel_preference"}},"modifyChannelNotificationPreferenceEndpoint":{"params":"ChhVQ282M2dXZldSZkVjaUo5OG1KTElVMFESAggDGAAgBFITCgIIAxILcFFrN3dVUDRrLVUYAA%3D%3D"}},"trackingParams":"CMQCEO21BBgEIhMIlNH27ZCIkgMVlUI4BR0jkjxn","isSelected":false}},{"menuServiceItemRenderer":{"text":{"runs":[{"text":"구독 취소"}]},"icon":{"iconType":"PERSON_MINUS"},"serviceEndpoint":{"clickTrackingParams":"CMACENuLChgFIhMIlNH27ZCIkgMVlUI4BR0jkjxnygEEU-2K-Q==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CMACENuLChgFIhMIlNH27ZCIkgMVlUI4BR0jkjxnygEEU-2K-Q==","openPopupAction":{"popup":{"confirmDialogRenderer":{"trackingParams":"CMECEMY4IhMIlNH27ZCIkgMVlUI4BR0jkjxn","dialogMessages":[{"runs":[{"text":"Bill Raymond"},{"text":" 구독을 취소하시겠습니까?"}]}],"confirmButton":{"buttonRenderer":{"style":"STYLE_BLUE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"구독 취소"}]},"serviceEndpoint":{"clickTrackingParams":"CMMCEPBbIhMIlNH27ZCIkgMVlUI4BR0jkjxnMgV3YXRjaMoBBFPtivk=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/unsubscribe"}},"unsubscribeEndpoint":{"channelIds":["UCo63gWfWRfEciJ98mJLIU0Q"],"params":"CgIIAxILcFFrN3dVUDRrLVUYAA%3D%3D"}},"accessibility":{"label":"구독 취소"},"trackingParams":"CMMCEPBbIhMIlNH27ZCIkgMVlUI4BR0jkjxn"}},"cancelButton":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"취소"}]},"accessibility":{"label":"취소"},"trackingParams":"CMICEPBbIhMIlNH27ZCIkgMVlUI4BR0jkjxn"}},"primaryIsCancel":false}},"popupType":"DIALOG"}}]}},"trackingParams":"CMACENuLChgFIhMIlNH27ZCIkgMVlUI4BR0jkjxn"}}]}},"popupType":"DROPDOWN"}}]}},"targetId":"notification-bell","secondaryIcon":{"iconType":"EXPAND_MORE"}}},"targetId":"watch-subscribe","signInEndpoint":{"clickTrackingParams":"CLkCEJsrIhMIlNH27ZCIkgMVlUI4BR0jkjxnygEEU-2K-Q==","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"채널을 구독하시겠습니까?"},"content":{"simpleText":"채널을 구독하려면 로그인하세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CL4CEP2GBCITCJTR9u2QiJIDFZVCOAUdI5I8ZzIJc3Vic2NyaWJlygEEU-2K-Q==","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253DpQk7wUP4k-U%26continue_action%3DQUFFLUhqbWQ3d0xHRVlGTEh1akwxNjBKeDhBNjFwUVhKZ3xBQ3Jtc0ttY2Jqa1ktaHhvOVg0Y19JX0tHUzZjaDFGMnpwajlCX3FZQXI2SlhndmozWS14c3doX0JBWWRINWFwazd6eGpWVlFPSlJ6ZDliNlA5QUU1ZThiMGJlYUJpdmFqS3RlQ1NRVTR2RFE0YUo2TXlTS1IwbnNvVjg3d1N5bjNETFdyWklIczNjZm1lZWlDLTVPZ0NXdkZyS1h3QU1wNkY4MnR3aEQ1QmVBNXFTODJEZkxCT2ttTVBzT2w3MFFjVHM3bFdjQWlubS0\u0026hl=ko\u0026ec=66429","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CL4CEP2GBCITCJTR9u2QiJIDFZVCOAUdI5I8Z8oBBFPtivk=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=pQk7wUP4k-U","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"pQk7wUP4k-U","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr2---sn-ab02a0nfpgxapox-bh2zs.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=a5093bc143f893e5\u0026ip=1.208.108.242\u0026initcwndbps=3783750\u0026mt=1768293662\u0026oweuc="}}}}},"continueAction":"QUFFLUhqbWQ3d0xHRVlGTEh1akwxNjBKeDhBNjFwUVhKZ3xBQ3Jtc0ttY2Jqa1ktaHhvOVg0Y19JX0tHUzZjaDFGMnpwajlCX3FZQXI2SlhndmozWS14c3doX0JBWWRINWFwazd6eGpWVlFPSlJ6ZDliNlA5QUU1ZThiMGJlYUJpdmFqS3RlQ1NRVTR2RFE0YUo2TXlTS1IwbnNvVjg3d1N5bjNETFdyWklIczNjZm1lZWlDLTVPZ0NXdkZyS1h3QU1wNkY4MnR3aEQ1QmVBNXFTODJEZkxCT2ttTVBzT2w3MFFjVHM3bFdjQWlubS0","idamTag":"66429"}},"trackingParams":"CL4CEP2GBCITCJTR9u2QiJIDFZVCOAUdI5I8Zw=="}}}}}},"subscribedEntityKey":"EhhVQ282M2dXZldSZkVjaUo5OG1KTElVMFEgMygB","onSubscribeEndpoints":[{"clickTrackingParams":"CLkCEJsrIhMIlNH27ZCIkgMVlUI4BR0jkjxnKPgdMgV3YXRjaMoBBFPtivk=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/subscribe"}},"subscribeEndpoint":{"channelIds":["UCo63gWfWRfEciJ98mJLIU0Q"],"params":"EgIIAxgAIgtwUWs3d1VQNGstVQ%3D%3D"}}],"onUnsubscribeEndpoints":[{"clickTrackingParams":"CLkCEJsrIhMIlNH27ZCIkgMVlUI4BR0jkjxnygEEU-2K-Q==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CLkCEJsrIhMIlNH27ZCIkgMVlUI4BR0jkjxnygEEU-2K-Q==","openPopupAction":{"popup":{"confirmDialogRenderer":{"trackingParams":"CLsCEMY4IhMIlNH27ZCIkgMVlUI4BR0jkjxn","dialogMessages":[{"runs":[{"text":"Bill Raymond"},{"text":" 구독을 취소하시겠습니까?"}]}],"confirmButton":{"buttonRenderer":{"style":"STYLE_BLUE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"구독 취소"}]},"serviceEndpoint":{"clickTrackingParams":"CL0CEPBbIhMIlNH27ZCIkgMVlUI4BR0jkjxnKPgdMgV3YXRjaMoBBFPtivk=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/unsubscribe"}},"unsubscribeEndpoint":{"channelIds":["UCo63gWfWRfEciJ98mJLIU0Q"],"params":"CgIIAxILcFFrN3dVUDRrLVUYAA%3D%3D"}},"accessibility":{"label":"구독 취소"},"trackingParams":"CL0CEPBbIhMIlNH27ZCIkgMVlUI4BR0jkjxn"}},"cancelButton":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"취소"}]},"accessibility":{"label":"취소"},"trackingParams":"CLwCEPBbIhMIlNH27ZCIkgMVlUI4BR0jkjxn"}},"primaryIsCancel":false}},"popupType":"DIALOG"}}]}}],"timedAnimationData":{"animationTiming":[2186040],"macroMarkersIndex":[0],"animationDurationSecs":1.5,"borderStrokeThicknessDp":2,"borderOpacity":1,"fillOpacity":0,"trackingParams":"CLoCEPBbIhMIlNH27ZCIkgMVlUI4BR0jkjxn","animationOrigin":"ANIMATION_ORIGIN_SMARTIMATION"}}},"metadataRowContainer":{"metadataRowContainerRenderer":{"collapsedItemCount":0,"trackingParams":"CLgCEM2rARgBIhMIlNH27ZCIkgMVlUI4BR0jkjxn"}},"showMoreText":{"simpleText":"...더보기"},"showLessText":{"simpleText":"간략히"},"trackingParams":"CLgCEM2rARgBIhMIlNH27ZCIkgMVlUI4BR0jkjxn","defaultExpanded":false,"descriptionCollapsedLines":3,"showMoreCommand":{"clickTrackingParams":"CLgCEM2rARgBIhMIlNH27ZCIkgMVlUI4BR0jkjxnygEEU-2K-Q==","commandExecutorCommand":{"commands":[{"clickTrackingParams":"CLgCEM2rARgBIhMIlNH27ZCIkgMVlUI4BR0jkjxnygEEU-2K-Q==","changeEngagementPanelVisibilityAction":{"targetId":"engagement-panel-structured-description","visibility":"ENGAGEMENT_PANEL_VISIBILITY_EXPANDED"}},{"clickTrackingParams":"CLgCEM2rARgBIhMIlNH27ZCIkgMVlUI4BR0jkjxnygEEU-2K-Q==","scrollToEngagementPanelCommand":{"targetId":"engagement-panel-structured-description"}}]}},"showLessCommand":{"clickTrackingParams":"CLgCEM2rARgBIhMIlNH27ZCIkgMVlUI4BR0jkjxnygEEU-2K-Q==","changeEngagementPanelVisibilityAction":{"targetId":"engagement-panel-structured-description","visibility":"ENGAGEMENT_PANEL_VISIBILITY_HIDDEN"}},"attributedDescription":{"content":"🍕 Slice up your project to deliver more value! 🎯\n\n👉 To contact Anton, read the transcript, listen to the audio, and much more, visit here: https://agileinaction.com/agile-in-ac...\n\nToday, Anton Skornyakov, Certified Scrum Trainer, co-founder, and managing director of Agile.coach, will help you navigate the complexities of delivering value in your projects, regardless of the industry.\n\nIn this episode, Anton and Bill Raymond dive into the art of slicing work into manageable pieces to deliver immediate value. Drawing from diverse examples like software development, house renovation, and public housing projects, we explore how agile principles can be applied in various contexts to enhance adaptability, risk management, and prioritization.\n\nIn this podcast, you will learn the following:\n\n✅ The importance of breaking down work into smaller, value-delivering pieces.\n\n✅ Strategies for prioritizing tasks to address risks and uncertainties.\n\n🎉 How to apply agile `principles beyond software development to achieve continuous improvement.\n\nChapters:\n\n00:00 Introducing Anton Skornyakov\n02:14 The concept of effective value delivery\n02:30 Illustrative story: Slicing work to renovate a house\n07:46 The Importance of adapting and learning from risks\n08:58 Practical ways to start slicing work\n25:56 Real-world example: Housing project\n32:18 Using the podcast as an example\n35:31 Conclusion and how to contact Anton Skornyakov","commandRuns":[{"startIndex":142,"length":40,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLgCEM2rARgBIhMIlNH27ZCIkgMVlUI4BR0jkjxnSOWn4p-U-M6EpQHKAQRT7Yr5","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbklld2NUSFZJeVQxYkh4VnQtYXZCQUhiN0UxUXxBQ3Jtc0tsaVdVRUNqV1dpNnRoa2hKVnBlY0dLX1A1cUJSVVVhRk9SN0VJdjdDN2VVZGQ3SkhtdlNEcFNXal9qZmZ3TU9yUFpPc1A2akV1ZVhaNnlVVjc5UDVMV096RWZKQUM2UENDZW1kbFhrZHhhMVFOZS12SQ\u0026q=https%3A%2F%2Fagileinaction.com%2Fagile-in-action-podcast%2F2024%2F03%2F12%2Favoid-the-undocumented-pipes-problem-by-slicing-your-work.html\u0026v=pQk7wUP4k-U","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbklld2NUSFZJeVQxYkh4VnQtYXZCQUhiN0UxUXxBQ3Jtc0tsaVdVRUNqV1dpNnRoa2hKVnBlY0dLX1A1cUJSVVVhRk9SN0VJdjdDN2VVZGQ3SkhtdlNEcFNXal9qZmZ3TU9yUFpPc1A2akV1ZVhaNnlVVjc5UDVMV096RWZKQUM2UENDZW1kbFhrZHhhMVFOZS12SQ\u0026q=https%3A%2F%2Fagileinaction.com%2Fagile-in-action-podcast%2F2024%2F03%2F12%2Favoid-the-undocumented-pipes-problem-by-slicing-your-work.html\u0026v=pQk7wUP4k-U","target":"TARGET_NEW_WINDOW","nofollow":true}}}},{"startIndex":1059,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLgCEM2rARgBIhMIlNH27ZCIkgMVlUI4BR0jkjxnygEEU-2K-Q==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=pQk7wUP4k-U","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"pQk7wUP4k-U","continuePlayback":true,"startTimeSeconds":0,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr2---sn-ab02a0nfpgxapox-bh2zs.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=a5093bc143f893e5\u0026ip=1.208.108.242\u0026initcwndbps=3783750\u0026mt=1768293662\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"0초"}}},{"startIndex":1094,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLgCEM2rARgBIhMIlNH27ZCIkgMVlUI4BR0jkjxnygEEU-2K-Q==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=pQk7wUP4k-U\u0026t=134s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"pQk7wUP4k-U","continuePlayback":true,"startTimeSeconds":134,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr2---sn-ab02a0nfpgxapox-bh2zs.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=a5093bc143f893e5\u0026ip=1.208.108.242\u0026osts=134\u0026initcwndbps=3783750\u0026mt=1768293662\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"2분 14초"}}},{"startIndex":1140,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLgCEM2rARgBIhMIlNH27ZCIkgMVlUI4BR0jkjxnygEEU-2K-Q==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=pQk7wUP4k-U\u0026t=150s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"pQk7wUP4k-U","continuePlayback":true,"startTimeSeconds":150,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr2---sn-ab02a0nfpgxapox-bh2zs.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=a5093bc143f893e5\u0026ip=1.208.108.242\u0026osts=150\u0026initcwndbps=3783750\u0026mt=1768293662\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"2분 30초"}}},{"startIndex":1199,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLgCEM2rARgBIhMIlNH27ZCIkgMVlUI4BR0jkjxnygEEU-2K-Q==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=pQk7wUP4k-U\u0026t=466s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"pQk7wUP4k-U","continuePlayback":true,"startTimeSeconds":466,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr2---sn-ab02a0nfpgxapox-bh2zs.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=a5093bc143f893e5\u0026ip=1.208.108.242\u0026osts=466\u0026initcwndbps=3783750\u0026mt=1768293662\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"7분 46초"}}},{"startIndex":1256,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLgCEM2rARgBIhMIlNH27ZCIkgMVlUI4BR0jkjxnygEEU-2K-Q==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=pQk7wUP4k-U\u0026t=538s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"pQk7wUP4k-U","continuePlayback":true,"startTimeSeconds":538,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr2---sn-ab02a0nfpgxapox-bh2zs.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=a5093bc143f893e5\u0026ip=1.208.108.242\u0026osts=538\u0026initcwndbps=3783750\u0026mt=1768293662\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"8분 58초"}}},{"startIndex":1299,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLgCEM2rARgBIhMIlNH27ZCIkgMVlUI4BR0jkjxnygEEU-2K-Q==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=pQk7wUP4k-U\u0026t=1556s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"pQk7wUP4k-U","continuePlayback":true,"startTimeSeconds":1556,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr2---sn-ab02a0nfpgxapox-bh2zs.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=a5093bc143f893e5\u0026ip=1.208.108.242\u0026osts=1556\u0026initcwndbps=3783750\u0026mt=1768293662\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"25분 56초"}}},{"startIndex":1341,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLgCEM2rARgBIhMIlNH27ZCIkgMVlUI4BR0jkjxnygEEU-2K-Q==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=pQk7wUP4k-U\u0026t=1938s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"pQk7wUP4k-U","continuePlayback":true,"startTimeSeconds":1938,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr2---sn-ab02a0nfpgxapox-bh2zs.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=a5093bc143f893e5\u0026ip=1.208.108.242\u0026osts=1938\u0026initcwndbps=3783750\u0026mt=1768293662\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"32분 18초"}}},{"startIndex":1379,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLgCEM2rARgBIhMIlNH27ZCIkgMVlUI4BR0jkjxnygEEU-2K-Q==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=pQk7wUP4k-U\u0026t=2131s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"pQk7wUP4k-U","continuePlayback":true,"startTimeSeconds":2131,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr2---sn-ab02a0nfpgxapox-bh2zs.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=a5093bc143f893e5\u0026ip=1.208.108.242\u0026osts=2131\u0026initcwndbps=3783750\u0026mt=1768293662\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"35분 31초"}}}],"styleRuns":[{"startIndex":0,"length":142,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":142,"length":40,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4282296063},{"key":"USER_INTERFACE_THEME_LIGHT","value":4278607828}]}},"fontFamilyName":"Roboto"},{"startIndex":182,"length":877,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":1059,"length":5,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4282296063},{"key":"USER_INTERFACE_THEME_LIGHT","value":4278607828}]}},"fontFamilyName":"Roboto"},{"startIndex":1064,"length":30,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":1094,"length":5,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4282296063},{"key":"USER_INTERFACE_THEME_LIGHT","value":4278607828}]}},"fontFamilyName":"Roboto"},{"startIndex":1099,"length":41,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":1140,"length":5,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4282296063},{"key":"USER_INTERFACE_THEME_LIGHT","value":4278607828}]}},"fontFamilyName":"Roboto"},{"startIndex":1145,"length":54,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":1199,"length":5,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4282296063},{"key":"USER_INTERFACE_THEME_LIGHT","value":4278607828}]}},"fontFamilyName":"Roboto"},{"startIndex":1204,"length":52,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":1256,"length":5,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4282296063},{"key":"USER_INTERFACE_THEME_LIGHT","value":4278607828}]}},"fontFamilyName":"Roboto"},{"startIndex":1261,"length":38,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":1299,"length":5,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4282296063},{"key":"USER_INTERFACE_THEME_LIGHT","value":4278607828}]}},"fontFamilyName":"Roboto"},{"startIndex":1304,"length":37,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":1341,"length":5,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4282296063},{"key":"USER_INTERFACE_THEME_LIGHT","value":4278607828}]}},"fontFamilyName":"Roboto"},{"startIndex":1346,"length":33,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":1379,"length":5,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4282296063},{"key":"USER_INTERFACE_THEME_LIGHT","value":4278607828}]}},"fontFamilyName":"Roboto"},{"startIndex":1384,"length":47,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"}]},"headerRuns":[{"startIndex":0,"length":142,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":142,"length":40,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":182,"length":877,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":1059,"length":5,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":1064,"length":30,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":1094,"length":5,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":1099,"length":41,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":1140,"length":5,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":1145,"length":54,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":1199,"length":5,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":1204,"length":52,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":1256,"length":5,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":1261,"length":38,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":1299,"length":5,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":1304,"length":37,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":1341,"length":5,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":1346,"length":33,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":1379,"length":5,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":1384,"length":47,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"}]}},{"compositeVideoPrimaryInfoRenderer":{}},{"itemSectionRenderer":{"contents":[{"continuationItemRenderer":{"trigger":"CONTINUATION_TRIGGER_ON_ITEM_SHOWN","continuationEndpoint":{"clickTrackingParams":"CLcCELsvGAMiEwiU0fbtkIiSAxWVQjgFHSOSPGfKAQRT7Yr5","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/next"}},"continuationCommand":{"token":"Eg0SC3BRazd3VVA0ay1VGAYyJSIRIgtwUWs3d1VQNGstVTAAeAJCEGNvbW1lbnRzLXNlY3Rpb24%3D","request":"CONTINUATION_REQUEST_TYPE_WATCH_NEXT"}}}}],"trackingParams":"CLcCELsvGAMiEwiU0fbtkIiSAxWVQjgFHSOSPGc=","sectionIdentifier":"comment-item-section","targetId":"comments-section"}}],"trackingParams":"CLYCELovIhMIlNH27ZCIkgMVlUI4BR0jkjxn"}},"secondaryResults":{"secondaryResults":{"results":[{"lockupViewModel":{"contentImage":{"thumbnailViewModel":{"image":{"sources":[{"url":"https://i.ytimg.com/vi/yVetSg_l-QI/hqdefault.jpg?sqp=-oaymwEiCKgBEF5IWvKriqkDFQgBFQAAAAAYASUAAMhCPQCAokN4AQ==\u0026rs=AOn4CLAS5av-zV0e4EW9AZaRHoB083LKjQ","width":168,"height":94},{"url":"https://i.ytimg.com/vi/yVetSg_l-QI/hqdefault.jpg?sqp=-oaymwEjCNACELwBSFryq4qpAxUIARUAAAAAGAElAADIQj0AgKJDeAE=\u0026rs=AOn4CLB4FwS1cnEYZ_M8U0p8kAm9S5Yzpw","width":336,"height":188}]},"overlays":[{"thumbnailOverlayBadgeViewModel":{"thumbnailBadges":[{"thumbnailBadgeViewModel":{"text":"30:22","badgeStyle":"THUMBNAIL_OVERLAY_BADGE_STYLE_DEFAULT","animationActivationTargetId":"yVetSg_l-QI","animationActivationEntityKey":"Eh8veW91dHViZS9hcHAvd2F0Y2gvcGxheWVyX3N0YXRlIMMCKAE%3D","lottieData":{"url":"https://www.gstatic.com/youtube/img/lottie/audio_in | 2026-01-13T08:48:25 |
https://www.linkedin.com/uas/login?fromSignIn=true&session_redirect=https%3A%2F%2Fwww.linkedin.com%2Fcompany%2Fsuprsend&trk=organization_guest_main-feed-card_ellipsis-menu-semaphore-sign-in-redirect&guestReportContentType=POST&_f=guest-reporting | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T08:48:25 |
https://docs.devcycle.com/integrations/google-analytics-4/ | Sending DevCycle Data as a Custom Event to Google Analytics 4 (GTM Specific) | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up On this page Sending DevCycle Data as a Custom Event to Google Analytics 4 (GTM Specific) Transition from Google Optimize This guide enables you to integrate DevCycle feature flags with Google Analytics 4 (GA4) for A/B testing and experimentation using Google Tag Manager (GTM). If you are a former Google Optimize customer transitioning to GA4, this guide is specific to GTM implementations. GTM Elements: Tags, Variables, and Triggers Below is a description of Google Tag Manager's tags, variables, and triggers. For more in-depth understanding, consult Google's official documentation . Tags execute specified functionality, such as sending data to GA4 or initializing DevCycle. Variables serve as placeholders for predefined values, which in this guide store the feature and variation data. Triggers are conditions that, when met, execute actions defined in Tags. Google Tag Manager (GTM) Configuration Step 1: Create a New Tag for DevCycle Initialization and Feature Flag Configuration Values Navigate to your GTM workspace and access the "Tags" section. Create a new tag and name it "DevCycle Initialization & Feature Flag Configuration Values". Choose "Custom HTML" for "Tag Configuration". Insert a script to push a custom event named set_user_properties (or any name of your choosing) to the dataLayer with the parameters: featureName: {{featureName}} and variation: {{variation}} . This script can be found below. < script > let user = { isAnonymous : true } ; let devcycleOptions = { logLevel : "debug" } ; let devcycleClient = DevCycle . initializeDevCycle ( "<SDK_KEY>" , // Replace with your specific DevCycle SDK Key user , devcycleOptions ) ; devcycleClient . onClientInitialized ( ) . then ( function ( ) { let features = devcycleClient . allFeatures ( ) ; pushData ( features ) ; } ) ; function pushData ( featuresConfig ) { let arr = [ ] ; // JSON to Array for ( let i in featuresConfig ) { arr . push ( [ i , featuresConfig [ i ] ] ) ; } // Push to dataLayer for ( let j = 0 ; j < arr . length ; j ++ ) { let featureName = arr [ j ] [ 0 ] . replaceAll ( "-" , "_" ) ; let currentVariation = arr [ j ] [ 1 ] [ "variationName" ] . replaceAll ( "-" , "_" ) ; window . dataLayer . push ( { event : "set_user_properties" , // Can be any event name you want featureName : featureName , variationName : currentVariation , } ) ; } } < / script > For “Triggering", select the “Window Loaded” option as the firing trigger. Step 2: Configure GTM Variables Navigate to the “Variable” section. In “User-Defined Variables", create a new variable. Choose “Data Layer Variable” for "Variable Type". Enter “featureName” for "Data Layer Variable Name". Repeat to create another variable and name it “variationName". Step 3: Create Tag to Send Custom Events Option 1: Setup via Google Tag In your GTM workspace, navigate to "Tags" and create a new one. Name it "GA4_Custom_User_Properties". Select "Google Tag" for "Tag Configuration". Provide your Tag ID for your Google Analytics instance. Under "Shared event settings", add a new Parameter with the featureName variable you created as the "Event Parameter", and your variationName variable as the "value". Option 2: Send Custom Events to Google Analytics 4 In your GTM workspace, navigate to "Tags" and create a new one. Name it "GA4_Custom_User_Properties". Select "GA4 Event" for "Tag Configuration." In "Configuration Tag", choose your existing GA4 Configuration Tag. Input set_user_properties for "Event Name" (or the event name you chose). Step 4: Define Trigger for the new Tag Within the tag you just setup, create a new "Firing Trigger" in "Triggering". Create a new trigger and set the trigger type to "Custom Event" or to another trigger of your choice. Name the event (if applicable) as set_user_properties (Or the event name you chose in your custom HTML). Step 5: Publish Changes Before hitting "Submit", it's crucial to validate that your configurations are working as intended. Use GTM's "Preview" mode for this. How to Validate your setup with GTM's Preview Mode Click on "Preview" at the top right of the GTM interface. This will open a new browser tab, where you'll navigate to your website. Perform actions that should trigger the tag you've configured. Check the GTM Preview pane that appears at the bottom of your website. It should show the tags that are fired upon your actions. Specifically, confirm that your DevCycle feature and variation data is correctly passed to GA4 tags. When you've confirmed that your data is being passed in correctly, publish your changes by clicking on "Submit"! Google Analytics 4 Configuration Reporting in Google Analytics 4 Navigate to "Reports" > "Library" > "New Report". Choose the metric for analysis under "Event Metric". Select the feature property under "Dimension," e.g., DevCycle_featureNameA . If the dimension doesn't exist: Go to "Admin" > "Custom definitions" > "Create custom dimension". Set the scope to Event and name the event parameter according to your feature. Contributing to DevCycle or Creating a New Integration: DevCycle's tools and integrations are open source and can be found on the DevCycle GitHub repository . For new integrations, refer to DevCycle's Management API and DevCycle Bucketing API . Edit this page Last updated on Jan 9, 2026 Transition from Google Optimize GTM Elements: Tags, Variables, and Triggers Google Tag Manager (GTM) Configuration Step 1: Create a New Tag for DevCycle Initialization and Feature Flag Configuration Values Step 2: Configure GTM Variables Step 3: Create Tag to Send Custom Events Step 4: Define Trigger for the new Tag Step 5: Publish Changes Google Analytics 4 Configuration Reporting in Google Analytics 4 DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:25 |
https://docs.suprsend.com/docs/slack-template#content-area | Slack Template - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection GETTING STARTED What is SuprSend? Quick Start Guide Best Practices Plan Your Integration Go-live checklist CORE CONCEPTS Templates Design Template Channel Editors Email Template In-App Inbox Template SMS Template Whatsapp Template Android Push Template iOS Push Template Web Push Template Slack Template Microsoft teams Template Testing the Template Handlebars Helpers Internationalization Users Events Workflow Notification Categories Preferences Tenants Lists Broadcast Objects Translations DLT Guidelines Whatsapp Template Guidelines WORKFLOW BUILDER Design Workflow Node List Workflow Settings Trigger Workflow Validate Trigger Payload Tenant Workflows Notification Inbox Overview Multi Tabs React Javascript (Angular, Vuejs etc) React Native Flutter (Headless) PREFERENCE CENTRE Embedded Preference Centre Javascript Angular React VENDOR INTEGRATION GUIDE Overview Email Integrations SMS Integrations Android Push Whatsapp Integrations iOS Push Chat Integrations Vendor Fallback Tenant Vendor INTEGRATIONS Webhook Connectors MONITORING & DEBUGGING Logs Audit Logs Error Guides MANAGE YOUR ACCOUNT Authentication Methods Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Channel Editors Slack Template Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Channel Editors Slack Template OpenAI Open in ChatGPT How to design Slack templates using text editor or JSONNET editor for rich block kit templates. OpenAI Open in ChatGPT Edit Template SuprSend provides two ways to design Slack templates: Text Editor : For simple text-based messages with variable interpolation JSONNET Editor : For rich, interactive templates using Slack’s Block Kit with buttons, images, and complex layouts Text Editor The text editor is ideal for simple text messages with variable content. You can add variables in Handlebars syntax as {{...}} . If the output has special html text, enclose variable in triple curly braces as {{{url}}} to avoid HTML escaping. Sample Template Mock Data Copy Ask AI New Signup request in ABC company UserName: {{user_name}} Email: {{user_email}} Organization: {{org.name}} Domain: {{org.domain}} JSONNET Editor The JSONNET editor enables rich template design using Slack Block Kit Builder . This allows you to create interactive templates with buttons, images, checkboxes, and styled text. It is essentially JSON template where variables can be added in JSONNET syntax as data.variable_name or data["$variable_name"] . Template Examples 1. Simple Text Template JSONNET Template Mock Data Copy Ask AI [ { "type" : "section" , "text" : { "type" : "mrkdwn" , "text" : "New Signup on ABC company" } }, { "type" : "section" , "text" : { "type" : "mrkdwn" , "text" : ">_UserName_: *%(user_name)s* \n >_Email_: *%(email)s* \n >_Organization_: *%(org_name)s* \n >_Domain_: *%(domain)s*" % { user_name : data.user_name , email : data.user_email , org_name : data.org.name , domain : data.org.domain } } }, { "type" : "divider" } ] 2. With Buttons: Approval Request Template Mock Data Copy Ask AI [ { "type" : "section" , "text" : { "type" : "mrkdwn" , "text" : "Share access requested for *<%(document_link)s|%(document_name)s>*" % { document_link : data.document_link , document_name : data.document_name } } }, { "type" : "section" , "fields" : [ { "type" : "mrkdwn" , "text" : "*Requested by:* \n " + data.requester_name }, { "type" : "mrkdwn" , "text" : "*When:* \n " + data.submitted_at }, { "type" : "mrkdwn" , "text" : "*Reason:* \n " + data.access_reason } ] }, { "type" : "actions" , "elements" : [ { "type" : "button" , "text" : { "type" : "plain_text" , "emoji" : true , "text" : "Approve" }, "style" : "primary" , "value" : "approve_access" }, { "type" : "button" , "text" : { "type" : "plain_text" , "emoji" : true , "text" : "Deny" }, "style" : "danger" , "value" : "deny_access" } ] } ] 3. With Image: Anomaly Alert Template Mock Data Copy Ask AI [ { "type" : "section" , "text" : { "type" : "mrkdwn" , "text" : ":warning: *High Error Rate Detected* \n Our system has experienced a spike in errors over the last *30 minutes*." } }, { "type" : "section" , "text" : { "type" : "mrkdwn" , "text" : "The error rate has significantly increased, impacting reliability. \n Please investigate immediately to avoid service degradation." } }, { "type" : "image" , "title" : { "type" : "plain_text" , "text" : "Request vs Failure Trend (Last 6 Hours)" , "emoji" : true }, "image_url" : data.image_url , "alt_text" : "Graph showing high error rate spike" }, { "type" : "section" , "fields" : [ { "type" : "mrkdwn" , "text" : "*Impacted Services:* \n " + data.impacted_services }, { "type" : "mrkdwn" , "text" : "*Time Range:* \n " + data.time_range }, { "type" : "mrkdwn" , "text" : "*Error Rate:* \n " + data.error_rate } ] }, { "type" : "divider" }, { "type" : "context" , "elements" : [ { "type" : "mrkdwn" , "text" : "🔍 View logs: <%(log_url)s|Open in Monitoring Tool> \n 📊 See metrics dashboard: <%(dashboard_url)s|Error Trends>" % { log_url : data.log_url , dashboard_url : data.dashboard_url } } ] } ] 4. With Array List: Pending Task Digest (Batched Alert) Template Mock Data Copy Ask AI [ { "type" : "section" , "text" : { "type" : "mrkdwn" , "text" : "Hi " + data [ "$recipient" ] .name + " :wave:" } }, { "type" : "section" , "text" : { "type" : "mrkdwn" , "text" : "You have " +data [ "$batched_events_count" ] + " *pending tasks* for today:" } }, { "type" : "rich_text" , "elements" : [ { "type" : "rich_text_list" , "style" : "bullet" , "indent" : 0 , "elements" : [ { "type" : "rich_text_section" , "elements" : [ { "type" : "text" , "text" : task.title + " (" + task.status + ")" } ] } for task in data [ "$batched_events" ] ] } ] }, { "type" : "actions" , "elements" : [ { "type" : "button" , "text" : { "type" : "plain_text" , "text" : "View Pending tasks" , "emoji" : true }, "url" : "https://app.company.com/tasks" , "value" : "task_url" } ] } ] Adding dynamic content Here’s how you can different types of variables in both handlebars and JSONNET syntax. Variable Type Handlebars Syntax JSONNET Syntax Parent Level variables {{user_name}} data.user_name Nested Object {{org.name}} data.org.name Print Array element at Index {{task_list.[0].task_name}} data.task_list[0].task_name Recipient {{$recipient.name}} data["$recipient"].name Actor {{$actor.name}} data["$actor"].name Tenant {{$tenant.brand_name}} data["$tenant"].brand_name Print each item in the Array Handlebars JSONNET Copy Ask AI {{#each task_list}} {{task_name}}: {{task_description}} {{/each}} Conditional Logic Handlebars JSONNET Copy Ask AI {{#if is_new_org}} New Organization {{else}} Existing Organization {{/if}} Batched Template Handlebars JSONNET Copy Ask AI Total events: {{$batched_events_count}} {{#each $batched_events}} {{item}} {{/each}} Preview Template Add mock JSON data using the Mock data button for all variables used in the template Click Load Preview to see the rendered template For JSONNET templates, click View in Slack Block Kit to see the actual Slack UI preview You must add mock data for all variables in your template. Missing mock data will cause rendering errors and prevent the preview from loading. Publish Template Once your template is ready, click Publish Draft and provide a version name to publish it. The published template becomes the live version and will be used whenever the associated workflow is triggered. Test Template Use this option to send a test message in Slack and preview how it will appear in user’s device. Click the Test button, then enter the user’s distinct_id and select the Slack channel where the test message should be sent. Template testing only uses the published Live version, so make sure to publish your changes before testing. Promote to Production You can clone template across workspaces by using Clone -> Outside Template option. Clone -> Within template can be used to clone within different languages and versions of the same template. Best Practice : Always design templates in your staging workspace first, then promote them to production. This ensures thorough testing of the changes without impacting end users. Was this page helpful? Yes No Suggest edits Raise issue Previous Microsoft teams Template How to design simple MS Teams template using markdown editor or use JSONNET editor to replicate Microsoft's adaptive card design. Next ⌘ I x github linkedin youtube Powered by On this page Edit Template Text Editor JSONNET Editor Template Examples Adding dynamic content Preview Template Publish Template Test Template Promote to Production | 2026-01-13T08:48:25 |
https://www.linkedin.com/legal/cookie-policy?trk=d_checkpoint_rp_requestPasswordReset_ft_cookie_policy | Cookie Policy | LinkedIn Skip to main content User Agreement Summary of User Agreement Privacy Policy Professional Community Policies Cookie Policy Copyright Policy Regional Info EU Notice California Privacy Disclosure U.S. State Privacy Laws User Agreement Summary of User Agreement Privacy Policy Professional Community Policies Cookie Policy Copyright Policy Regional Info EU Notice California Privacy Disclosure U.S. State Privacy Laws Cookie Policy Effective on June 3, 2022 At LinkedIn, we believe in being clear and open about how we collect and use data related to you. This Cookie Policy applies to any LinkedIn product or service that links to this policy or incorporates it by reference. We use cookies and similar technologies such as pixels, local storage and mobile ad IDs (collectively referred to in this policy as “cookies”) to collect and use data as part of our Services, as defined in our Privacy Policy (“Services”) and which includes our sites, communications, mobile applications and off-site Services, such as our ad services and the “Apply with LinkedIn” and “Share with LinkedIn” plugins or tags. In the spirit of transparency, this policy provides detailed information about how and when we use these technologies. By continuing to visit or use our Services, you are agreeing to the use of cookies and similar technologies for the purposes described in this policy. What technologies are used? ENTER A SUMMARY Type of technology Description Cookies A cookie is a small file placed onto your device that enables LinkedIn features and functionality. Any browser visiting our sites may receive cookies from us or cookies from third parties such as our customers, partners or service providers. We or third parties may also place cookies in your browser when you visit non-LinkedIn sites that display ads or that host our plugins or tags . We use two types of cookies: persistent cookies and session cookies. A persistent cookie lasts beyond the current session and is used for many purposes, such as recognizing you as an existing user, so it’s easier to return to LinkedIn and interact with our Services without signing in again. Since a persistent cookie stays in your browser, it will be read by LinkedIn when you return to one of our sites or visit a third party site that uses our Services. Session cookies last only as long as the session (usually the current visit to a website or a browser session). Pixels A pixel is a tiny image that may be embedded within web pages and emails, requiring a call (which provides device and visit information) to our servers in order for the pixel to be rendered in those web pages and emails. We use pixels to learn more about your interactions with email content or web content, such as whether you interacted with ads or posts. Pixels can also enable us and third parties to place cookies on your browser. Local storage Local storage enables a website or application to store information locally on your device(s). Local storage may be used to improve the LinkedIn experience, for example, by enabling features, remembering your preferences and speeding up site functionality. Other similar technologies We also use other tracking technologies, such as mobile advertising IDs and tags for similar purposes as described in this Cookie Policy. References to similar technologies in this policy includes pixels, local storage, and other tracking technologies. Our cookie tables lists cookies and similar technologies that are used as part of our Services. Please note that the names of cookies and similar technologies may change over time. What are these technologies used for? Below we describe the purposes for which we use these technologies. ENTER SUMMARY Purpose Description Authentication We use cookies and similar technologies to recognize you when you visit our Services. If you’re signed into LinkedIn, these technologies help us show you the right information and personalize your experience in line with your settings. For example, cookies enable LinkedIn to identify you and verify your account. Security We use cookies and similar technologies to make your interactions with our Services faster and more secure. For example, we use cookies to enable and support our security features, keep your account safe and to help us detect malicious activity and violations of our User Agreement. Preferences, features and services We use cookies and similar technologies to enable the functionality of our Services, such as helping you to fill out forms on our Services more easily and providing you with features, insights and customized content in conjunction with our plugins. We also use these technologies to remember information about your browser and your preferences. For example, cookies can tell us which language you prefer and what your communications preferences are. We may also use local storage to speed up site functionality. Customized content We use cookies and similar technologies to customize your experience on our Services. For example, we may use cookies to remember previous searches so that when you return to our services, we can offer additional information that relates to your previous search. Plugins on and off LinkedIn We use cookies and similar technologies to enable LinkedIn plugins both on and off the LinkedIn sites. For example, our plugins, including the "Apply with LinkedIn" button or the "Share" button may be found on LinkedIn or third-party sites, such as the sites of our customers and partners. Our plugins use cookies and other technologies to provide analytics and recognize you on LinkedIn and third-party sites. If you interact with a plugin (for instance, by clicking "Apply"), the plugin will use cookies to identify you and initiate your request to apply. You can learn more about plugins in our Privacy Policy . Advertising Cookies and similar technologies help us show relevant advertising to you more effectively, both on and off our Services and to measure the performance of such ads. We use these technologies to learn whether content has been shown to you or whether someone who was presented with an ad later came back and took an action (e.g., downloaded a white paper or made a purchase) on another site. Similarly, our partners or service providers may use these technologies to determine whether we've shown an ad or a post and how it performed or provide us with information about how you interact with ads. We may also work with our customers and partners to show you an ad on or off LinkedIn, such as after you’ve visited a customer’s or partner’s site or application. These technologies help us provide aggregated information to our customers and partners. For further information regarding the use of cookies for advertising purposes, please see Sections 1.4 and 2.4 of the Privacy Policy . As noted in Section 1.4 of our Privacy Policy, outside Designated Countries , we also collect (or rely on others who collect) information about your device where you have not engaged with our Services (e.g., ad ID, IP address, operating system and browser information) so we can provide our Members with relevant ads and better understand their effectiveness. For further information, please see Section 1.4 of the Privacy Policy . Analytics and research Cookies and similar technologies help us learn more about how well our Services and plugins perform in different locations. We or our service providers use these technologies to understand, improve, and research products, features and services, including as you navigate through our sites or when you access LinkedIn from other sites, applications or devices. We or our service providers, use these technologies to determine and measure the performance of ads or posts on and off LinkedIn and to learn whether you have interacted with our websites, content or emails and provide analytics based on those interactions. We also use these technologies to provide aggregated information to our customers and partners as part of our Services. If you are a LinkedIn member but logged out of your account on a browser, LinkedIn may still continue to log your interaction with our Services on that browser until the expiration of the cookie in order to generate usage analytics for our Services. We may share these analytics in aggregate form with our customers. What third parties use these technologies in connection with our Services? Third parties such as our customers, partners and service providers may use cookies in connection with our Services. For example, third parties may use cookies in their LinkedIn pages, job posts and their advertisements on and off LinkedIn for their own marketing purposes. For an illustration, please visit LinkedIn’s Help Center . Third parties may also use cookies in connection with our off-site Services, such as LinkedIn ad services. Third parties may use cookies to help us to provide our Services. We may also work with third parties for our own marketing purposes and to enable us to analyze and research our Services. Your Choices You have choices on how LinkedIn uses cookies and similar technologies. Please note that if you limit the ability of LinkedIn to set cookies and similar technologies, you may worsen your overall user experience, since it may no longer be personalized to you. It may also stop you from saving customized settings like login information. Opt out of targeted advertising As described in Section 2.4 of the Privacy Policy , you have choices regarding the personalized ads you may see. LinkedIn Members can adjust their settings here . Visitor controls can be found here . Some mobile device operating systems such as Android provide the ability to control the use of mobile advertising IDs for ads personalization. You can learn how to use these controls by visiting the manufacturer’s website. We do not use iOS mobile advertising IDs for targeted advertising. Browser Controls Most browsers allow you to control cookies through their settings, which may be adapted to reflect your consent to the use of cookies. Further, most browsers also enable you to review and erase cookies, including LinkedIn cookies. To learn more about browser controls, please consult the documentation that your browser manufacturer provides. What is Do Not Track (DNT)? DNT is a concept that has been promoted by regulatory agencies such as the U.S. Federal Trade Commission (FTC), for the Internet industry to develop and implement a mechanism for allowing Internet users to control the tracking of their online activities across websites by using browser settings. As such, LinkedIn does not generally respond to “do not track” signals. Other helpful resources To learn more about advertisers’ use of cookies, please visit the following links: Internet Advertising Bureau (US) European Interactive Digital Advertising Alliance (EU) Internet Advertising Bureau (EU) LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language | 2026-01-13T08:48:25 |
https://www.fine.dev/blog/ai-developer-agents | AI Developer Agents: Revolutionizing Software Development for Startups with Fine Home Docs Changelog Pricing Sign in Get started -> Menu Home Docs Changelog Pricing <- Go Back AI Developer Agents: Revolutionizing Software Development for Startups with Fine You've probably not only heard of, but tried out or subscribed to an AI coding tool in the last year or two. If you're like most developers, it's an autocomplete tool such as GitHub Copilot. Kind of like pair programming, you write a word, the AI completes the line. You may have also heard terms like AI developer agent or Software 3.0 bandied about. In some cases, you've probably heard people discussing the end of coding as we know it and thought - this is the usual scaremongering, these tools aren't that good. Let's dive together into what these AI developer agents are - what makes it an agent, rather than the assistants you've already tried out? How are they affecting software development? How can you use them at work - in your startup, or for your clients? There's a lot of noise out there on the social networks. Indie hackers and non-coders have been building lots of software using new tools. But for the startup ecosystem, AI developer agents hold potential that hasn't fully been explored. Table of Contents Introduction The Rise of AI in Software Development What is an AI Developer Agent? Understanding AI Developer Agents Key Features of a Good AI Developer Agent How to Effectively Use an AI Developer Agent Benefits to Startups and Developers Introducing Fine: The Next-Generation AI Developer Agent Fine's Benefits for Startups and Developers Real-World Use Cases of Fine Getting Started with Fine The Rise of AI in Software Development The integration of AI into software development has streamlined workflows, reduced errors, and accelerated production timelines. AI tools assist developers by providing intelligent code suggestions, detecting bugs early, and automating repetitive tasks. This shift not only boosts productivity but also allows developers to focus on innovative solutions rather than mundane coding chores. Introduction to Software 3.0 Software 3.0 represents a paradigm shift where AI doesn't just assist but actively participates in the development process. In this model, AI agents can understand specifications, write code, and even make autonomous decisions to optimize performance. This progression signifies a move towards more intelligent, adaptive, and efficient software development practices. If previously, developers spent the largest portion of their time writing code, followed by reviewing code, followed by writing specs, that pyramid is being flipped on its head. We software engineers aren't known for being the best communicators, but our natural language communication skills are becoming more important than how fast you type. Now, startup dev teams are focusing most of their time on planning and writing specs, giving it to AI developer agents, reviewing the code and finishing the last 10% of revisions. What is an AI Developer Agent? An AI Developer Agent is an advanced tool that utilizes machine learning and natural language processing to assist and automate software development tasks. Unlike traditional development tools that require manual input for each function, AI Developer Agents can interpret high-level instructions and execute complex coding tasks independently. Identity, Tools and Guidelines. Each agent has a unique identity and a set of skills that it brings to the task. This identity provides perspective to the AI when performing its functions, leading to more effective and focused results. To perform their tasks, agents are equipped with a set of tools. These could range from the ability to browse a repository or third-party documentation to the ability to write code. Many tasks in software development follow a pattern - a set of steps that need to be executed in order to accomplish the task. When you run an Agent in Fine, it will execute a plan. This plan will be generated on-the-fly based on the Agent's guidelines, allowing for flexibility and adaptability to the specific needs of the task. For example, an agent may implement a feature in React using a plan which might involve creating a component, updating the routing, managing state,etc., adapting as needed. Their Role in Modern Development Workflows In contemporary development environments, AI Developer Agents act as virtual team members. They can convert issues into pull requests, write and modify multiple files based on developer specifications, and integrate seamlessly with existing workflows. This capability transforms the development process, making it more efficient and collaborative. When each developer can manage 3-4 agents for the price of a daily coffee, delegating work instead of having to do it manually, startups can grow significantly faster. The Growing Importance of AI Developer Agents The adoption of AI tools by developers and startups is accelerating. Companies seek to leverage AI Developer Agents to reduce time-to-market, enhance code quality, and stay competitive. Measuring the success of AI developer agents is really the same as any development team - using DORA metrics, for example. As these agents become more sophisticated, their role expands from mere assistants to integral components of the development team. 1. Understanding AI Developer Agents Definition and Core Concepts AI Developer Agents are intelligent systems designed to perform coding tasks autonomously. They utilize algorithms that learn from vast codebases, enabling them to generate code, fix bugs, and optimize performance without direct human intervention. How They Differ from Traditional Development Tools Traditional tools require developers to manually input commands and code. In contrast, AI Developer Agents can interpret natural language instructions, understand the context of the project, and make decisions to execute tasks efficiently. This autonomy sets them apart, offering capabilities beyond standard development tools. The Evolution of AI in Development The journey of AI in coding began with simple code editors and auto-completion features. Over time, these evolved into intelligent agents capable of understanding complex instructions and performing end-to-end development tasks. From Basic Code Editors to Intelligent Agents Early code editors provided syntax highlighting and basic error detection. The introduction of AI brought advanced features like predictive code suggestions and automated debugging. Today, AI Developer Agents can manage entire development cycles, marking a significant leap from their predecessors. 2. Key Features of a Good AI Developer Agent Intelligent Code Assistance Modern AI Developer Agents offer more than just auto-completion. They can perform entire development tasks by transforming issues into pull requests autonomously, write and modify multiple files to handle complex changes across a codebase based on specifications, and provide proactive error detection and correction to identify and fix bugs. Independence of the Development Environment Unlike tools that require integration with an Integrated Development Environment (IDE), the best AI Developer Agents operate independently. They run on cloud-based platforms, which means they have their own development environments that are accessible from anywhere. Additionally, they offer autonomous task execution, allowing them to perform tasks without the need for constant developer intervention. Seamless Integrations Effective AI Developer Agents integrate with essential tools that are vital for a smooth development workflow. They connect with version control systems like Git to track changes, and integrate with issue management platforms such as Jira or Trello for task management. Additionally, they work seamlessly with communication tools like Slack or Microsoft Teams to facilitate team collaboration. For continuous integration and deployment, they integrate with CI/CD pipelines such as Jenkins or GitHub Actions . Finally, they connect with bug detection tools like Sentry or Bugsnag for effective error monitoring. Full Context Awareness For accurate task execution, AI Developer Agents must have full context awareness. This means they need to access entire codebases to understand the project's context comprehensively. They must also be able to perform comprehensive searches to find and reference relevant code segments. By having complete information, they can reduce errors and avoid hallucinations, thereby ensuring high-quality output. Security and safety are a serious concern when giving anyone access to your entire codebase, including AI developer agents. Fine's approach of integrating with your GitHub ensures you code is safe in your trusty VCS, whilst the Agent can read and suggest edits which you'll approve. Learning and Adaptability AI Developer Agents exhibit learning and adaptability by continuously improving based on new code and developer interactions. They also adapt to the team's specific coding styles, ensuring that their output matches the established conventions and practices of the development team. Collaboration Tools AI Developer Agents come equipped with collaboration tools that provide shared insights, making recommendations visible to the entire team. They also facilitate team coordination by enhancing communication and making task delegation more efficient among team members. Security and Privacy AI Developer Agents prioritize security and privacy by implementing data protection measures to ensure that code and proprietary information remain secure. They also adhere to industry standards and regulations for data handling, ensuring compliance with all necessary protocols. This is an area that is still evolving as the laws and regulations are updated to reflect the growing capabilities of LLMs. 3. How to Effectively Use an AI Developer Agent Getting Started To get started with an AI Developer Agent, you first need to set up integrations by connecting the agent with your code repositories, issue trackers, and other tools. Once integrated, you should customize the agent's settings to align with your project requirements and team workflows, ensuring it operates smoothly within your development environment. Best Practices When using an AI Developer Agent, it's best to delegate entire tasks such as full features or bug fixes, allowing the agent to manage them autonomously. However, if the task is particularly large, breaking down large projects into smaller tasks that are manageable by the AI can help streamline development and maintain productivity. You can also create automations for repetitive tasks, letting the agent handle mundane coding activities and freeing up time for more complex work. Pitfalls to Avoid While AI Developer Agents can be highly efficient, it's crucial not to over-rely on them. Developers should still review and understand the code produced to maintain quality and ensure proper functionality. Neglecting code reviews can lead to issues down the line, so always perform thorough reviews to uphold high coding standards. Optimizing Workflows To optimize your workflows, customize the AI Developer Agent to fit specific project needs and team preferences. Providing continuous feedback to the agent will also help improve its performance over time, ensuring it adapts to your unique requirements and becomes a more effective tool for your development team. 4. Benefits to Startups and Developers Accelerated Development Cycles AI Developer Agents significantly accelerate development cycles by enabling faster coding through automated code generation. They also allow for quick prototyping, making it easier to rapidly create prototypes to test ideas and features. Enhanced Code Quality With intelligent error detection and correction, AI Developer Agents help minimize bugs , leading to enhanced code quality. They also ensure consistent standards are maintained across the project, resulting in a more uniform and reliable codebase. Cost Efficiency AI Developer Agents contribute to cost efficiency by reducing development costs through increased productivity without the need for additional manpower. They also help optimize the use of existing resources, ensuring that teams can achieve more with what they already have. Focus on Innovation By automating routine tasks, AI Developer Agents free up developers to focus on creative problem-solving and innovation. This shift allows teams to allocate more time to strategic planning and developing unique features that add value to the project. Scalability AI Developer Agents support scalability by enabling development efforts to grow without requiring proportional increases in team size. They offer flexible scaling, allowing resources to be adjusted based on project demands, making it easier to manage both small and large projects efficiently. 5. Introducing Fine: The Next-Generation AI Developer Agent About Fine Fine is a cutting-edge AI Developer Agent designed to revolutionize software development. Its mission is to empower developers and startups by automating tasks, enhancing collaboration, and accelerating project timelines. What Sets Fine Apart Fine sets itself apart by equipping agents with their own virtual development environment that operates independently in the cloud, making it accessible from anywhere without relying on local systems. It also provides deep integrations, seamlessly connecting with a wide array of development tools, ensuring a smooth and efficient workflow. Moreover, Fine has full context understanding, which allows it to access and comprehend entire codebases, ensuring accurate task execution and reducing the risk of errors. Fine's Advanced Features Fine offers a user-friendly interface with an intuitive design that makes it easy for developers to assign tasks and monitor progress effectively. It utilizes cutting-edge AI algorithms, leveraging advanced machine learning to deliver superior performance. Additionally, Fine provides customization and flexibility, allowing it to adapt to the unique requirements and workflows of each project, ensuring a tailored development experience. 6. Fine's Benefits for Startups and Developers Tailored Solutions Fine provides tailored solutions by employing adaptive learning, allowing it to learn from your codebase and adapt to your specific coding style. It also offers project-specific configurations, enabling developers to customize settings to fit the unique needs of their projects, ensuring that Fine aligns perfectly with their development goals. Improved Collaboration Fine enhances team collaboration through integrated coordination tools that improve communication among team members. It also offers shared workspaces, allowing developers to view and interact with the AI's output, making collaboration more seamless and efficient across the entire team. Real-Time Insights Fine provides real-time insights by delivering immediate feedback, offering instant suggestions and code improvements to enhance development efficiency. It also includes performance analytics, giving developers access to data on efficiency gains and productivity, enabling them to make informed decisions and continuously optimize their workflows. 7. Real-World Use Cases of Fine Industry Applications E-commerce : Streamlining the development of online platforms to provide seamless user experiences and improve transaction processes. AI Developer Agents can help automate the creation of product pages, payment gateways, and customer service chatbots, allowing for efficient scalability. Healthcare Tech : Accelerating the creation of secure medical software that adheres to stringent compliance standards. AI Developer Agents can assist in developing electronic health records (EHR) systems, telehealth platforms, and patient management applications, ensuring both data security and usability. Financial Services : Enhancing the development of compliant financial applications, including payment processing systems, fraud detection, and secure customer portals. AI Developer Agents streamline the coding of regulatory requirements, enabling rapid adaptation to changing financial regulations. Retail : Transforming retail operations by facilitating the development of inventory management systems, point-of-sale (POS) software, and customer loyalty programs. AI Developer Agents can also help in the creation of personalized marketing tools to boost customer engagement and sales. Education Technology (EdTech) : Supporting the development of interactive learning platforms, virtual classrooms, and student management systems. AI Developer Agents assist in coding features like video integration, assessment modules, and personalized learning pathways, enhancing the overall educational experience. Manufacturing : Enabling the development of production management software, predictive maintenance tools, and supply chain management systems. AI Developer Agents help automate data collection and analytics, allowing manufacturers to optimize operations and reduce downtime. Logistics and Supply Chain : Streamlining the development of logistics software, including route optimization tools, shipment tracking systems, and warehouse management solutions. AI Developer Agents help logistics companies optimize their operations and improve the efficiency of supply chain processes. Telecommunications : Assisting in the development of network management tools, customer service applications, and billing systems. AI Developer Agents enable faster deployment of features and ensure that telecommunications platforms remain robust and scalable. Real Estate : Simplifying the creation of property management software, virtual tour integrations, and client communication tools. AI Developer Agents can help automate data handling, property listing updates, and customer inquiries, making real estate management more efficient. Using AI to build AI At Fine, we use our own AI Developer Agents to enhance and build Fine itself. This practice creates a positive feedback loop where our AI continuously improves the platform. By leveraging Fine's AI capabilities, we automate the development of new features, perform code maintenance, and run extensive testing cycles. Fine's agents assist in creating new functionalities, optimizing existing ones, and even identifying areas for further improvement. This approach allows us to accelerate our development cycles, maintain high-quality standards, and ensure that Fine remains at the cutting edge of AI-driven software development. Using AI to build AI is not just a slogan—it’s our daily reality, pushing the boundaries of what our platform can achieve. - Getting Started with Fine 8. Getting Started with Fine Easy Onboarding Process Sign Up : Create an account on Fine's website . Integrate Tools : Connect your repositories and development tools. Fine currently supports GitHub, Linear and Slack, with more on the way. Start Assigning Tasks : Begin leveraging Fine's capabilities immediately. Support and Resources Tutorials and Documentation : Access a wealth of resources to maximize Fine's potential. Customer Support : Reach out to our support team for any assistance. Conclusion AI Developer Agents are reshaping the landscape of software development, bringing unprecedented efficiency and innovation. Fine stands at the forefront of this transformation, offering a next-generation solution that empowers developers and startups to achieve more. Embrace the future of software development with Fine. Join the revolution and elevate your development process to new heights. Transform your software development experience. Try Fine today and be a part of the AI-driven future. Full Table of Contents Introduction The Rise of AI in Software Development Introduction to Software 3.0 What is an AI Developer Agent? Their Role in Modern Development Workflows The Growing Importance of AI Developer Agents Understanding AI Developer Agents Definition and Core Concepts How They Differ from Traditional Development Tools The Evolution of AI in Development From Basic Code Editors to Intelligent Agents Key Features of a Good AI Developer Agent Intelligent Code Assistance Independence of the Development Environment Seamless Integrations Full Context Awareness Learning and Adaptability Collaboration Tools Security and Privacy How to Effectively Use an AI Developer Agent Getting Started Best Practices Common Pitfalls to Avoid Optimizing Workflows Benefits to Startups and Developers Accelerated Development Cycles Enhanced Code Quality Cost Efficiency Focus on Innovation Scalability Introducing Fine: The Next-Generation AI Developer Agent About Fine What Sets Fine Apart Fine's Advanced Features Fine's Benefits for Startups and Developers Tailored Solutions Improved Collaboration Real-Time Insights Real-World Use Cases of Fine Start building today Try out the smoothest way to build, launch and manage an app Try for Free -> © Fine.dev - All rights reserved. Product Overview AI Workflows Pricing & Plans Changelog Blog Docs Company Press Terms & Conditions Privacy policy | 2026-01-13T08:48:25 |
https://docs.devcycle.com/integrations/#ide-plugins | Integrations | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up On this page Integrations Welcome to DevCycle Integrations! Here you will find all of the various first party tools made with the DevCycle APIs, as well as third party integrations to connect DevCycle to the tools of your needs. Contributing to DevCycle or creating a new Integration: If you would like to contribute to an existing integration or tool, all of DevCycle's tools and integrations are open source on the DevCycle Github repository. Further, if you'd like to create a new tool or integration, a great starting point is DevCycle's Management API which allows you to modify and interact with features and more within a DevCycle project, as well as the DevCycle Bucketing API which is used to serve users features and variables (and powers the DevCycle SDKs!) Observability Dynatrace Monitor and analyze your feature flags with Dynatrace observability platform. OpenTelemetry Monitor and analyze your feature flags with OpenTelemetry. Snowflake Data Sharing Access your Organization's Event data on Snowflake Google Analytics Send DevCycle Feature/Variation data from Tag Manager to Google Analytics 4 for A/B test analysis Rollbar Enhance error logging with DevCycle Feature and Variable data IDE Plugins VSCode Extension Use DevCycle directly in Visual Studio Code. Interoperability OpenFeature Use DevCycle with the OpenFeature Flagging Standard. Feature Flag Importer Import resources from other feature flag providers. Webhooks Connect apps and services to DevCycle. Vercel Edge Config Upload DevCycle configurations to Vercel Edge Config for faster retrieval Code Analysis GitHub: Flag Code Usages Display code snippets for each variable used in a project. GitHub: Flag Change Insights Display added/removed flags on each Pull Request. Bitbucket: Flag Code Usages Display code snippets for each variable used in a project. Bitbucket: Flag Change Insights Display added/removed flags on each Pull Request. GitLab: Flag Code Usages Display code snippets for each variable used in a project. GitLab: Flag Change Insights Display added/removed flags on each Merge Request. Collaboration Tools Slack Connect DevCycle to your Slack workspace to track Feature updates. DevOps Jira: Flag Management Link Jira tickets directly to DecCycle features Terraform Provider Manage projects, features and more with Terraform Edit this page Last updated on Jan 9, 2026 Observability IDE Plugins Interoperability Code Analysis Collaboration Tools DevOps DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:25 |
https://www.youtube.com/channel/UCaw7jsGhrsaoSIYPPUF5q2w/playlists | OpenAPI Initiative - YouTube 정보 보도자료 저작권 문의하기 크리에이터 광고 개발자 약관 개인정보처리방침 정책 및 안전 YouTube 작동의 원리 새로운 기능 테스트하기 © 2026 Google LLC, Sundar Pichai, 1600 Amphitheatre Parkway, Mountain View CA 94043, USA, 0807-882-594 (무료), yt-support-solutions-kr@google.com, 호스팅: Google LLC, 사업자정보 , 불법촬영물 신고 크리에이터들이 유튜브 상에 게시, 태그 또는 추천한 상품들은 판매자들의 약관에 따라 판매됩니다. 유튜브는 이러한 제품들을 판매하지 않으며, 그에 대한 책임을 지지 않습니다. | 2026-01-13T08:48:25 |
https://ruul.io/blog/how-to-find-freelance-graphic-design-jobs | Best Freelance Jobs That’ll Stay In Demand Product Payment Requests Get paid anywhere. Sell Services Make your services buyable Sell Products Create once sell forever Subscriptions Get paid on repeat Ruul Space Your personel storefront. One link for everything you offer. Learn more Pricing Resources Partner Programs Referral Program Get 1% for life. Seriously. Affiliate Program Bring users, get paid Partners Let’s grow together. More Blog About us Support Brand Kit For Customers Log in Sign up For Businesses Login Sign up grow Best Freelance Jobs You're looking for the best freelance jobs AI won't wipe out. Safe, in-demand, future-ready, long-lasting work… you'll find it all right here. Canan Başer 5 min read RUUL FOR INDEPENDENCE You chose independence.We make sure you keep it. Sell your time, your talent, whatever you create or build always on your terms. Get started See Example This is also a heading This is a heading Key Points Busy scrolling through 8 sections? Here’s your condensed preview: Tech rules the freelance world: Devs (software, blockchain, AI, cyber) are still flat out in demand. AI isn’t replacing devs, it’s hiring them. $100+ rates is the norm. Writers and designers aren’t going away: Human creativity > sloppy creation by AI. Copywriters, brand builders, and UI/UX professionals that use AI as part of their "real" talent are getting paid. Marketers, who mix data & creativity = $$$: Digital marketing is now AI enabled, but still needs humans with expertise in strategy, ads, SEO, and growth. Teaching is going digital and worldwide: Online courses, tutoring and coaching are on volatility. If you can teach it, you can sell it (and possibly scale it). If you're looking for the best freelance jobs , you're really looking for something that will stay valuable. After all, who wants to master a skill just to be replaced by AI later? The thought alone is a bit scary. 😬 Don’t worry, I’ve done the digging for you. Here are high-demand freelance jobs , spread across 8 key categories, that are expected to stay in demand even in the age of AI. Ready to dive in? 1) Software Development Software developers are the people behind nearly all aspects of the digital world, from the apps you use on your mobile phone to systems that keep global business running. They take an idea such as ordering food, managing a remote team, or watching a movie and turn that idea into a reliable, working software. They also troubleshoot software issues, optimize software performance, and make sure software runs smoothly. Is it worth becoming a software developer in 2025? There's a lot of talk about AI taking jobs, but it's not true. In the U.S., jobs for software developers will increase 15% from 2024 to 2034. There are about 129,200 new developer jobs every year. To sum it up, GitHub's CEO Thomas Dohmke said it best: - "When AI gets better and better, the smartest companies will hire more software developers, not less." Demand for developers continues to flourish—with AI, eCommerce, and automation, it seems to be forever. Learn the basics 🎥 Watch: [ Guide To Becoming A Self-Taught Software Developer ] → Traversy Media explains precisely how you can become a self-taught software developer, from what language to learn first to building real-world projects and portfolios. How much can you make? The worldwide average falls between $20–$150/hour . If you're in North America and are building things in AI, cloud, or cybersecurity, it would be about $80–140/hour. So, depending on what you're building and where you're living, that's where you'll land on the pay scale. Also see 👉🏻 [ Freelance Developer Rates ] 2) Blockchain Engineering Blockchain engineers are the ones who build the infrastructure for decentralized systems. They create secure, transparent, and tamper-proof environments where data cannot be faked, modified, or lost. Consider: Global payment systems NFT platforms Voting methodologies Digital identity solutions Smart cities 🔑 In this world, code = trust. And those who write that trust into the system are blockchain engineers. Is it worth becoming a blockchain engineer in 2025? In 2025, there were 66,494 new Web3 jobs globally, a 47% increase from 2024. The numbers are not back to the 2022 heights, but that is actually a good sign. It shows we are moving beyond the hype stage, and the only real professionals have survived. Companies are not looking for vague “crypto enthusiasts.” They are looking for engineers and developers who are truly professionals, especially in: Rust (for high-performance blockchain coding) Solidity (for ETH smart contracts) Security auditing (to avoid million-dollar hacks) Layer 2/zk technologies (for faster, cheaper scaling) Investment capital is returning to blockchain, but with a focus on infrastructure, privacy, and security. We're past the hype period, and competent engineers are now driving a more stable, high-value economy. Learn the basics 🎥 Watch: [How does a blockchain work? – Simply Explained ] → This Simply Explained video breaks down blockchain in plain language. You’ll see how blocks, hashing, and decentralization actually work behind the scenes. How much can you make? The average rate is $81–$100/hour . Upwork mid-level developers earn about $30–$59/hour , while top-level engineers can charge up to $200/hour with enterprise clients. Adding, Blockchain roles tend to be remote and global, so you can access lucrative markets, no matter where you live. 3) AI & ML Engineering AI (Artificial Intelligence) and ML (Machine Learning) engineers are those folks who work with systems like ChatGPT, self-driving cars, and voice assistants. But first, let’s clear up a common confusion: ML engineers make sure ChatGPT gives great answers. AI engineers make sure we can actually use ChatGPT on our devices. Ultimately, the ML engineer builds the brain, while the AI engineer gives it a body and a purpose. Is it worth becoming an AI engineer in 2025? The percentage of companies utilizing AI jumped from 55% to 78% in just one year. At the same time, ML has become one of the fastest-growing freelance categories on sites like Upwork. The demand for engineers is changing towards: LLM deployment Model fine-tuning Infrastructure scaling Evaluation and safety testing AI is not taking jobs, it's creating jobs! We can thank it for creating jobs that didn't exist before. 🙂 Learn the basics 🎥 Watch: [ Machine Learning for Everybody – Full Course ] → freeCodeCamp’s “Machine Learning for Everybody” gives a friendly introduction to AI and ML concepts, from training models to real-life use cases, all without complex math. How much can you make? Global engineering rates for AI/ML professionals vary between $35 and $160+/hour . On Upwork, the average is $35–$60/hour , but that’s for entry to mid-level work. But experienced freelancers working with startups or enterprise projects can earn 2–5× more, easily reaching top-tier rates. 4) Cybersecurity The job of a cybersecurity expert is to protect computers, phones, cloud, networks, and data. It is like installing a security system to protect your home from a thief. They have three tasks: → enact prophylactic measures → detect attacks → repair damage after an attack Large corporations and government agencies cannot keep going without this security chain. Is it worth becoming a cybersecurity specialist in 2025? This year, cybersecurity spending will rise from $193B to $213B . Growth is strong in Cloud and Application Security, because they realize they must protect their data as they move it online. In fact, there are not enough cybersecurity experts. Currently, there are 5.47 million people working in the field. But they still need 4.76 million more. That's a record gap, and it shows that the world needs more cybersecurity professionals. Also, only 14% of organizations (about 1.5 out of 10) claim that they have all the talent needed in cybersecurity. The rest? say they're facing a critical skills gap. So, there’s a budget + high risk → rising demand for freelancers → perfect time to start. Risks are growing, budgets are growing, and the world currently doesn't have enough experts yet. Learn the basics 🎥 Watch: [Introduction to Cybersecurity – Simplilearn ] → Understand what ethical hacking and defending a system really are. Simplilearn’s introduction to cybersecurity will walk you through how hackers think and how the experts stop them. How much can you make? Freelancers in cybersecurity can expect to see hourly rates between $60-$120. However, if you can demonstrate your specialized skills, you could start charging $150+ per hour. Additionally, if you eventually transition into a more senior management role (ex. vCISO), it's entirely possible to earn between $200-300 per hour. 5) Copywriting Copywriters can write just about anything you could find on the internet: social media posts, blog articles, short ad copy, marketing emails, sales pages, and newsletters. Most copywriters have some kind of specialization and are known for it, such as a beauty writer, health writer, B2B article writer, or even a LinkedIn ghostwriter. But of course, you could be a generalist or have even a few specializations if you prefer. Is it worth becoming a copywriter in 2025? 46% of B2B marketers say their content budgets will increase in 2025. I’m not surprised, since content marketing drives : demand/leads (74%) subscriptions/nurturing (62%) sales impact (49%) There's rigorous demand and big budgets for human, conversational content. Plus, AI-generated “slop fatigue,” writers who can connect with readers stand out more than ever. Joe Pulizzi , founder of Content Marketing Institute, backs this belief: — "AI can create a lot of content, but humans still lead in what content is worth creating." I believe AI's true way of impact is in coordination and content operations, not creation. Brands are looking for authentic voices, and human writers who can create emotional connections are more valuable than ever. Learn the basics 🎥 Watch: [ Start Copywriting FAST – 8 Steps for Beginners ] → In this video from Alex Cattoni, you’ll learn the 8 steps to start copywriting FAST — from building empathy, to writing words that persuade your reader to become a buyer. How much can you make? Worldwide, copywriters typically earn $15–$90/hr, depending on experience and niche. Others are paid per word, and if you have specialized expertise (i.e., in health), you may earn $1.25 a word. For simpler topics, rates are usually $0.30–$0.50 per word. About what writers earn worldwide 👉🏻 [ Freelance Writer Rates ] 6) Design Ever see a billboard, some product packaging, or a social media post and think, "wow, that actually looks really cool"? Yep, you can thank a designer for that. Is it worth becoming a designer in 2025? We're seeing some double-digit growth in UI/UX specifically, based on a study that collected and quantified over 22,500 data points. I also checked out what's happening on freelance job sites, and took a look at the Fiverr Business Trends Index and Upwork data. And it’s legit, job postings and searches for all kinds of design services have jumped significantly in areas like website design 3D product rendering Social media content design branding/creative On the branding side, client expectations have now shifted to expecting both great quality and delivery yesterday. And you can probably guess the buzzword designers can’t stop mentioning: → (AI powered design + human touch) It’s the hottest combo across the creative world, and design is no exception. Creative demand is booming again. Designers who are familiar with AI tools and can interconnect them with human brilliance will be in the best positions. Learn the basics 🎥 Watch: [ The 2025 UI/UX Crash Course for Beginners - Learn Figma ] → This DesignCourse tutorial shows you how to go from wireframes to full mockups using Figma. You’ll see the real design workflow step by step. How much can you make? On Upwork, you are looking at designer rates in the $15- $35/hr range. However, this is pretty low for experienced designers. Most freelancers who are professionals will say they earn much more. Top-tier designers can earn $100-150/hr or higher. More about how much you can earn 👉🏻 [ Freelance Designer Rates ] 7) Digital Marketing A digital marketer enhances a brand’s online presence via social media, search engines, ads, emails, and every other avenue that allows consumers to find the brand. The objective is to take someone from awareness to trust, and from trust to sales. But digital marketing is not one job any longer; it's a toolkit. Some marketers excel at SEO. Others are experts in Instagram ads. The ones who shine? They go deep into one skill and establish credible authority around it. Is it worth becoming a digital marketer in 2025? This year, global ad spend is expected to reach $1.17 trillion , a 7% increase from last year. Companies have the budget, but they are reallocating to what provides verifiable ROI: social media and content marketing are increasingly becoming joint drivers of digital growth. And that engine is now powered by AI. 93% of managers and 83% of teams say AI has improved ROI, personalization, data use, and cost efficiency. For freelancers, that means: Brands are looking for strategic operators to turn creativity and data into results. Budgets are growing fast, it's freelancers who are able to corral creativity and data that will be at the forefront of the new wave of marketing. Learn the basics 🎥 Watch: [ Digital Marketing 101 - A Complete Beginner's Guide to Marketing ] → Laurie Wang’s video walks you through how the main digital marketing channels (SEO, email, social, ads) connect and work together. Ideal for beginners. How much can you make? In the mid to lower market, Upwork rates usually range from $15–$45 per hour. But if you're an expert in a strategic field (like SEO in the US/CA market), you can earn $75–$200/hr . Performance-based pay is also common in roles like ad management. 8) Education When you can learn something new without even stepping into a school setting, congratulations, you are learning online. As a freelance teacher or coach, you can teach students in so many different "areas". This could be about: Work-related skills (project management, design, etc.) Personal development (such as confidence, productivity, life skills) Or anything more academic, such as languages, academic subjects, and even complex sciences. You can provide recorded courses together, or you can lead live classes together over groups of video conferencing calls. You can set it up however you would like, as this is your setup in life. Is it worth becoming an educator in 2025? Some educators are selling fully designed course packs, and some are operating "cohort-based" classes, which are small groups of people learning together at the same time. And this concept is projected to go from $3.8B in 2024 to $15.2B by 2033. Language learning is also growing. Expected to grow to 21.1B in 2025 and more than double by 2030. There is a significant demand for speaking coaches and fluency mentors. On the coaching side, the number of coaches in the world has grown 15% from 2023, and it is now greater than 122,974. And many coaches are not strictly doing coaching: 60% are also teaching 57% are also consultants 49% are also mentoring Most significantly, 59% of coaches expect to earn more next year. On the business side, Learning and Development leaders are going deeper on AI training and closing skills gaps. More businesses are looking to hire external experts (coaches and educators) for flexible, impactful training. Meanwhile, companies like Coursera and Udemy are also seeing solid growth in revenue and users. This is bringing normalization to online learning and is paving the way for a new wave of freelancers in the space. Learn the basics 🎥 Watch: [ Teach Online in 2025 | How to Start & Succeed as an Online Teacher ] → Jamie (ESL Teacher 365)’s video explains how to begin teaching online in 2025, main pathways (companies, marketplaces, freelance), key requirements (TEFL, technology, niche), and tips for beginners, especially for non-native teachers. How much can you make? Costs depend on the subject and the tutor’s level of expertise. Most tutors on Upwork charge $20–$40/hr , while in-person, 1:1 coaching in Europe could go for $100/hr+, and up to $200/hr. The most lucrative tutoring markets include tutoring STEM, software, data science, AI, ML, and no-code. Where working freelance finally feels effortless! When you work with Ruul , you will avoid all of that usual freelancing nonsense: Get your invoice in a few seconds (VAT is calculated automatically). Sell your services in 190 countries and 140 currencies, even crypto! Showcase your portfolio, services, subscriptions, and products. All in one Space. Get paid directly to your bank within 1 day, or on the spot with crypto. Ruul removes the roadblocks for ease of freelancing. Sign up now , join thousands of other independents, and get paid in 2025 how you deserve! FAQs 1. What is the highest-paid freelance job? AI and blockchain engineers had the highest earnings in 2025, while making $150-$200/hr. These freelance professionals build core systems (AI platforms, smart contracts, and secure infrastructure) which are in constant demand due to the critical need in the global economy. 2. How much do freelance AI engineers make? Freelance AI engineers earn about $35-$160 an hour, while senior specialists in the field of MLOps or infrastructure earn more than $200 an hour. As more corporations begin using and scaling AI systems within their operations, the pay will continue to escalate. 3. What is best for freelancing? Software, AI, design work, copywriting, and digital marketing ranked highest for freelancers in 2025. These jobs combine creativity and tech, can pay extremely well ($20-$150+/hour), and will continue to be in demand for many years, even beyond the advent of AI. 4. Which skill is best for freelancing in 2025? AI, software, and cybersecurity skills ranked the highest for freelancing in 2025. Skills combining tech with creativity, like AI-powered coding or UX design work, will be highly sought after and hard to compete with on a global level. ABOUT THE AUTHOR Canan Başer Developing and implementing creative growth strategies. At Ruul, I focus on strengthening our brand and delivering real value to our global community through impactful content and marketing projects. More Essential web development tools for freelancers With so many resources and choices floating around, it can be very difficult to choose the best tools to use as a web developer. Read more Ruul Now Supports Cryptocurrency Payments for Freelancers Accept crypto payments as a freelancer! Ruul now supports Bitcoin, Ethereum, and stablecoin payouts—fast & global. Read more How to Sell Subscriptions Turn your services into steady monthly revenue: learn the best subscription models, smart pricing, and retention tactics that keep customers paying. Read more MORE THAN 120,000 Independents Over 120,000 independents trust Ruul to sell their services, digital products, and securely manage their payments. FROM 190 Countries Truly global coverage: trusted across 190 countries with seamless payouts available in 140 currencies. PROCESSED $200m+ of Transactions Over $200M successfully processed, backed by an 8-year legacy of secure, reliable transactions trusted by independents worldwide. FREQUENTLY ASKED QUESTIONS Everything you need to know. Get clear, straightforward answers to the most common questions about using Ruul. hey@ruul.io What is Ruul? Ruul is a merchant-of-record platform helping freelancers and creators globally sell services, digital products, subscriptions, and easily get paid. Who is Ruul for? Ruul is designed for freelancers, creators, and independent professionals who want a simple way to sell online and get paid globally. How does Ruul work? Open an account, complete a quick verification (KYC), and link your payout account. Then, start selling through your store or send payment requests to customers instantly. How does pricing work? Signing up is free. There are no subscription or hidden fees. Ruul charges a small commission only when you sell or get paid through the platform. What is a Merchant of Record? A merchant of record is the legal seller responsible for processing payments, handling taxes, and managing compliance for each transaction. What can I sell on Ruul? You can sell services, digital products, license keys, online courses, subscriptions, and digital memberships. How do I get paid on Ruul? Add your preferred bank account, digital wallet, or receive payouts in stablecoins as crypto. Funds arrive within 24 hours after a payout is triggered. OPEN AN ACCOUNT START MAKING MONEY TODAY ruul.space/ Thank you! Your submission has been received! Oops! Something went wrong while submitting the form. Trustpilot Product Payment Requests Sell Services Sell Products Subscriptions Ruul Space Pricing For Businesses Resources Blog About Contact Support Referral Program Affiliate Program Partner Program Tools Invoice Generator NDA Generator Service Agreement Generator Freelancer Hourly Rate Calculator All Rights Reserved © 2025 Terms Of Use Privacy Policy | 2026-01-13T08:48:25 |
https://www.linkedin.com/signup/cold-join?session_redirect=https%3A%2F%2Fwww%2Elinkedin%2Ecom%2Fcompany%2Fsuprsend&trk=organization_guest_nav-header-join | Sign Up | LinkedIn Join LinkedIn now — it’s free! Not you? Remove photo Join LinkedIn To create a LinkedIn account, you must understand how LinkedIn processes your personal information by selecting learn more for each item listed. Agree to all terms We collect and use personal information. Learn more We share personal information with third parties to provide our services. Learn more Further information is available in our Korea Privacy Addendum . Privacy Policy Addendum 1 of 2 2 of 2 Agree to the term Continue Back Agree to all terms Email Password Show Remember me First name Last name By clicking Agree & Join, you agree to the LinkedIn User Agreement , Privacy Policy , and Cookie Policy . Agree & Join or Security verification Already on LinkedIn? Sign in Looking to create a page for a business? Get help LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language | 2026-01-13T08:48:25 |
https://www.fine.dev/blog/ai-coding-guide | AI Coding – A Simple Guide for Developers Home Docs Changelog Pricing Sign in Get started -> Menu Home Docs Changelog Pricing <- Go Back AI Coding – A Simple Guide for Developers Table of Contents Introduction: What is AI Coding The Importance of Context in AI Coding Tips for Providing Better Context Practical Instructions for Providing Context to AI Coding Tools 1. Creating a Knowledge Graph 2. Implementing Retrieval-Augmented Generation (RAG) 3. Copy-Pasting Relevant Code into ChatGPT and Claude 4. Understanding Potential Mistakes Without Proper Context Using AI to Generate Code Incorporating AI Tools into Your Workflow Advice for Front-End Developers Practical Tips Advice for Back-End Developers Practical Tips Use Cases for AI in Coding 1. Automated Bug Fixes 2. Predicting Performance Bottlenecks 3. Large Codebase Refactoring Industry-Specific Benefits Best Large Language Models (LLMs) for Coding 1. OpenAI 2. Anthropic 3. Google Gemini 4. Other Notable Models Choosing the Right LLM for Your Needs Popular AI Coding Tools 1. Fine 2. ChatGPT 3. Replit 4. Devin 5. Cursor Conclusion Introduction: What is AI Coding In today's rapidly evolving tech landscape, AI coding has emerged as a game-changer for developers. But what exactly is AI coding? Simply put, it's the use of artificial intelligence to assist in writing, optimizing, and managing code. AI coding tools help developers write better, faster, and more efficient code by automating repetitive tasks, providing intelligent code suggestions, and even debugging. This blog will delve into the importance of context in AI coding, how to use AI for generating code, offer practical advice for both front-end and back-end developers, explore various use cases, introduce some of the top AI coding tools available today, and discuss the best large language models (LLMs) for coding. The Importance of Context in AI Coding The first key to success in AI coding is understanding context . AI tools analyze the surrounding code to generate relevant and accurate suggestions. Without proper context, AI-generated code can be irrelevant or even introduce errors. Here's why context matters: Code Quality: In complex systems, context helps maintain consistency and functionality across different modules. Relevance: AI tools can provide more precise code snippets when they understand the broader scope of the project. Efficiency: Proper context reduces the time developers spend correcting AI-generated code. Imagine asking a lawyer off the street to represent you in court, without knowing anything about you, the case, or the evidence. The best lawyer in the world would struggle! The same goes for AI in coding - only if you provide the relevant information will you get relevant results. Tips for Providing Better Context: Descriptive Comments: Write clear and detailed comments to guide the AI tool. Structured Code: Organize your code logically to help AI understand the flow and dependencies. Consistent Naming Conventions: Use meaningful and consistent names for variables, functions, and classes. Integrate Platforms: The more of your tech stack that can be integrated, the more data the AI will be able to access and the better the output will be. Fine offers GitHub, Linear, and Sentry integrations with more on the way. Practical Instructions for Providing Context to AI Coding Tools To maximize the effectiveness of AI coding tools, providing comprehensive and well-structured context is essential. Here are some practical methods to enhance context for AI tools: 1. Creating a Knowledge Graph A knowledge graph is a structured representation of information that outlines the relationships between different components of your codebase. By creating a knowledge graph, you can provide AI tools with a holistic view of your project, enabling them to make more informed suggestions. How to Create a Knowledge Graph: Identify Key Components: List out all the modules, classes, functions, and their interactions within your project. Define Relationships: Establish how these components interact, depend on each other, and contribute to the overall functionality. Use Visualization Tools: Utilize tools like Neo4j or Graphviz to visualize the knowledge graph, making it easier to understand and update. Benefits: Enhances AI's understanding of the project structure. Facilitates better code suggestions and optimizations. Helps in identifying dependencies and potential areas for improvement. Fine creates a knowledge graph called Atlas, which includes your codebase from GitHub and issues from Sentry and Linear. This way, it prepares the AI to handle any task you give it. You don’t need to work hard creating your own knowledge graph when we’ve done it for you. 2. Implementing Retrieval-Augmented Generation (RAG) Retrieval-Augmented Generation (RAG) combines traditional information retrieval techniques with generative AI models to provide more accurate and contextually relevant responses. How to Use RAG: Integrate Data Sources: Connect your AI coding tool to relevant data sources such as documentation, code repositories, and knowledge bases. Contextual Retrieval: Ensure that the AI can retrieve pertinent information from these sources before generating code suggestions. Continuous Learning: Update the data sources regularly to keep the AI informed about the latest changes and best practices in your project. Benefits: Improves the relevance and accuracy of AI-generated code. Enables AI to leverage existing knowledge and documentation. Enhances the tool's ability to handle complex queries and tasks. 3. Copy-Pasting Relevant Code into ChatGPT and Claude When using conversational AI tools like ChatGPT for coding assistance, providing snippets of relevant code can significantly improve the quality of the responses. How to Provide Relevant Code: Select Key Sections: Identify and copy the sections of code that are directly related to your query or the task at hand. Provide Contextual Information: Along with the code, include comments or explanations that describe the functionality and purpose of the code segments. Ask Specific Questions: Clearly state what you need help with, such as debugging a particular function or optimizing a code block. Example: # Function to calculate the factorial of a number def factorial(n): if n == 0: return 1 else: return n * factorial(n-1) # I need to optimize this recursive factorial function to handle larger numbers without hitting the recursion limit. Question: How can I optimize the above factorial function to handle larger inputs efficiently? Benefits: Provides AI with the necessary context to generate accurate solutions. Reduces ambiguity, leading to more precise and helpful responses. Saves time by directly addressing specific issues within the code. This is similar to GitHub Copilot and some other tools where you can highlight the relevant context to direct the AI. 4. Understanding Potential Mistakes Without Proper Context AI coding tools, while powerful, can make mistakes if not provided with adequate context. Common errors include: Irrelevant Code Suggestions: Without understanding the project structure, AI might suggest code that doesn't fit the existing framework. Syntax Errors: Lack of context can lead to syntax mistakes, especially in languages with strict syntax rules. Logical Flaws: AI might introduce logical errors if it doesn't fully grasp the intended functionality. Security Vulnerabilities: Inadequate context can result in code that exposes security loopholes or fails to follow best practices. Backend Errors In languages commonly used for backend such as Python, AI may make more mistakes if it doesn’t have context, such as NameErrors and IndentationErrors - mistakes that you wouldn’t have made coding manually. You can read more about common Python errors and how different AI applications handle them here. Fine is less likely to make such errors, as it has full knowledge of your codebase. Mitigation Strategies: Always Review AI-Generated Code: Never blindly trust the AI's suggestions; always verify and test the code. Provide Comprehensive Context: The more information you provide, the better the AI can assist accurately. Use Multiple Sources: Cross-reference AI suggestions with official documentation and best practices. Continuous Feedback: Provide feedback to the AI tool to help it learn and improve over time. Using AI to Generate Code AI coding tools are revolutionizing the way developers write code by automating mundane tasks and enhancing creativity. Here's how AI is being used to generate code: Code Snippets: AI can suggest entire lines or blocks of code based on the current context. Automating Repetitive Tasks: Tasks like boilerplate code generation, formatting, and refactoring can be handled by AI, freeing up developers to focus on more complex problems. Bug Detection: AI can identify potential bugs and vulnerabilities in real-time, ensuring higher code quality. Incorporating AI Tools into Your Workflow: Choose the Right Tool: Select an AI coding tool that integrates seamlessly with your development workflow. Customize Settings: Tailor the tool’s settings to match your coding style and project requirements. Regularly Review Suggestions: While AI can assist, always review and test AI-generated code to ensure it meets your standards. Advice for Front-End Developers Front-end development focuses on the user interface and user experience. AI coding tools can significantly enhance this process: UI/UX Enhancement: AI can suggest design improvements and optimize user interfaces for better engagement. Streamlining CSS/HTML/JS: Automate the generation of responsive designs and ensure cross-browser compatibility. Automated Testing: AI tools can perform repetitive testing tasks, ensuring your front-end code is robust and error-free. Practical Tips: Use AI for Responsive Design: Let AI suggest layout adjustments for different screen sizes. Optimize Performance: AI can analyze and optimize front-end performance, reducing load times and improving user experience. Leverage AI for Accessibility: Ensure your applications are accessible by using AI to identify and fix accessibility issues. Advice for Back-End Developers Back-end development involves server-side logic, database management, and ensuring the smooth operation of applications. AI coding tools can streamline these processes: Automating Server-Side Logic: AI can generate efficient server-side code, handling complex operations with ease. Security Vulnerability Detection: Identify and fix security issues before they become problematic. Database Query Optimization: AI can analyze and optimize database queries for better performance. Practical Tips: API Generation: Use AI to create and manage APIs, ensuring they are secure and efficient. Automate Testing: Implement AI-driven testing to validate back-end processes and ensure reliability. Optimize Code Performance: Leverage AI to analyze and enhance the performance of your server-side code. Use Cases for AI in Coding AI coding has a wide range of applications across various industries. Here are some real-world use cases: 1. Automated Bug Fixes Fine’s AI can identify and fix bugs in your codebase, reducing the time spent on debugging and improving overall code quality. 2. Predicting Performance Bottlenecks By analyzing code patterns, AI can predict potential performance issues, allowing developers to address them proactively. 3. Large Codebase Refactoring Managing and refactoring large codebases can be daunting. AI tools can assist with this process, ensuring consistency and reducing errors. Industry-Specific Benefits: E-Commerce: Enhance platform performance and security with AI-driven optimizations. Add features to improve user experience and conversion rates rapidly. Fintech: Ensure the reliability and security of financial applications through AI-assisted coding. SaaS Platforms: Improve scalability and performance with AI-generated and optimized code. Healthcare: Streamline data processing and ensure compliance with regulatory standards through AI-assisted code generation. Education Technology: Enhance learning platforms by personalizing features and improving code quality with AI-driven development. Gaming: Optimize game performance and identify bugs faster with AI-generated suggestions and automated testing. Best Large Language Models (LLMs) for Coding Large Language Models (LLMs) are at the heart of modern AI coding tools. They power the intelligent features that assist developers in writing and managing code. Here are some of the best LLMs for coding: 1. OpenAI OpenAI's models, including GPT-4 , are renowned for their versatility and capability in understanding and generating human-like text. In coding, GPT-4 excels at code generation, debugging, and providing intelligent suggestions across multiple programming languages. OpenAI also offers Codex , specifically fine-tuned for programming tasks, making it a popular choice for developers seeking advanced AI assistance. OpenAI also recently released preview and mini versions of their latest model, o1, which is outperforming competitors on many benchmarks. 2. Anthropic Anthropic's Claude models focus on safety and reliability, ensuring that AI-generated code adheres to best practices and minimizes errors. These models are designed to understand complex coding contexts and provide suggestions that align with developers' intent. Anthropic emphasizes ethical AI use, making their models a trustworthy option for sensitive and critical development environments. Claude Sonnet 3.5 was widely regarded as the most powerful LLM for coding, until o1’s release, and many developers still prefer it. 3. Google Gemini Google's Gemini models leverage Google's extensive research in natural language processing and machine learning. Gemini is designed to integrate seamlessly with Google's ecosystem, offering robust support for various programming languages and frameworks. With a focus on scalability and performance, Gemini models are ideal for large-scale projects requiring consistent and efficient code generation. 4. Other Notable Models: Cohere : Known for their fast and efficient language models, Cohere offers solutions tailored for real-time coding assistance and integration into development workflows. Grok: A versatile AI model designed to assist developers in writing, debugging, and optimizing code effectively. IBM Watson: IBM's AI offerings include models that specialize in enterprise-level coding assistance, focusing on security, compliance, and integration with existing IT infrastructures. Choosing the Right LLM for Your Needs: When selecting an LLM for coding, consider the following factors: Language Support: Ensure the model supports the programming languages you use. Integration: Look for models that integrate smoothly with your development environment and tools. Customization: Some models offer more flexibility for customization and fine-tuning based on specific project requirements. Safety and Reliability: Prioritize models that emphasize code accuracy and security to minimize the risk of introducing vulnerabilities. Click here to learn about the leading LLMs for coding and how they compare. o1-preview and Claude 3.5 Sonnet are considered to be the prominent AI models for coding. Popular AI Coding Tools There are several AI coding tools available, each with unique features tailored to different needs. Here are some of the leading options: 1. Fine Features: Fine offers advanced code generation, intelligent suggestions, automations and a full-context knowledge graph. It leverages state-of-the-art LLMs including o1 and Claude Sonnet to provide accurate and context-aware code assistance. Best For: Professional developers seeking a comprehensive AI assistant that enhances productivity across multiple programming languages, working on existing codebases. Integration: Integrates with GitHub, Linear, Sentry and Slack - with further integrations such as Jira, Monday Dev, Clickup, Data Dog, Jam.dev and posthog coming soon. 2. ChatGPT Features: ChatGPT provides conversational AI assistance, allowing developers to ask questions, seek code examples, and receive real-time support. It excels in understanding natural language queries and providing detailed explanations. Best For: Asking short questions about coding in general - such as explaining functions you’re not familiar with. Integration: Accessible via web interface, API, and can be integrated into various development tools through plugins and extensions. 3. Replit Features: Replit offers an online coding platform with integrated AI assistance. It supports collaborative coding, real-time code suggestions, and automated debugging. Best For: Teams and individual developers looking for a cloud-based development environment with built-in AI support. Integration: Fully web-based, allowing seamless collaboration and access from any device with internet connectivity. 4. Devin Features: Devin focuses on optimizing backend development with AI-driven code generation, API creation, and database management. It offers robust security features and performance optimization tools. Best For: Back-end developers seeking specialized AI tools to streamline server-side development and database interactions. Integration: Compatible with major backend frameworks and integrates with popular cloud services for deployment and management. Devin isn’t currently publicly available, but you can apply for Beta access via their website. 5. Cursor Features: Cursor provides AI-powered code generation and real-time collaboration features. It emphasizes building large blocks of code and reducing development time. Best For: Developers who prioritize code quality and seek tools that can begin a project from scratch and take it to MVP. Integration: Cursor is built on VSCode making it familiar for many developers. Equally as time-consuming as writing code is reviewing code. Here's a comparison of how different AI Coding tools handle code reviews. Conclusion AI coding boosts productivity, improves code quality, and lets developers focus on creative tasks. Providing context, using AI for code generation, and choosing the right tools can greatly benefit developers. Pick the best large language models for your needs to optimize your workflow. Automate tasks, optimize performance, and enhance security with AI coding tools. Embrace AI to unlock new efficiency and innovation. Try Fine for free at ai.fine.dev and elevate your coding workflow today. Start building today Try out the smoothest way to build, launch and manage an app Try for Free -> © Fine.dev - All rights reserved. Product Overview AI Workflows Pricing & Plans Changelog Blog Docs Company Press Terms & Conditions Privacy policy | 2026-01-13T08:48:25 |
https://www.linkedin.com/help/linkedin?trk=d_checkpoint_rp_requestPasswordReset_ft_send_feedback&lang=en | LinkedIn Help Attention screen reader users, you are in a mobile optimized view and content may not appear where you expect it to be. To return the screen to its desktop view, please maximize your browser. Skip to content Skip to search Close jump menu Help LinkedIn Help Dropdown menu, expand to explore help for other LinkedIn products Close menu Get help with: LinkedIn Corporate Billing Learning Marketing Solutions Recruiter Sales Navigator Talent Insights Go to LinkedIn Sign in Sign in We’re here to help. LinkedIn shortcuts Change or add an email address Opens in new tab. Reset your password Opens in new tab. Cancel LinkedIn Premium subscription Close your account Opens in new tab. LinkedIn public profile visibility Apply for jobs on LinkedIn Recommended topics View all Basics Data and Privacy Subscription Billing Your Profile Connections Search and Apply for Jobs Suggested articles Manage emails from LinkedIn You can manage the types and frequency of emails from LinkedIn and even choose to stop specific emails by unsubscribing. Learn more To manage emails: Click the Me icon at the top of your LinkedIn homepage. Click Settings & Privacy. Click… Cancel LinkedIn Premium subscription Basics, Premium, and Invoice and Billing Details You can cancel your LinkedIn Premium subscription at any time. After cancellation, your account returns to a Basic (free) plan, and you’ll lose access to the Premium features such as InMail credits, profile insights, LinkedIn Learning, the Premium… Visibility of shared posts Post and Share Content The visibility of posts and engagement activity that appear in the main feed and profile may vary depending on the visibility option that the author has selected for the post. You can't change the visibility option after you've shared your post. The… Visibility and impact of your social activity on the LinkedIn feed Post Your LinkedIn feed contains professional content from your network, your shares, likes, and posts, companies you follow, and other content that we believe you may be interested in. LinkedIn's systems track and analyze social actions such as writing… Share profile updates with your network Learn more You can choose to notify your network about job changes, education changes, and work anniversaries. Enabling notifications about your profile changes may generate a post in your network’s feed, an in-app notification, or an email… Access country specific employment types You can now select employment types that are specific to the country in which you’ve worked and more accurately represent your professional experience. Note: You must change the location on your introduction section in order to access a new… More help Other ways we can help Please sign in so we can provide the best support possible. Sign in Professional Community Policies Our policies ensure you have a safe and professional experience on LinkedIn. Learn more Transparency Center Your account security and online safety is our top priority. Learn more LinkedIn Status Page Get insights and historical information into factors that could be impacting LinkedIn's products. Learn more LinkedIn Contact us Select a language. The page will automatically refresh after a language has been selected. العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) LinkedIn Corporation © 2026 About Transparency Center Privacy and Terms Cookies Copyright Terms Privacy Guest controls Dismiss Privacy and Terms menu LinkedIn Corporation © 2026 | 2026-01-13T08:48:25 |
https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fdev.to%2Fleena_malhotra%2Fwhy-asking-for-better-outputs-misses-the-real-problem-29f9&title=Why%20Asking%20for%20Better%20Outputs%20Misses%20the%20Real%20Problem&summary=Yesterday%2C%20I%20spent%20four%20hours%20debugging%20why%20Ideogram%20V3%20kept%20generating%20inconsistent%20architectural...&source=DEV%20Community | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T08:48:25 |
https://www.linkedin.com/signup/cold-join?session_redirect=https%3A%2F%2Fwww%2Elinkedin%2Ecom%2Fcompany%2Fsuprsend&trk=organization_guest_main-feed-card_like-cta | Sign Up | LinkedIn Join LinkedIn now — it’s free! Not you? Remove photo Join LinkedIn To create a LinkedIn account, you must understand how LinkedIn processes your personal information by selecting learn more for each item listed. Agree to all terms We collect and use personal information. Learn more We share personal information with third parties to provide our services. Learn more Further information is available in our Korea Privacy Addendum . Privacy Policy Addendum 1 of 2 2 of 2 Agree to the term Continue Back Agree to all terms Email Password Show Keep me logged in First name Last name By clicking Agree & Join, you agree to the LinkedIn User Agreement , Privacy Policy , and Cookie Policy . Agree & Join or Security verification Already on LinkedIn? Sign in Looking to create a page for a business? Get help LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language | 2026-01-13T08:48:25 |
https://docs.devcycle.com/integrations/#devops | Integrations | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up On this page Integrations Welcome to DevCycle Integrations! Here you will find all of the various first party tools made with the DevCycle APIs, as well as third party integrations to connect DevCycle to the tools of your needs. Contributing to DevCycle or creating a new Integration: If you would like to contribute to an existing integration or tool, all of DevCycle's tools and integrations are open source on the DevCycle Github repository. Further, if you'd like to create a new tool or integration, a great starting point is DevCycle's Management API which allows you to modify and interact with features and more within a DevCycle project, as well as the DevCycle Bucketing API which is used to serve users features and variables (and powers the DevCycle SDKs!) Observability Dynatrace Monitor and analyze your feature flags with Dynatrace observability platform. OpenTelemetry Monitor and analyze your feature flags with OpenTelemetry. Snowflake Data Sharing Access your Organization's Event data on Snowflake Google Analytics Send DevCycle Feature/Variation data from Tag Manager to Google Analytics 4 for A/B test analysis Rollbar Enhance error logging with DevCycle Feature and Variable data IDE Plugins VSCode Extension Use DevCycle directly in Visual Studio Code. Interoperability OpenFeature Use DevCycle with the OpenFeature Flagging Standard. Feature Flag Importer Import resources from other feature flag providers. Webhooks Connect apps and services to DevCycle. Vercel Edge Config Upload DevCycle configurations to Vercel Edge Config for faster retrieval Code Analysis GitHub: Flag Code Usages Display code snippets for each variable used in a project. GitHub: Flag Change Insights Display added/removed flags on each Pull Request. Bitbucket: Flag Code Usages Display code snippets for each variable used in a project. Bitbucket: Flag Change Insights Display added/removed flags on each Pull Request. GitLab: Flag Code Usages Display code snippets for each variable used in a project. GitLab: Flag Change Insights Display added/removed flags on each Merge Request. Collaboration Tools Slack Connect DevCycle to your Slack workspace to track Feature updates. DevOps Jira: Flag Management Link Jira tickets directly to DecCycle features Terraform Provider Manage projects, features and more with Terraform Edit this page Last updated on Jan 9, 2026 Observability IDE Plugins Interoperability Code Analysis Collaboration Tools DevOps DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:25 |
https://www.linkedin.com/signup/cold-join?session_redirect=https%3A%2F%2Fwww%2Elinkedin%2Ecom%2Fsearch%2Fresults%2Fpeople%2F%3FfacetCurrentCompany%3D%255B73206845%255D&trk=public_biz_employees-join | Sign Up | LinkedIn Make the most of your professional life Not you? Remove photo Join LinkedIn To create a LinkedIn account, you must understand how LinkedIn processes your personal information by selecting learn more for each item listed. Agree to all terms We collect and use personal information. Learn more We share personal information with third parties to provide our services. Learn more Further information is available in our Korea Privacy Addendum . Privacy Policy Addendum 1 of 2 2 of 2 Agree to the term Continue Back Agree to all terms Email Password Show Keep me logged in First name Last name By clicking Agree & Join, you agree to the LinkedIn User Agreement , Privacy Policy , and Cookie Policy . Agree & Join or Security verification Already on LinkedIn? Sign in Looking to create a page for a business? Get help LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language | 2026-01-13T08:48:25 |
https://docs.devcycle.com/integrations/vercel-edge-config/ | Vercel Edge Config | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up On this page Vercel Edge Config The Vercel Edge Config integration allows you to automatically sync DevCycle flagging configurations to Vercel Edge Config , a lightning fast data storage system optimized for deployments running on Vercel. With this integration, DevCycle SDKs running in Vercel can obtain flag configurations faster than ever, reducing latency and improving your user experience. Prerequisites The Edge Config integration is currently available for the following SDKs: Node.js Next.js Using the integration requires a Vercel account, an application running in that account which is using one of the above SDKs, and an Edge Config connected to a project in Vercel . info Using this integration will count towards your usage of Edge Config in Vercel and is subject to billing in your Vercel account. There are also limits to the size of data that can be stored in Edge Config. You can see the limit your plan allows on the Limits and Pricing page. We recommend using a separate Edge Config specifically for storing DevCycle configurations in order to allocate as much storage as possible. We also recommend having a Pro or Enterprise plan, as a typical DevCycle configuration will not fit within the hobby plan size limit. The configuration size will grow with the number of flags in your project, and heavy users may require an enterprise plan to fit their configuration. If your Edge Config cannot store your project's configuration after the integration has been set up, we will reach out to you with more information. Setup Configure Integration To get started, visit the integration's page on Vercel and click "Add Integration". This will open a separate window which will load the setup form on the DevCycle dashboard. If you don't already have a DevCycle account, you will be taken through the signup process. Once you've created your account and Organization, you'll be brought back to the integration setup. Once logged in, you can select which projects in DevCycle you want to sync to Edge Config, and which Edge Config to sync them to. If you don't have an Edge Config already set up, one will be created for you with the name "devcycle" during the configuration flow. You can also create an Edge Config ahead of time by following Vercel's documentation . After you have made your selections, hit "Submit" to finish configuring the integration. Connect a Vercel Project To use the integration in your application, you must connect the desired Edge Config in Vercel to the Vercel project where you will be running DevCycle. To do so, navigate to the "Storage" tab in the Vercel Dashboard, click on the Edge Config you want to connect, and visit the "Projects" section in the sidebar. See the Vercel docs for more information Once a project has been connected, an environment variable called EDGE_CONFIG will be set in that project which can be used in the following steps to connect to your Edge Config. In order to set this variable locally for testing, make sure to pull down the latest environment variables using the Vercel CLI by executing the following in your project's directory: vercel env pull If you do not have the Vercel CLI set up for this project, follow their steps to link the CLI to your Vercel Project Setup SDK If you haven't already installed the DevCycle Node.js or Next.js SDK you can follow the installation and usage guides for those SDKs in our documentation here . You can also find helpful setup information like where to find DevCycle SDK keys in our Quickstart Tutorial . In order to use the integration in a DevCycle SDK, you must install the @devcycle/vercel-edge-config package and provide it during SDK initialization. Using that package requires the @vercel/edge-config package to be installed as well: npm install @devcycle/vercel-edge-config @vercel/edge-config or yarn add @devcycle/vercel-edge-config @vercel/edge-config Follow the SDK-specific instructions below: Node.js For more information on Node SDK usage, see the docs import { createClient } from '@vercel/edge-config' import { EdgeConfigSource } from '@devcycle/vercel-edge-config' import { initializeDevCycle } from '@devcycle/nodejs-server-sdk' // the EDGE_CONFIG environment variable contains a connection string for a particular edge config. It is set automatically // when you connect an edge config to a project in Vercel. const edgeClient = createClient ( process . env . EDGE_CONFIG ) const edgeConfigSource = new EdgeConfigSource ( edgeClient ) const devcycleClient = initializeDevCycle ( process . env . DEVCYCLE_SERVER_SDK_KEY , // pass the edgeConfigSource as the "configSource" option during SDK intialization to tell the SDK to use Edge Config // for retrieving its configuration { configSource : edgeConfigSource } ) Now the SDK will retrieve its configuration from Edge Config. That's it! Next.js For more information on Next.js SDK usage, see the docs App Router import { createClient } from '@vercel/edge-config' import { EdgeConfigSource } from '@devcycle/vercel-edge-config' import { setupDevCycle } from '@devcycle/nextjs-sdk/server' const edgeClient = createClient ( process . env . EDGE_CONFIG ) const edgeConfigSource = new EdgeConfigSource ( edgeClient ) export const { getVariableValue , getClientContext } = setupDevCycle ( { serverSDKKey : process . env . DEVCYCLE_SERVER_SDK_KEY ?? '' , clientSDKKey : process . env . NEXT_PUBLIC_DEVCYCLE_CLIENT_SDK_KEY ?? '' , userGetter : ( ) => ( { user_id : 'test_user' } ) , options : { // pass the configSource option with the instance of EdgeConfigSource configSource : edgeConfigSource } } ) Pages Router import { createClient } from '@vercel/edge-config' import { EdgeConfigSource } from '@devcycle/vercel-edge-config' import { getServerSideDevCycle } from '@devcycle/nextjs-sdk/pages' const edgeClient = createClient ( process . env . EDGE_CONFIG ) const edgeConfigSource = new EdgeConfigSource ( edgeClient ) export const getServerSideProps : GetServerSideProps = async ( context ) => { const user = { user_id : 'server-user' , } return { props : { ... ( await getServerSideDevCycle ( { serverSDKKey : process . env . DEVCYCLE_SERVER_SDK_KEY || '' , clientSDKKey : process . env . NEXT_PUBLIC_DEVCYCLE_CLIENT_SDK_KEY || '' , user , context , options : { // pass the configSource option with the instance of EdgeConfigSource configSource : edgeConfigSource } } ) ) , } , } } Edit this page Last updated on Jan 9, 2026 Prerequisites Setup Configure Integration Connect a Vercel Project Setup SDK DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:25 |
https://www.linkedin.com/signup/cold-join?session_redirect=https%3A%2F%2Fwww%2Elinkedin%2Ecom%2Fsearch%2Fresults%2Fpeople%2F%3FfacetCurrentCompany%3D%255B73206845%255D&trk=org-employees_cta_face-pile-cta | Sign Up | LinkedIn Make the most of your professional life Not you? Remove photo Join LinkedIn To create a LinkedIn account, you must understand how LinkedIn processes your personal information by selecting learn more for each item listed. Agree to all terms We collect and use personal information. Learn more We share personal information with third parties to provide our services. Learn more Further information is available in our Korea Privacy Addendum . Privacy Policy Addendum 1 of 2 2 of 2 Agree to the term Continue Back Agree to all terms Email Password Show Keep me logged in First name Last name By clicking Agree & Join, you agree to the LinkedIn User Agreement , Privacy Policy , and Cookie Policy . Agree & Join or Security verification Already on LinkedIn? Sign in Looking to create a page for a business? Get help LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language Takes less than 2 minutes Join LinkedIn to connect with people, jobs and opportunities that matter Join now Leave | 2026-01-13T08:48:25 |
https://www.linkedin.com/signup/cold-join?session_redirect=https%3A%2F%2Fwww%2Elinkedin%2Ecom%2Fcompany%2Fsuprsend&trk=organization_guest_main-feed-card_comment-cta | Sign Up | LinkedIn Join LinkedIn Make the most of your professional life Not you? Remove photo Join LinkedIn To create a LinkedIn account, you must understand how LinkedIn processes your personal information by selecting learn more for each item listed. Agree to all terms We collect and use personal information. Learn more We share personal information with third parties to provide our services. Learn more Further information is available in our Korea Privacy Addendum . Privacy Policy Addendum 1 of 2 2 of 2 Agree to the term Continue Back Agree to all terms By clicking Agree & Join, you agree to the LinkedIn User Agreement , Privacy Policy , and Cookie Policy . or Email Password Show First name Last name Agree & Join Security verification Already on LinkedIn? Sign in Looking to create a page for a business? Get help LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language Follow top companies Over 60% of the fortune 100 companies use LinkedIn to hire. Join now Leave | 2026-01-13T08:48:25 |
https://docs.devcycle.com/sdk/server-side-sdks/nestjs | NestJS SDK | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up SDK Overview SDK Lifecycle SDK Features Client-side SDKS Server-side SDKS Node.js SDK NestJS SDK Installation Getting Started Usage OpenFeature Typescript Example App PHP SDK Go SDK Ruby SDK Python SDK Java SDK .NET SDK SDK Proxy Server-side SDKS NestJS SDK DevCycle NestJS Server SDK The NestJS SDK supports Local Bucketing mode by default and performs fast local evaluations of your feature flags. Installation Installing the SDK Getting Started Initializing the SDK Usage Using the SDK OpenFeature How to implement the OpenFeature Provider Typescript SDK features for Typescript users Example App Try it out for yourself The SDK is available as a package on NPM, will a full Typescript interface. It is also open source and can be viewed on the DevCycle GitHub . Edit this page Last updated on Jan 9, 2026 Previous Example App Next Installation DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:25 |
https://docs.devcycle.com/integrations/rollbar | Rollbar | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up On this page Rollbar Rollbar is a tool used for error logging and real-time performance tracking for your applications. Rollbar provides you with the ability to capture detailed information on errors to help diagnose and resolve issues faster. Enrich your logs further by including DevCycle Feature data into your error logging. The DevCycle Rollbar integration enhances error tracking by adding feature configuration data directly to your Rollbar error logs. By sending DevCycle Feature and Variable data from the DevCycle SDKs to Rollbar, developers can gain valuable insights into the specific feature configuration that was delivered to a user during an error. Configuration Including DevCycle Features in your Rollbar Config Include DevCycle Feature data to the initialization of Rollbar to allow all Rollbar errors to be populated with the specific DevCycle feature configuration at that time of the error. The exact DevCycle data and format that you pass to Rollbar can be easily configured, so feel free to experiment with the data that's available on your SDK. In our example below, we supply all Features and Variables that the user/device received to the Rollbar config. Steps : Get all Features and/or all Variables from the DevCycle SDK. Create a custom field called devCycleSettings within your Rollbar config payload. Add your Features and Variables to the devCycleSettings object. import { Provider , useRollbar } from '@rollbar / react import { useDevCycleClient , useIsDevCycleInitialized , useVariableValue , withDevCycleProvider } from '@devcycle/react-client-sdk' ... function MyComponent ( ) { const devCycleClient = useDevCycleClient ( ) const devCycleFeatures = devCycleClient . allFeatures ( ) const devCycleVariables = devCycleClient . allVariables ( ) const rollbarConfig = { accessToken : 'YOUR_ROLLBAR_CLIENT_ACCESS_TOKEN' , captureUncaught : true , captureUnhandledRejections : true , environment : 'production' , payload : { custom : { devCycleSettings : { features : devCycleFeatures , // this will send all DevCycle features in the error payload to Rollbar variables : devCycleVariables // this will send all DevCycle variables in the error payload to Rollbar } } } } return ( < Provider config = { rollbarConfig } > < TestError /> </ Provider > } function App ( ) { const devcycleReady = useIsDevCycleInitialized ( ) if ( ! devcycleReady ) return < div > < h1 > DevCycle is not ready! Loading State... </ h1 > </ div > return ( < > < div > < Router > < Routes > < Route path = " / " element = { < MyComponent /> } /> </ Routes > </ Router > </ div > </ > ) } export default withDevCycleProvider ( { sdkKey : 'YOUR_DEVCYCLE_SDK_KEY' , user : { user_id : 'USER_ID' , isAnonymous : false } } ) ( App ) Including DevCycle Features on Specific Errors Rollbar allows you to define extra properties for an error. Instead of providing all Feature data on initialization, you may want to supply DevCycle Feature data to specific errors of you choice. In our example below, we're using DevCycle to determine whether a user should receive a new Feature with new behavior or the existing old behavior. If there is an error running any of those behaviors, we're logging an error to Rollbar and supplying all DevCycle Features to the error as an extra property. Steps : Get all Features and/or all Variables from the DevCycle SDK. In your rollbar.error properties, add a custom field (ex: devCycleFeature ) containing your Feature or Variable data. Example: const rollbar = useRollbar ( ) ; const variableValue = useVariableValue ( 'variable_key' , false ) try { if ( variableValue ) { testNewBehavior ( ) } else { oldBehavior ( ) } } catch ( error ) { if ( variableValue ) { const devcycleClient = useDevCycleClient ( ) const features = devcycleClient . allFeatures ( ) rollbar . error ( error , { devCycleFeature : { name : 'New Feature' , id : features [ 'feature-key' ] [ '_id' ] } } ) } } Service Links Rollbar service links allow you to create links that connect directly with DevCycle, to provide easy access to Features and Variables from the Rollbar interface. To learn how to create service links for DevCycle, visit the Rollbar docs here . Edit this page Last updated on Jan 9, 2026 Configuration Including DevCycle Features in your Rollbar Config Including DevCycle Features on Specific Errors Service Links DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:25 |
https://www.linkedin.com/checkpoint/lg/login?session_redirect=https%3A%2F%2Fwww%2Elinkedin%2Ecom%2FshareArticle%3Fmini%3Dtrue%26url%3Dhttps%253A%252F%252Fdev%2Eto%252Fcodebunny20%252Flooking-for-help-if-possible-im-stuck-on-my-trackmyhrt-app-medication-symptom-tracker-38fa%26title%3D%25F0%259F%258C%2588%2520Looking%2520for%2520help%2520if%2520possible%253A%2520I%25E2%2580%2599m%2520Stuck%2520on%2520My%2520TrackMyHRT%2520App%2520%2528Medication%2520%252B%2520Symptom%2520Tracker%2529%26summary%3DHey%2520devs%2520%25E2%2580%2594%2520I%25E2%2580%2599m%2520working%2520on%2520a%2520small%252C%2520offline%252C%2520privacy%25E2%2580%2591first%2520desktop%2520app%2520called%2520TrackMyHRT%252C%2520and%2520I%25E2%2580%2599ve%2520hit%2E%2E%2E%26source%3DDEV%2520Community&fromSignIn=true&trk=reset_password | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T08:48:25 |
https://www.linkedin.com/jobs/suprsend-jobs-worldwide?f_C=73206845&trk=top-card_top-card-primary-button-top-card-primary-cta | 2 Suprsend jobs in Worldwide Agree & Join LinkedIn By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Skip to main content LinkedIn Suprsend in Worldwide Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Sign in Join now for free SuprSend Clear text SuprSend (2) Done Any time Any time (2) Done Job type Full-time (2) Done Experience level Entry level (1) Mid-Senior level (1) Done Remote On-site (2) Done Reset Get notified when a new job is posted. Set alert Sign in to set job alerts for “Suprsend” roles. Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now SuprSend jobs 2 Suprsend Jobs in Worldwide UI / UX Designer UI / UX Designer SuprSend Bengaluru, Karnataka, India 1 month ago Product Marketing Manager Product Marketing Manager SuprSend Bengaluru, Karnataka, India 1 month ago Sign in to view all job postings Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language You’re signed out Sign in for the full experience. Sign in Join now | 2026-01-13T08:48:25 |
https://www.linkedin.com/signup/cold-join?session_redirect=https%3A%2F%2Fwww.linkedin.com%2FshareArticle%3Fmini%3Dtrue%26url%3Dhttps%253A%252F%252Fdev.to%252Fcodebunny20%252Flooking-for-help-if-possible-im-stuck-on-my-trackmyhrt-app-medication-symptom-tracker-38fa%26title%3D%25F0%259F%258C%2588%2520Looking%2520for%2520help%2520if%2520possible%253A%2520I%25E2%2580%2599m%2520Stuck%2520on%2520My%2520TrackMyHRT%2520App%2520%2528Medication%2520%252B%2520Symptom%2520Tracker%2529%26summary%3DHey%2520devs%2520%25E2%2580%2594%2520I%25E2%2580%2599m%2520working%2520on%2520a%2520small%252C%2520offline%252C%2520privacy%25E2%2580%2591first%2520desktop%2520app%2520called%2520TrackMyHRT%252C%2520and%2520I%25E2%2580%2599ve%2520hit...%26source%3DDEV%2520Community | Sign Up | LinkedIn Make the most of your professional life Not you? Remove photo Join LinkedIn To create a LinkedIn account, you must understand how LinkedIn processes your personal information by selecting learn more for each item listed. Agree to all terms We collect and use personal information. Learn more We share personal information with third parties to provide our services. Learn more Further information is available in our Korea Privacy Addendum . Privacy Policy Addendum 1 of 2 2 of 2 Agree to the term Continue Back Agree to all terms Email Password Show First name Last name By clicking Agree & Join, you agree to the LinkedIn User Agreement , Privacy Policy , and Cookie Policy . Agree & Join or Security verification Already on LinkedIn? Sign in Looking to create a page for a business? Get help LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language | 2026-01-13T08:48:25 |
https://docs.devcycle.com/sdk/#theme-svg-external-link | SDK Overview | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up SDK Overview SDK Lifecycle SDK Features Client-side SDKS Server-side SDKS SDK Proxy SDK Overview SDK Overview DevCycle has both client-side and server-side SDKs. This page describes the differences between these SDK types. Implementation and usage change depending on which type of SDK is being used. tip Explore our SDK Features and Functionality to discover how to implement your solutions using the DevCycle SDKs. Client Side SDKs DevCycle client-side SDKs are meant for single-user contexts, such as web browsers and mobile apps. These SDKs retrieve their configuration for the current user when they are initialized and any time the user is re-identified. They also receive updates in real time when configuration is changed in the DevCycle platform. The current Client-Side SDKs are: JavaScript SDK React SDK Next.js SDK Angular SDK iOS SDK Android SDK React Native SDK Flutter SDK Roku SDK Server-Side SDKs Server-side SDKs are used in multi-user contexts such as backend services, where each call to the SDK will likely be for a different user. The user's ID and any other targeting information must be passed in on every SDK function call. The current Server-Side SDKs are: NodeJS SDK NestJS SDK Go SDK PHP SDK Python SDK Ruby SDK Java SDK .NET SDK OpenFeature Providers OpenFeature is an open standard that provides a vendor-agnostic, community-driven SDKs for feature flagging that works natively with DevCycle. Client-Side JavaScript React Angular iOS Android Server-Side NodeJS NestJS Go Ruby Java .NET / C# Python PHP Edit this page Last updated on Jan 9, 2026 Next SDK Lifecycle DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:25 |
https://www.linkedin.com/signup/cold-join?session_redirect=https%3A%2F%2Fwww%2Elinkedin%2Ecom%2Fcompany%2Fsuprsend&trk=organization_guest_main-feed-card_social-actions-reactions | Sign Up | LinkedIn Join LinkedIn now — it’s free! Not you? Remove photo Join LinkedIn To create a LinkedIn account, you must understand how LinkedIn processes your personal information by selecting learn more for each item listed. Agree to all terms We collect and use personal information. Learn more We share personal information with third parties to provide our services. Learn more Further information is available in our Korea Privacy Addendum . Privacy Policy Addendum 1 of 2 2 of 2 Agree to the term Continue Back Agree to all terms Email Password Show Keep me logged in First name Last name By clicking Agree & Join, you agree to the LinkedIn User Agreement , Privacy Policy , and Cookie Policy . Agree & Join or Security verification Already on LinkedIn? Sign in Looking to create a page for a business? Get help LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language | 2026-01-13T08:48:25 |
https://t.co/XfoMa0Vsqt | JavaScript is not available. We’ve detected that JavaScript is disabled in this browser. Please enable JavaScript or switch to a supported browser to continue using x.com. You can see a list of supported browsers in our Help Center. Help Center Terms of Service Privacy Policy Cookie Policy Imprint Ads info © 2026 X Corp. Something went wrong, but don’t fret — let’s give it another shot. Try again Some privacy related extensions may cause issues on x.com. Please disable them and try again. | 2026-01-13T08:48:25 |
https://docs.devcycle.com/integrations/#theme-svg-external-link | Integrations | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up On this page Integrations Welcome to DevCycle Integrations! Here you will find all of the various first party tools made with the DevCycle APIs, as well as third party integrations to connect DevCycle to the tools of your needs. Contributing to DevCycle or creating a new Integration: If you would like to contribute to an existing integration or tool, all of DevCycle's tools and integrations are open source on the DevCycle Github repository. Further, if you'd like to create a new tool or integration, a great starting point is DevCycle's Management API which allows you to modify and interact with features and more within a DevCycle project, as well as the DevCycle Bucketing API which is used to serve users features and variables (and powers the DevCycle SDKs!) Observability Dynatrace Monitor and analyze your feature flags with Dynatrace observability platform. OpenTelemetry Monitor and analyze your feature flags with OpenTelemetry. Snowflake Data Sharing Access your Organization's Event data on Snowflake Google Analytics Send DevCycle Feature/Variation data from Tag Manager to Google Analytics 4 for A/B test analysis Rollbar Enhance error logging with DevCycle Feature and Variable data IDE Plugins VSCode Extension Use DevCycle directly in Visual Studio Code. Interoperability OpenFeature Use DevCycle with the OpenFeature Flagging Standard. Feature Flag Importer Import resources from other feature flag providers. Webhooks Connect apps and services to DevCycle. Vercel Edge Config Upload DevCycle configurations to Vercel Edge Config for faster retrieval Code Analysis GitHub: Flag Code Usages Display code snippets for each variable used in a project. GitHub: Flag Change Insights Display added/removed flags on each Pull Request. Bitbucket: Flag Code Usages Display code snippets for each variable used in a project. Bitbucket: Flag Change Insights Display added/removed flags on each Pull Request. GitLab: Flag Code Usages Display code snippets for each variable used in a project. GitLab: Flag Change Insights Display added/removed flags on each Merge Request. Collaboration Tools Slack Connect DevCycle to your Slack workspace to track Feature updates. DevOps Jira: Flag Management Link Jira tickets directly to DecCycle features Terraform Provider Manage projects, features and more with Terraform Edit this page Last updated on Jan 9, 2026 Observability IDE Plugins Interoperability Code Analysis Collaboration Tools DevOps DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:25 |
https://www.linkedin.com/signup/cold-join?session_redirect=https%3A%2F%2Fwww.linkedin.com%2Ffeed%2Fhashtag%2Fhiring&trk=organization_guest_main-feed-card-text | Sign Up | LinkedIn Join LinkedIn now — it’s free! Not you? Remove photo Join LinkedIn To create a LinkedIn account, you must understand how LinkedIn processes your personal information by selecting learn more for each item listed. Agree to all terms We collect and use personal information. Learn more We share personal information with third parties to provide our services. Learn more Further information is available in our Korea Privacy Addendum . Privacy Policy Addendum 1 of 2 2 of 2 Agree to the term Continue Back Agree to all terms Email Password Show Remember me First name Last name By clicking Agree & Join, you agree to the LinkedIn User Agreement , Privacy Policy , and Cookie Policy . Agree & Join or Security verification Already on LinkedIn? Sign in Looking to create a page for a business? Get help LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language | 2026-01-13T08:48:25 |
https://docs.devcycle.com/platform/extras/webhooks/ | Webhooks | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up Home Getting Started Essentials DevCycle Overview Key Features System Architecture Feature Hierarchy Feature Types Platform Feature Flags Experimentation Account Management Security and Guardrails Testing and QA Extras Custom Domains Feature Opt-In Self-Hosted Feature Flags with DevCycle Webhooks Examples Platform Extras Webhooks On this page Webhooks This topic explains how to create and use Webhooks in DevCycle. Webhooks allow you to build your own integrations that subscribe to Feature changes in DevCycle. Use Webhooks to update external ticket trackers, notify teammates of new features, targeting changes, and more. Outbound Webhooks Creating a Webhook To create a Webhook: Navigate to the Integrations page. Navigate to the "Webhooks" section and click + New Webhook . The "Create a Webhook" modal appears. Give the Webhook a human-readable name. (Optional) Give the Webhook a description. Enter a Payload URL. Click Create Webhook . From there, you will be taken to the Webhook details page. Select if you'd like events sent for all Features in your project or a single Feature. Select which events will be sent through the Webhook. Click Save . Example Payload Below is the type definition for the payload that gets sent to the Webhook url: /** * The 'newContents' and 'previousContents' type is a subset of the resource * that was changed */ export type AuditLogChange = { type : string newContents : Record < string , unknown > | null previousContents : Record < string , unknown > | null _environments ? : string [ ] metadata ? : Record < string , unknown > } type User = { name ? : string email : string } type WebhookPayload = { /** * An array of types that were triggered, the 'changes' property * should have all these events in this array */ events : string [ ] /** * The key of the Feature */ key ? : string /** * The key of the project */ projectId : string /** * The version of the payload so we can have different versions * in the future */ version : string /** * The changes that were made */ changes : AuditLogChange [ ] /** * The date this Webhook triggered the URL on */ date : Date /** * The user that triggered the change */ user : User } For example, a user edits a Feature’s key and adds a new variable, the data posted to the user’s Webhook URL would be: { "events" : [ "modifiedFeature" , "addedVariable" ] , "key" : "feature-key" , "date" : "2024-01-16T18:30:42.796Z" , "user" : { "name" : "Jason" , "email" : " [email protected] " } , "version" : "1" "changes" : [ { "type" : "modifiedFeature" , "newContents" : { "key" : "new-feature-key" } , "previousContents" : { "key" : "feature-key" } } , { "type" : "addedVariable" , "newContents" : { ... // new variable object } , "previousContents" : null } , ] } Testing a Webhook To test a Webhook: Navigate to the Integrations page. Navigate to the "Webhooks" section. Click the expand arrows next to the Add integration button. Navigate to the Test section of the Webhook details page. Click Test Connection to verify the Webhook Url is accessible. The API response will be displayed below. Deleting a Webhook To delete a Webhook: Navigate to the Integrations page. Navigate to the "Webhooks" section. Click on the Webhook that you wish to delete. Navigate to the Settings section of the Webhook details page. Click Delete Webhook . A confirmation modal will appear. Click Delete . Inbound Webhooks (Coming Soon) This feature will allow the user to create Webhook urls for certain actions, like turning on/off a Feature in production. If you would like this feature, contact [email protected] ! Edit this page Last updated on Jan 9, 2026 Previous Self-Hosted Feature Flags with DevCycle Next Examples Outbound Webhooks Creating a Webhook Example Payload Testing a Webhook Deleting a Webhook Inbound Webhooks (Coming Soon) DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:25 |
https://docs.devcycle.com/integrations/gitlab/pr-insights-action | GitLab: Feature Flag Change Insights on Merge Request | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up On this page GitLab: Feature Flag Change Insights on Merge Request Get the integration here: https://gitlab.com/devcycle/devcycle-pr-insights-ci-cd Overview With this GitLab CI/CD pipeline, information on which DevCycle features have been added or removed in a code change will be shown directly on each Merge Request as a comment. Note: This is intended to run for all merge requests. Example Output Access Tokens This pipeline uses the GitLab API to add comments to a Merge Requests. To do this, it requires a GitLab access token with the api scope. GitLab provides different types of access tokens, but we recommend using a project access token for this pipeline. If your GitLab plan does not support project access tokens, a personal access token can be used instead. To create a project access token, follow the instuctions outlined in the GitLab documentation . To create a personal access token, follow the instuctions outlined in the GitLab documentation . The access token should be stored as a GitLab CI/CD variable in your project settings. To do this, navigate to your project settings, select CI/CD from the left sidebar, and then select Variables . From here, you can add a new variable with the name GITLAB_ACCESS_TOKEN and the value of your access token. Usage Create a new .gitlab-ci.yml file in your GitLab repository or update the existing one. Add the code_usages stage and paste the following code into a code_usages: pr_insights : stage : pr_insights image : devcycleinfra/devcycle - pr - insights - gitlab : latest script : - git fetch origin $CI_MERGE_REQUEST_TARGET_BRANCH_NAME - git fetch origin $CI_MERGE_REQUEST_SOURCE_BRANCH_NAME - node /devcycle - pr - insights - ci - cd rules : - if : $CI_PIPELINE_SOURCE == 'merge_request_event' Your DevCycle API credentials and project token are required to update the DevCycle dashboard. When referencing your API client ID and secret, we recommend using GitLab CI/CD variables to store your credentials securely. Environment Variables Your DevCycle API credentials and project token are required to update the DevCycle dashboard. These should be set as environment variables in your GitLab project settings: Variable Description DEVCYCLE_PROJECT_KEY Your DevCycle project key, see Projects DEVCYCLE_CLIENT_ID Your organization's API client ID, see Organization Settings DEVCYCLE_CLIENT_SECRET Your organization's API client secret, see Organization Settings When setting these environment variables, we recommend you protect them to ensure they're only exposed to protected branches or tags and mask them to hide their values in job logs. Usage Set the necessary environment variables in your GitLab project settings as described above. Add the provided .gitlab-ci.yaml to your project root. Push your changes. The pipeline should run automatically on any merge request. Support For any issues, feedback, or questions, please feel free to open an issue on this repository. Edit this page Overview Example Output Access Tokens Usage Environment Variables Usage Support DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:25 |
https://docs.devcycle.com/integrations/#interoperability | Integrations | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up On this page Integrations Welcome to DevCycle Integrations! Here you will find all of the various first party tools made with the DevCycle APIs, as well as third party integrations to connect DevCycle to the tools of your needs. Contributing to DevCycle or creating a new Integration: If you would like to contribute to an existing integration or tool, all of DevCycle's tools and integrations are open source on the DevCycle Github repository. Further, if you'd like to create a new tool or integration, a great starting point is DevCycle's Management API which allows you to modify and interact with features and more within a DevCycle project, as well as the DevCycle Bucketing API which is used to serve users features and variables (and powers the DevCycle SDKs!) Observability Dynatrace Monitor and analyze your feature flags with Dynatrace observability platform. OpenTelemetry Monitor and analyze your feature flags with OpenTelemetry. Snowflake Data Sharing Access your Organization's Event data on Snowflake Google Analytics Send DevCycle Feature/Variation data from Tag Manager to Google Analytics 4 for A/B test analysis Rollbar Enhance error logging with DevCycle Feature and Variable data IDE Plugins VSCode Extension Use DevCycle directly in Visual Studio Code. Interoperability OpenFeature Use DevCycle with the OpenFeature Flagging Standard. Feature Flag Importer Import resources from other feature flag providers. Webhooks Connect apps and services to DevCycle. Vercel Edge Config Upload DevCycle configurations to Vercel Edge Config for faster retrieval Code Analysis GitHub: Flag Code Usages Display code snippets for each variable used in a project. GitHub: Flag Change Insights Display added/removed flags on each Pull Request. Bitbucket: Flag Code Usages Display code snippets for each variable used in a project. Bitbucket: Flag Change Insights Display added/removed flags on each Pull Request. GitLab: Flag Code Usages Display code snippets for each variable used in a project. GitLab: Flag Change Insights Display added/removed flags on each Merge Request. Collaboration Tools Slack Connect DevCycle to your Slack workspace to track Feature updates. DevOps Jira: Flag Management Link Jira tickets directly to DecCycle features Terraform Provider Manage projects, features and more with Terraform Edit this page Last updated on Jan 9, 2026 Observability IDE Plugins Interoperability Code Analysis Collaboration Tools DevOps DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:25 |
https://docs.devcycle.com/examples | DevCycle Example Apps | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up Home Getting Started Essentials DevCycle Overview Key Features System Architecture Feature Hierarchy Feature Types Platform Feature Flags Experimentation Account Management Security and Guardrails Testing and QA Extras Examples Examples On this page DevCycle Example Apps Welcome to the Example Apps page, which showcases example applications using the DevCycle SDKs. The goal of this page is to provide developers with a comprehensive collection of example applications that demonstrate how to utilize DevCycle's SDKs with a variety of programming languages and frameworks. Client side JavaScript React Next.js - App Router Vue JS MacOS tvOS Flutter Roku Server Side Local Bucketing ( See here for more explanation ) Node.js Go PHP Python Ruby Java .NET NestJS Cloud Bucketing ( See here for more explanation ) Node.js Go Ruby Java .NET Mobile iOS (Objective C) iOS (Swift) Android (Java) Android (Kotlin) Edit this page Last updated on Jan 9, 2026 Previous Webhooks Client side Server Side Local Bucketing Cloud Bucketing Mobile DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:25 |
https://docs.devcycle.com/sdk/server-side-sdks/python | Python SDK | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up SDK Overview SDK Lifecycle SDK Features Client-side SDKS Server-side SDKS Node.js SDK NestJS SDK PHP SDK Go SDK Ruby SDK Python SDK Installation Getting Started Usage OpenFeature Example App Java SDK .NET SDK SDK Proxy Server-side SDKS Python SDK DevCycle Python Server SDK Welcome to the DevCycle Python Server SDK. There are two modes for the SDK, Local Bucketing (using the local bucketing engine) and Cloud bucketing (using the DevCycle Bucketing API ). We recommend using the Local Bucketing mode by default, as it performs fast local evaluations of your feature flags. If you need access to EdgeDB you will need to use the Cloud Bucketing mode of the SDK. Installation Installing the SDK Getting Started Initializing the SDK Usage Using the SDK OpenFeature How to implement the OpenFeature Provider Example App Try it out for yourself The SDK is available as a package on PyPI. It is also open source and can be viewed on Github. Edit this page Last updated on Jan 9, 2026 Previous Example App Next Installation DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:25 |
https://docs.devcycle.com/integrations/#observability | Integrations | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up On this page Integrations Welcome to DevCycle Integrations! Here you will find all of the various first party tools made with the DevCycle APIs, as well as third party integrations to connect DevCycle to the tools of your needs. Contributing to DevCycle or creating a new Integration: If you would like to contribute to an existing integration or tool, all of DevCycle's tools and integrations are open source on the DevCycle Github repository. Further, if you'd like to create a new tool or integration, a great starting point is DevCycle's Management API which allows you to modify and interact with features and more within a DevCycle project, as well as the DevCycle Bucketing API which is used to serve users features and variables (and powers the DevCycle SDKs!) Observability Dynatrace Monitor and analyze your feature flags with Dynatrace observability platform. OpenTelemetry Monitor and analyze your feature flags with OpenTelemetry. Snowflake Data Sharing Access your Organization's Event data on Snowflake Google Analytics Send DevCycle Feature/Variation data from Tag Manager to Google Analytics 4 for A/B test analysis Rollbar Enhance error logging with DevCycle Feature and Variable data IDE Plugins VSCode Extension Use DevCycle directly in Visual Studio Code. Interoperability OpenFeature Use DevCycle with the OpenFeature Flagging Standard. Feature Flag Importer Import resources from other feature flag providers. Webhooks Connect apps and services to DevCycle. Vercel Edge Config Upload DevCycle configurations to Vercel Edge Config for faster retrieval Code Analysis GitHub: Flag Code Usages Display code snippets for each variable used in a project. GitHub: Flag Change Insights Display added/removed flags on each Pull Request. Bitbucket: Flag Code Usages Display code snippets for each variable used in a project. Bitbucket: Flag Change Insights Display added/removed flags on each Pull Request. GitLab: Flag Code Usages Display code snippets for each variable used in a project. GitLab: Flag Change Insights Display added/removed flags on each Merge Request. Collaboration Tools Slack Connect DevCycle to your Slack workspace to track Feature updates. DevOps Jira: Flag Management Link Jira tickets directly to DecCycle features Terraform Provider Manage projects, features and more with Terraform Edit this page Last updated on Jan 9, 2026 Observability IDE Plugins Interoperability Code Analysis Collaboration Tools DevOps DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:25 |
https://docs.devcycle.com/integrations/gitlab/pr-insights-action/ | GitLab: Feature Flag Change Insights on Merge Request | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up On this page GitLab: Feature Flag Change Insights on Merge Request Get the integration here: https://gitlab.com/devcycle/devcycle-pr-insights-ci-cd Overview With this GitLab CI/CD pipeline, information on which DevCycle features have been added or removed in a code change will be shown directly on each Merge Request as a comment. Note: This is intended to run for all merge requests. Example Output Access Tokens This pipeline uses the GitLab API to add comments to a Merge Requests. To do this, it requires a GitLab access token with the api scope. GitLab provides different types of access tokens, but we recommend using a project access token for this pipeline. If your GitLab plan does not support project access tokens, a personal access token can be used instead. To create a project access token, follow the instuctions outlined in the GitLab documentation . To create a personal access token, follow the instuctions outlined in the GitLab documentation . The access token should be stored as a GitLab CI/CD variable in your project settings. To do this, navigate to your project settings, select CI/CD from the left sidebar, and then select Variables . From here, you can add a new variable with the name GITLAB_ACCESS_TOKEN and the value of your access token. Usage Create a new .gitlab-ci.yml file in your GitLab repository or update the existing one. Add the code_usages stage and paste the following code into a code_usages: pr_insights : stage : pr_insights image : devcycleinfra/devcycle - pr - insights - gitlab : latest script : - git fetch origin $CI_MERGE_REQUEST_TARGET_BRANCH_NAME - git fetch origin $CI_MERGE_REQUEST_SOURCE_BRANCH_NAME - node /devcycle - pr - insights - ci - cd rules : - if : $CI_PIPELINE_SOURCE == 'merge_request_event' Your DevCycle API credentials and project token are required to update the DevCycle dashboard. When referencing your API client ID and secret, we recommend using GitLab CI/CD variables to store your credentials securely. Environment Variables Your DevCycle API credentials and project token are required to update the DevCycle dashboard. These should be set as environment variables in your GitLab project settings: Variable Description DEVCYCLE_PROJECT_KEY Your DevCycle project key, see Projects DEVCYCLE_CLIENT_ID Your organization's API client ID, see Organization Settings DEVCYCLE_CLIENT_SECRET Your organization's API client secret, see Organization Settings When setting these environment variables, we recommend you protect them to ensure they're only exposed to protected branches or tags and mask them to hide their values in job logs. Usage Set the necessary environment variables in your GitLab project settings as described above. Add the provided .gitlab-ci.yaml to your project root. Push your changes. The pipeline should run automatically on any merge request. Support For any issues, feedback, or questions, please feel free to open an issue on this repository. Edit this page Overview Example Output Access Tokens Usage Environment Variables Usage Support DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:25 |
https://docs.devcycle.com/integrations/vercel-edge-config | Vercel Edge Config | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up On this page Vercel Edge Config The Vercel Edge Config integration allows you to automatically sync DevCycle flagging configurations to Vercel Edge Config , a lightning fast data storage system optimized for deployments running on Vercel. With this integration, DevCycle SDKs running in Vercel can obtain flag configurations faster than ever, reducing latency and improving your user experience. Prerequisites The Edge Config integration is currently available for the following SDKs: Node.js Next.js Using the integration requires a Vercel account, an application running in that account which is using one of the above SDKs, and an Edge Config connected to a project in Vercel . info Using this integration will count towards your usage of Edge Config in Vercel and is subject to billing in your Vercel account. There are also limits to the size of data that can be stored in Edge Config. You can see the limit your plan allows on the Limits and Pricing page. We recommend using a separate Edge Config specifically for storing DevCycle configurations in order to allocate as much storage as possible. We also recommend having a Pro or Enterprise plan, as a typical DevCycle configuration will not fit within the hobby plan size limit. The configuration size will grow with the number of flags in your project, and heavy users may require an enterprise plan to fit their configuration. If your Edge Config cannot store your project's configuration after the integration has been set up, we will reach out to you with more information. Setup Configure Integration To get started, visit the integration's page on Vercel and click "Add Integration". This will open a separate window which will load the setup form on the DevCycle dashboard. If you don't already have a DevCycle account, you will be taken through the signup process. Once you've created your account and Organization, you'll be brought back to the integration setup. Once logged in, you can select which projects in DevCycle you want to sync to Edge Config, and which Edge Config to sync them to. If you don't have an Edge Config already set up, one will be created for you with the name "devcycle" during the configuration flow. You can also create an Edge Config ahead of time by following Vercel's documentation . After you have made your selections, hit "Submit" to finish configuring the integration. Connect a Vercel Project To use the integration in your application, you must connect the desired Edge Config in Vercel to the Vercel project where you will be running DevCycle. To do so, navigate to the "Storage" tab in the Vercel Dashboard, click on the Edge Config you want to connect, and visit the "Projects" section in the sidebar. See the Vercel docs for more information Once a project has been connected, an environment variable called EDGE_CONFIG will be set in that project which can be used in the following steps to connect to your Edge Config. In order to set this variable locally for testing, make sure to pull down the latest environment variables using the Vercel CLI by executing the following in your project's directory: vercel env pull If you do not have the Vercel CLI set up for this project, follow their steps to link the CLI to your Vercel Project Setup SDK If you haven't already installed the DevCycle Node.js or Next.js SDK you can follow the installation and usage guides for those SDKs in our documentation here . You can also find helpful setup information like where to find DevCycle SDK keys in our Quickstart Tutorial . In order to use the integration in a DevCycle SDK, you must install the @devcycle/vercel-edge-config package and provide it during SDK initialization. Using that package requires the @vercel/edge-config package to be installed as well: npm install @devcycle/vercel-edge-config @vercel/edge-config or yarn add @devcycle/vercel-edge-config @vercel/edge-config Follow the SDK-specific instructions below: Node.js For more information on Node SDK usage, see the docs import { createClient } from '@vercel/edge-config' import { EdgeConfigSource } from '@devcycle/vercel-edge-config' import { initializeDevCycle } from '@devcycle/nodejs-server-sdk' // the EDGE_CONFIG environment variable contains a connection string for a particular edge config. It is set automatically // when you connect an edge config to a project in Vercel. const edgeClient = createClient ( process . env . EDGE_CONFIG ) const edgeConfigSource = new EdgeConfigSource ( edgeClient ) const devcycleClient = initializeDevCycle ( process . env . DEVCYCLE_SERVER_SDK_KEY , // pass the edgeConfigSource as the "configSource" option during SDK intialization to tell the SDK to use Edge Config // for retrieving its configuration { configSource : edgeConfigSource } ) Now the SDK will retrieve its configuration from Edge Config. That's it! Next.js For more information on Next.js SDK usage, see the docs App Router import { createClient } from '@vercel/edge-config' import { EdgeConfigSource } from '@devcycle/vercel-edge-config' import { setupDevCycle } from '@devcycle/nextjs-sdk/server' const edgeClient = createClient ( process . env . EDGE_CONFIG ) const edgeConfigSource = new EdgeConfigSource ( edgeClient ) export const { getVariableValue , getClientContext } = setupDevCycle ( { serverSDKKey : process . env . DEVCYCLE_SERVER_SDK_KEY ?? '' , clientSDKKey : process . env . NEXT_PUBLIC_DEVCYCLE_CLIENT_SDK_KEY ?? '' , userGetter : ( ) => ( { user_id : 'test_user' } ) , options : { // pass the configSource option with the instance of EdgeConfigSource configSource : edgeConfigSource } } ) Pages Router import { createClient } from '@vercel/edge-config' import { EdgeConfigSource } from '@devcycle/vercel-edge-config' import { getServerSideDevCycle } from '@devcycle/nextjs-sdk/pages' const edgeClient = createClient ( process . env . EDGE_CONFIG ) const edgeConfigSource = new EdgeConfigSource ( edgeClient ) export const getServerSideProps : GetServerSideProps = async ( context ) => { const user = { user_id : 'server-user' , } return { props : { ... ( await getServerSideDevCycle ( { serverSDKKey : process . env . DEVCYCLE_SERVER_SDK_KEY || '' , clientSDKKey : process . env . NEXT_PUBLIC_DEVCYCLE_CLIENT_SDK_KEY || '' , user , context , options : { // pass the configSource option with the instance of EdgeConfigSource configSource : edgeConfigSource } } ) ) , } , } } Edit this page Last updated on Jan 9, 2026 Prerequisites Setup Configure Integration Connect a Vercel Project Setup SDK DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:25 |
https://docs.devcycle.com/platform/security-and-guardrails/permissions/#can--2 | Roles & Permissions | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up Home Getting Started Essentials DevCycle Overview Key Features System Architecture Feature Hierarchy Feature Types Platform Feature Flags Experimentation Account Management Security and Guardrails Approval Workflows Audit Log Custom Property Schemas Feature Obfuscation Roles & Permissions SDK Visibility Variable Schemas Testing and QA Extras Examples Platform Security and Guardrails Roles & Permissions On this page Roles & Permissions At DevCycle, our permissions model is designed to protect production while supporting secure and scalable team collaboration. We offer flexible, role-based access controls that can be applied both at the Organization and Project level—allowing you to tailor access based on how your teams operate. Permissions are available for Organizations on our Business or Enterprise plans. You can visit our pricing page or contact our support team to learn more about our plans. Permission Levels Overview DevCycle supports multiple levels of permission enforcement: Flat Access (default) : All users have full access across all Projects Basic Permissions : Org-wide roles that protect production Environments (Business and Enterprise plans) Full Role-Based Access Control (RBAC) : Fine-grained permissions managed at the Project level (Enterprise plans only) info Permissions enforcement will apply to all Projects and Production-type Environments within your Organization. Basic Permissions (Organization-Wide Roles) Basic permissions apply at the Organization level and are available to all Business and Enterprise customers. The principle behind basic permissions is to protect Production Environments while keeping permissions and their management as lightweight as possible. This level is perfect for teams that want to be able to move fast but still require some governance protections to be in place. info To enable basic permissions, navigate to your Organization Settings page and enable it under the permissions dropdown. The roles available with Basic Permissions are: Members Can ✅ Configure Development and Staging Environments Configure Inactive Production Environments Cannot ❌ Enable or Disable Production Environments Targeting Configure Active Production Environments When Production is Active , Configure Variables and Variations Manage roles of other users Manage Organization or Project settings Publishers Everything Members can do, plus: Can ✅ Enable or Disable Production Environments Targeting Configure Active Production Environments When Production is Active , Configure Variables and Variations Manage Project settings Cannot ❌ Manage roles of other users Manage Organization settings or billing Owners Everything Publishers can do, plus: Can ✅ Manage roles of all users in the Organization Administer billing Assigning Roles To assign a role to a team member, simply navigate to their profile. If you are an owner, you will be able to assign a new role to the member by using the Role dropdown. After you have selected a role, click "save" and the team member's permissions will be updated. For the user to have the new permission level available to them they will need to generate a new session by logging in again. Full Role-Based Access Control (Project-Level Roles – Enterprise Only) For Organizations managing multiple teams or business units, DevCycle offers Project-level RBAC on Enterprise plans. This allows you to manage roles granularly, granting access only to the specific workspaces your team members need with the requisite roles they need in each of those workspaces. With Role-Based Access Control, you can: Scope access to individual Projects Prevent cross-project visibility and restrict access to only the Projects a user is assigned Align access with your SSO groups and SCIM-based provisioning This enables centralized identity and access management with decentralized control, especially when integrated with providers like Azure AD or Okta. info To enable and configure SSO and SCIM-based provisioning, please contact our support team. Role Matrix The table below outlines actions available to each role across Organization and Project levels. note All actions affecting Production Environments are restricted for roles below Publisher . Action Viewer Member Publisher Project Admin Org Admin Org Owner organization:read:settings ✅ ✅ ✅ ✅ ✅ ✅ organization:write:settings ✅ ✅ organization:read:members ✅ ✅ ✅ ✅ ✅ ✅ organization:write:members ✅ ✅ organization:read:billing ✅ ✅ ✅ ✅ ✅ ✅ organization:write:billing ✅ organization:read:projects ✅ ✅ ✅ project:read ✅ ✅ ✅ ✅ ✅ project:write ✅ project:write:settings ✅ ✅ project:delete ✅ feature:read:staleness ✅ ✅ ✅ feature:read ✅ ✅ ✅ ✅ ✅ feature:write ✅ ✅ ✅ ✅ feature:publish ✅ ✅ ✅ feature:delete ✅ ✅ feature:status:archive ✅ ✅ ✅ ✅ feature:status:complete ✅ ✅ ✅ feature:read:config ✅ ✅ ✅ ✅ ✅ feature:write:config ✅ ✅ ✅ ✅ audience:write ✅ ✅ ✅ ✅ audience:read ✅ ✅ ✅ ✅ ✅ audience:write:prod ✅ ✅ ✅ audience:delete ✅ ✅ variable:read ✅ ✅ ✅ ✅ ✅ variable:write ✅ ✅ ✅ ✅ variable:write:prod ✅ ✅ environment:read ✅ ✅ ✅ ✅ ✅ environment:write ✅ ✅ ✅ ✅ environment:delete ✅ ✅ variation:read ✅ ✅ ✅ ✅ ✅ variation:write ✅ ✅ ✅ ✅ variation:delete ✅ ✅ ✅ ✅ results:read ✅ ✅ ✅ ✅ ✅ user:read ✅ ✅ ✅ ✅ ✅ user:write ✅ ✅ ✅ ✅ ✅ auditlog:read ✅ ✅ ✅ ✅ ✅ customproperty:read ✅ ✅ ✅ ✅ ✅ customproperty:write ✅ ✅ ✅ ✅ customproperty:delete ✅ ✅ ✅ ✅ metric:read ✅ ✅ ✅ ✅ ✅ metric:write ✅ ✅ ✅ ✅ metric:delete ✅ ✅ ✅ ✅ metricassociation:read ✅ ✅ ✅ ✅ ✅ metricassociation:write ✅ ✅ ✅ ✅ metricassociation:delete ✅ ✅ ✅ ✅ project:read:overrides ✅ ✅ ✅ ✅ ✅ project:write:overrides ✅ ✅ ✅ ✅ ✅ webhook:read ✅ ✅ ✅ ✅ ✅ webhook:write ✅ ✅ ✅ ✅ webhook:delete ✅ ✅ ✅ project:read:tokens ✅ ✅ project:write:tokens ✅ Managing Role Mappings with SCIM and SSO For Enterprise customers using identity providers (IdPs) like Azure AD or Okta, DevCycle supports role mapping through SCIM and SSO group-based permissions . Roles can be mapped to IdP groups Users are automatically assigned the correct roles upon login Centralized IT control, local team autonomy This streamlines onboarding and offboarding, and ensures the principle of least privilege is maintained. To get started with Role-Based Access Control, contact our support team. Edit this page Last updated on Jan 9, 2026 Previous Feature Obfuscation Next SDK Visibility Permission Levels Overview Basic Permissions (Organization-Wide Roles) Members Publishers Owners Assigning Roles Full Role-Based Access Control (Project-Level Roles – Enterprise Only) Role Matrix Managing Role Mappings with SCIM and SSO DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:25 |
https://docs.devcycle.com/platform/security-and-guardrails/permissions/#cannot--1 | Roles & Permissions | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up Home Getting Started Essentials DevCycle Overview Key Features System Architecture Feature Hierarchy Feature Types Platform Feature Flags Experimentation Account Management Security and Guardrails Approval Workflows Audit Log Custom Property Schemas Feature Obfuscation Roles & Permissions SDK Visibility Variable Schemas Testing and QA Extras Examples Platform Security and Guardrails Roles & Permissions On this page Roles & Permissions At DevCycle, our permissions model is designed to protect production while supporting secure and scalable team collaboration. We offer flexible, role-based access controls that can be applied both at the Organization and Project level—allowing you to tailor access based on how your teams operate. Permissions are available for Organizations on our Business or Enterprise plans. You can visit our pricing page or contact our support team to learn more about our plans. Permission Levels Overview DevCycle supports multiple levels of permission enforcement: Flat Access (default) : All users have full access across all Projects Basic Permissions : Org-wide roles that protect production Environments (Business and Enterprise plans) Full Role-Based Access Control (RBAC) : Fine-grained permissions managed at the Project level (Enterprise plans only) info Permissions enforcement will apply to all Projects and Production-type Environments within your Organization. Basic Permissions (Organization-Wide Roles) Basic permissions apply at the Organization level and are available to all Business and Enterprise customers. The principle behind basic permissions is to protect Production Environments while keeping permissions and their management as lightweight as possible. This level is perfect for teams that want to be able to move fast but still require some governance protections to be in place. info To enable basic permissions, navigate to your Organization Settings page and enable it under the permissions dropdown. The roles available with Basic Permissions are: Members Can ✅ Configure Development and Staging Environments Configure Inactive Production Environments Cannot ❌ Enable or Disable Production Environments Targeting Configure Active Production Environments When Production is Active , Configure Variables and Variations Manage roles of other users Manage Organization or Project settings Publishers Everything Members can do, plus: Can ✅ Enable or Disable Production Environments Targeting Configure Active Production Environments When Production is Active , Configure Variables and Variations Manage Project settings Cannot ❌ Manage roles of other users Manage Organization settings or billing Owners Everything Publishers can do, plus: Can ✅ Manage roles of all users in the Organization Administer billing Assigning Roles To assign a role to a team member, simply navigate to their profile. If you are an owner, you will be able to assign a new role to the member by using the Role dropdown. After you have selected a role, click "save" and the team member's permissions will be updated. For the user to have the new permission level available to them they will need to generate a new session by logging in again. Full Role-Based Access Control (Project-Level Roles – Enterprise Only) For Organizations managing multiple teams or business units, DevCycle offers Project-level RBAC on Enterprise plans. This allows you to manage roles granularly, granting access only to the specific workspaces your team members need with the requisite roles they need in each of those workspaces. With Role-Based Access Control, you can: Scope access to individual Projects Prevent cross-project visibility and restrict access to only the Projects a user is assigned Align access with your SSO groups and SCIM-based provisioning This enables centralized identity and access management with decentralized control, especially when integrated with providers like Azure AD or Okta. info To enable and configure SSO and SCIM-based provisioning, please contact our support team. Role Matrix The table below outlines actions available to each role across Organization and Project levels. note All actions affecting Production Environments are restricted for roles below Publisher . Action Viewer Member Publisher Project Admin Org Admin Org Owner organization:read:settings ✅ ✅ ✅ ✅ ✅ ✅ organization:write:settings ✅ ✅ organization:read:members ✅ ✅ ✅ ✅ ✅ ✅ organization:write:members ✅ ✅ organization:read:billing ✅ ✅ ✅ ✅ ✅ ✅ organization:write:billing ✅ organization:read:projects ✅ ✅ ✅ project:read ✅ ✅ ✅ ✅ ✅ project:write ✅ project:write:settings ✅ ✅ project:delete ✅ feature:read:staleness ✅ ✅ ✅ feature:read ✅ ✅ ✅ ✅ ✅ feature:write ✅ ✅ ✅ ✅ feature:publish ✅ ✅ ✅ feature:delete ✅ ✅ feature:status:archive ✅ ✅ ✅ ✅ feature:status:complete ✅ ✅ ✅ feature:read:config ✅ ✅ ✅ ✅ ✅ feature:write:config ✅ ✅ ✅ ✅ audience:write ✅ ✅ ✅ ✅ audience:read ✅ ✅ ✅ ✅ ✅ audience:write:prod ✅ ✅ ✅ audience:delete ✅ ✅ variable:read ✅ ✅ ✅ ✅ ✅ variable:write ✅ ✅ ✅ ✅ variable:write:prod ✅ ✅ environment:read ✅ ✅ ✅ ✅ ✅ environment:write ✅ ✅ ✅ ✅ environment:delete ✅ ✅ variation:read ✅ ✅ ✅ ✅ ✅ variation:write ✅ ✅ ✅ ✅ variation:delete ✅ ✅ ✅ ✅ results:read ✅ ✅ ✅ ✅ ✅ user:read ✅ ✅ ✅ ✅ ✅ user:write ✅ ✅ ✅ ✅ ✅ auditlog:read ✅ ✅ ✅ ✅ ✅ customproperty:read ✅ ✅ ✅ ✅ ✅ customproperty:write ✅ ✅ ✅ ✅ customproperty:delete ✅ ✅ ✅ ✅ metric:read ✅ ✅ ✅ ✅ ✅ metric:write ✅ ✅ ✅ ✅ metric:delete ✅ ✅ ✅ ✅ metricassociation:read ✅ ✅ ✅ ✅ ✅ metricassociation:write ✅ ✅ ✅ ✅ metricassociation:delete ✅ ✅ ✅ ✅ project:read:overrides ✅ ✅ ✅ ✅ ✅ project:write:overrides ✅ ✅ ✅ ✅ ✅ webhook:read ✅ ✅ ✅ ✅ ✅ webhook:write ✅ ✅ ✅ ✅ webhook:delete ✅ ✅ ✅ project:read:tokens ✅ ✅ project:write:tokens ✅ Managing Role Mappings with SCIM and SSO For Enterprise customers using identity providers (IdPs) like Azure AD or Okta, DevCycle supports role mapping through SCIM and SSO group-based permissions . Roles can be mapped to IdP groups Users are automatically assigned the correct roles upon login Centralized IT control, local team autonomy This streamlines onboarding and offboarding, and ensures the principle of least privilege is maintained. To get started with Role-Based Access Control, contact our support team. Edit this page Last updated on Jan 9, 2026 Previous Feature Obfuscation Next SDK Visibility Permission Levels Overview Basic Permissions (Organization-Wide Roles) Members Publishers Owners Assigning Roles Full Role-Based Access Control (Project-Level Roles – Enterprise Only) Role Matrix Managing Role Mappings with SCIM and SSO DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:25 |
https://docs.devcycle.com/sdk/client-side-sdks/flutter | Flutter SDK | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up SDK Overview SDK Lifecycle SDK Features Client-side SDKS JavaScript SDK React SDK Next.js SDK Angular SDK iOS SDK Android SDK React Native Flutter SDK Installation Getting Started Usage Example App Roku SDK Server-side SDKS SDK Proxy Client-side SDKS Flutter SDK DevCycle Flutter Client SDK The Flutter Client SDK for DevCycle! This SDK uses our Client SDK APIs to perform all user segmentation and bucketing for the SDK, providing fast response times using our globally distributed edge workers all around the world. Installation Installing the SDK Getting Started Initializing the SDK Usage Using the SDK Example App Try it out for yourself The SDK is available as a package on Pub. It is also open source and can be viewed on GitHub. Edit this page Last updated on Jan 9, 2026 Previous Usage Next Installation DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:25 |
https://docs.devcycle.com/integrations/#code-analysis | Integrations | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up On this page Integrations Welcome to DevCycle Integrations! Here you will find all of the various first party tools made with the DevCycle APIs, as well as third party integrations to connect DevCycle to the tools of your needs. Contributing to DevCycle or creating a new Integration: If you would like to contribute to an existing integration or tool, all of DevCycle's tools and integrations are open source on the DevCycle Github repository. Further, if you'd like to create a new tool or integration, a great starting point is DevCycle's Management API which allows you to modify and interact with features and more within a DevCycle project, as well as the DevCycle Bucketing API which is used to serve users features and variables (and powers the DevCycle SDKs!) Observability Dynatrace Monitor and analyze your feature flags with Dynatrace observability platform. OpenTelemetry Monitor and analyze your feature flags with OpenTelemetry. Snowflake Data Sharing Access your Organization's Event data on Snowflake Google Analytics Send DevCycle Feature/Variation data from Tag Manager to Google Analytics 4 for A/B test analysis Rollbar Enhance error logging with DevCycle Feature and Variable data IDE Plugins VSCode Extension Use DevCycle directly in Visual Studio Code. Interoperability OpenFeature Use DevCycle with the OpenFeature Flagging Standard. Feature Flag Importer Import resources from other feature flag providers. Webhooks Connect apps and services to DevCycle. Vercel Edge Config Upload DevCycle configurations to Vercel Edge Config for faster retrieval Code Analysis GitHub: Flag Code Usages Display code snippets for each variable used in a project. GitHub: Flag Change Insights Display added/removed flags on each Pull Request. Bitbucket: Flag Code Usages Display code snippets for each variable used in a project. Bitbucket: Flag Change Insights Display added/removed flags on each Pull Request. GitLab: Flag Code Usages Display code snippets for each variable used in a project. GitLab: Flag Change Insights Display added/removed flags on each Merge Request. Collaboration Tools Slack Connect DevCycle to your Slack workspace to track Feature updates. DevOps Jira: Flag Management Link Jira tickets directly to DecCycle features Terraform Provider Manage projects, features and more with Terraform Edit this page Last updated on Jan 9, 2026 Observability IDE Plugins Interoperability Code Analysis Collaboration Tools DevOps DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:25 |
https://docs.devcycle.com/integrations/#collaboration-tools | Integrations | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up On this page Integrations Welcome to DevCycle Integrations! Here you will find all of the various first party tools made with the DevCycle APIs, as well as third party integrations to connect DevCycle to the tools of your needs. Contributing to DevCycle or creating a new Integration: If you would like to contribute to an existing integration or tool, all of DevCycle's tools and integrations are open source on the DevCycle Github repository. Further, if you'd like to create a new tool or integration, a great starting point is DevCycle's Management API which allows you to modify and interact with features and more within a DevCycle project, as well as the DevCycle Bucketing API which is used to serve users features and variables (and powers the DevCycle SDKs!) Observability Dynatrace Monitor and analyze your feature flags with Dynatrace observability platform. OpenTelemetry Monitor and analyze your feature flags with OpenTelemetry. Snowflake Data Sharing Access your Organization's Event data on Snowflake Google Analytics Send DevCycle Feature/Variation data from Tag Manager to Google Analytics 4 for A/B test analysis Rollbar Enhance error logging with DevCycle Feature and Variable data IDE Plugins VSCode Extension Use DevCycle directly in Visual Studio Code. Interoperability OpenFeature Use DevCycle with the OpenFeature Flagging Standard. Feature Flag Importer Import resources from other feature flag providers. Webhooks Connect apps and services to DevCycle. Vercel Edge Config Upload DevCycle configurations to Vercel Edge Config for faster retrieval Code Analysis GitHub: Flag Code Usages Display code snippets for each variable used in a project. GitHub: Flag Change Insights Display added/removed flags on each Pull Request. Bitbucket: Flag Code Usages Display code snippets for each variable used in a project. Bitbucket: Flag Change Insights Display added/removed flags on each Pull Request. GitLab: Flag Code Usages Display code snippets for each variable used in a project. GitLab: Flag Change Insights Display added/removed flags on each Merge Request. Collaboration Tools Slack Connect DevCycle to your Slack workspace to track Feature updates. DevOps Jira: Flag Management Link Jira tickets directly to DecCycle features Terraform Provider Manage projects, features and more with Terraform Edit this page Last updated on Jan 9, 2026 Observability IDE Plugins Interoperability Code Analysis Collaboration Tools DevOps DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:25 |
https://www.assemblyai.com/dashboard/signup?utm_source=devto&utm_medium=challenge&utm_campaign=streaming_challenge&utm_content=apikey | Already have an account? Log in Get your API key and up to 330 free hours of speech-to-text Experience AssemblyAI's industry-leading accuracy, low latency, and powerful Speech AI capabilities. No credit card required. With our API, you'll get access to: Speech-to-Text Build on the industry's most accurate ASR model, with only 30.4s latency on a 30 min audio file Streaming Speech-to-Text Automatically turn live audio into text with >90% accuracy and ~300ms latency Speech Understanding Extract maximum value from voice data and generate insights, summaries, and more Top companies choose AssemblyAI Already have an account? Log in Create your account Continue with Google OR Continue with email By continuing, you agree to our Terms of Service and Privacy Policy AssemblyAI | Sign Up | 2026-01-13T08:48:25 |
https://docs.x.com/status | X Developer Platform Status - X Skip to main content X home page English Search... ⌘ K Ask AI Support Developer portal Developer portal Search... Navigation Status X Developer Platform Status Home X API X Ads API XDKs Tutorials Use Cases Success Stories Status Changelog Developer Portal Forums GitHub Status X Developer Platform Status Incident History Status X Developer Platform Status Copy page Copy page All systems are operational X API v2 Normal GNIP Enterprise API Normal Developer Portal Normal Incident History ⌘ I X home page x github Terms of Service Privacy Policy Cookies Developer Terms x github | 2026-01-13T08:48:25 |
https://mailchimp.com/ | Marketing, Automation & Email Platform | Mailchimp Skip to main content Join Mailchimp with a free 14-day trial or save 15% off on 10,000+ contacts. Start today. Solutions and Services Solutions and Services See what’s new Email marketing Send personalized emails that convert Websites Create your branded web presence Social media marketing Amplify the conversation across multiple channels Templates Customize pre-designed layouts Marketing automation Deliver the right message at the right time Reporting and analytics Track sales & campaign performance Audience management Target and segment customers AI marketing tools Say hello to your AI growth assistant Content creation tools Build content that captivates and converts Lead generation platform Grow your audience with high-quality leads See all features See all our product offerings in one place For your industry E-commerce and retail Mobile and web apps Start-ups Agencies and freelancers Developers Professional Services Hire an Expert Personalized onboarding Customer success Integrations Integrations See 300+ Integrations Most Popular Most Popular Shopify WooCommerce Canva Zapier Square Wix Squarespace Stripe Salesforce LinkedIn Wordpress Facebook Your Tech Stack E-commerce Analytics Booking & Scheduling Loyalty Subscription management Customer service Forms & Surveys Developer tools Content For Developers Getting started Developer guides API docs Webhooks Resources Resources See all resources Learn with Mailchimp E-commerce Digital content Marketing automations Audience management Websites Email marketing Social media Mailchimp Presents Podcasts Series Films For Developers Marketing API Transactional API Release notes Transactional email Help Center Case Studies Events Professional Services Hire an Expert Personalized onboarding Customer success Switch to Mailchimp Pricing Search This page is now available in other languages. EN EN English ES Español FR Français BR Português DE Deutsch IT Italiano Sales: +1 (800) 315-5939 Start Free Trial Log In Start Free Trial Hi, %s Account Audience Campaigns Account Log Out Mailchimp Home Log In Main Menu Close Main Menu Main Menu Solutions and Services Back Close Main Menu Solutions and Services Email marketing Send personalized emails that convert Websites Create your branded web presence Social media marketing Amplify the conversation across multiple channels Templates Customize pre-designed layouts Marketing automation Deliver the right message at the right time Reporting and analytics Track sales & campaign performance Audience management Target and segment customers AI marketing tools Say hello to your AI growth assistant Content creation tools Build content that captivates and converts Lead generation platform Grow your audience with high-quality leads See all features See all our product offerings in one place See what’s new For your industry Back Close Main Menu For your industry E-commerce and retail Mobile and web apps Start-ups Agencies and freelancers Developers Professional Services Back Close Main Menu Professional Services Hire an Expert Personalized onboarding Customer success Integrations Back Close Main Menu Integrations Most Popular Back Close Main Menu Most Popular Shopify WooCommerce Canva Zapier Square Wix Squarespace Stripe Salesforce LinkedIn Wordpress Facebook Your Tech Stack Back Close Main Menu Your Tech Stack E-commerce Analytics Booking & Scheduling Loyalty Subscription management Customer service Forms & Surveys Developer tools Content See 300+ Integrations For Developers Back Close Main Menu For Developers Getting started Developer guides API docs Webhooks Resources Back Close Main Menu Resources Learn with Mailchimp Back Close Main Menu Learn with Mailchimp E-commerce Digital content Marketing automations Audience management Websites Email marketing Social media Mailchimp Presents Back Close Main Menu Mailchimp Presents Podcasts Series Films For Developers Back Close Main Menu For Developers Marketing API Transactional API Release notes Transactional email See all resources Help Center Case Studies Events Professional Services Back Close Main Menu Professional Services Hire an Expert Personalized onboarding Customer success Switch to Mailchimp Pricing Search This page is now available in other languages. English EN English ES Español FR Français BR Português DE Deutsch IT Italiano Contact Sales: +1 (800) 315-5939 Hi, %s Back Close Main Menu Account Audience Campaigns Account Log Out Mailchimp Home Log In Start Free Trial Log In Log In Start Free Trial Integrate your data. Inform your decisions. Impact your results. Harness the power of your data in real time and grow your revenue with email. Start Free Trial Convert with email automations Boost orders and customer lifetime value by dynamically personalizing emails based on browsing and purchase data. Explore marketing automation Create faster with generative AI Effortlessly create on-brand content with generative AI tools and choose from expertly designed templates. Explore AI tools Refine with segmentation Target customers with advanced logic like spend amounts, buying behavior, and predicted attributes. Explore audience management Optimize with analytics & reporting Analyze performance with custom reports, funnel visualizations, and industry benchmarking. Explore analytics and reporting Find out why we’re best-in-class The #1 email marketing and automation platform that recommends ways to get more opens, clicks, and sales. Up to 25x ROI seen by Mailchimp users* 24 years experience helping businesses sell more 11M+ Users of Mailchimp globally Over 3.1 billion emails with AI-generated content sent by Mailchimp customers* Get started easily with a personalized product tour An onboarding specialist is here to help you get started with confidence—it’s included with Standard and Premium plans.* Learn more about onboarding Try for free Save 15% on 10,000+ contacts Try our Standard plan for free ! Find out why customers see up to 24x ROI* using the Standard plan with a 14-day trial†. Cancel or downgrade to our Essentials or basic Free plans at any time. Find out why customers see up to 24x ROI* using the Standard plan with a 14-day trial†. Cancel or downgrade to our Essentials or basic Free plans at any time. Get 15% off our Standard plan Businesses with 10,000+ contacts can save 15% on their first 12 months.† Keep your discount if you change to Premium or Essentials . Cancel or downgrade to our basic Free plan at any time. Businesses with 10,000+ contacts can save 15% on their first 12 months.† Keep your discount if you change to Premium or Essentials . Cancel or downgrade to our basic Free plan at any time. Generative AI features Actionable insights into audience growth and conversion funnels Enhanced automations Custom-coded email templates Customizable Popup forms Personalized onboarding See all plans $ AUD R$ BRL $ CAD CHF CHF DKK kr € EUR £ GBP $ HKD ₹ INR ¥ JPY $ MXN $ NZD SEK kr $ SGD $ USD R ZAR Standard Send up to 6,000 emails each month. Need to manage more than 250,000 contacts?
Get in touch to learn about custom plans. Contacts Contacts 0-500 501-1,500 1,501-2,500 2,501-5,000 5,001-10,000 10,001-15,000 15,001-20,000 20,001-25,000 25,001-30,000 30,001-40,000 40,001-50,000 50,001-75,000 75,001-100,000 Try for free Try free for 14 days Free for 14 days Then, starts at $20 /month† per month† Save 15% on 10,000+ contacts Save 15% on 10,000+ contacts $ 20 00 /mo for 12 months per month for 12 months Then, starts at /month† per month† Try for free Try free for 14 days Free for 14 days Then, starts at $20 /month† per month† Save 15% on 10,000+ contacts Save 15% on 10,000+ contacts $ 20 00 /mo for 12 months per month for 12 months Then, starts at /month† per month† Try for free Try free for 14 days Free for 14 days Then, starts at $20 /month† per month† Save 15% on 10,000+ contacts Save 15% on 10,000+ contacts $ 20 00 /mo for 12 months per month for 12 months Then, starts at /month† per month† Try for free Try free for 14 days Free for 14 days Then, starts at $20 /month† per month† Save 15% on 10,000+ contacts Save 15% on 10,000+ contacts $ 20 00 /mo for 12 months per month for 12 months Then, starts at /month† per month† Start Free Trial Start Free Trial Buy Now Buy Now Contact limit exceeded Limit †See Free Trial Terms . Overages apply if contact or email send limit is exceeded. Learn More †See Offer Terms . Overages apply if contact or email send limit is exceeded. Learn More See all plans Bring in more data, drive more growth with our integrations Canva Create compelling visuals for your marketing. Mailchimp for Salesforce Sync your Mailchimp subscribers and Salesforce® leads across platforms. Instagram Promote and share your Instagram posts in email campaigns. Shopify Sync Shopify customers, products, and purchase data to Mailchimp. Google Analytics Unlock powerful insights with campaign, website, or landing page data. WooCommerce Power your ecommerce store with smart marketing features. QuickBooks Online Bring together your marketing tools and invoice data. Squarespace Commerce Market your ecommerce business and drive sales. Zapier Automatically pass data between web services without a single line of code. View all 300+ integrations Millions of users trust us with their email marketing. You can too. Start Free Trial *Disclaimers #1 AI-powered email marketing platform: Based on December 2023 publicly available data on the number of customers of competitors that also advertise using AI to enhance their email marketing and automation products and services. #1 email marketing and automation platform: Based on May 2025 publicly available data on competitors' number of customers. SMS Marketing: SMS is available as an add-on to paid plans in select countries. Application and agreement to terms is required before purchasing credits. Messages can only be delivered to contacts in the country selected. Australia messaging available only for contacts with +61 country code. SMS credits are added to your account after purchase and approval. Credits are issued monthly and unused credits expire and do not roll over. MMS only available for Standard and Premium plans sending to US and Canada contacts. Pricing varies. Click here for details. Intuit Assist: Intuit Assist functionality (beta) is available to certain users with Premium, Standard and Legacy plans in select countries in English only. Access to Intuit Assist is available at no additional cost at this time. Pricing, terms, conditions, special features and service options are subject to change without notice. Availability of features and functionality varies by plan type. Features may be broadly available soon but represents no obligation and should not be relied on in making a purchasing decision. For details, please view Mailchimp’s various plans and pricing. Personalized onboarding: Onboarding services differ per plan and are available for new or upgraded users with a Standard or Premium plan for the first 90 days after account creation or upgrade. Onboarding services are currently offered in English, Spanish and Portuguese for Premium plans, and in English for Standard plans. 24X ROI Standard Plan: Based on all e-commerce revenue attributable to Standard plan users’ Mailchimp campaigns from April 2023 to April 2024. Availability of features and functionality varies by plan type. For details, view plans and pricing . 25X ROI: Based on all e-commerce revenue attributable to paid plan users’ Mailchimp campaigns from April 2023 to April 2024 3.1 Billion Emails Sent: Based on InLine AI Assistant feature for December 2023 - August 2024. Standard and Premium plans only. Popup forms (beta): Very limited availability to new and existing Mailchimp users and on web browsers only. Features may be more broadly available soon, but represents no obligation and should not be relied on in making a purchasing decision. Availability of features and functionality varies by plan type. For details, view plans and pricing . †Free Trial Terms No Credit Card Free Trial: If you are on a Free Trial of the Standard or Essentials plan (each a “Paid Marketing Plan”) that did not require a credit card at sign up, you can send up to 500 emails including bulk sends and automation sends. Adding your credit card during your Free Trial unlocks your plan’s full email sending limits based on your contact tier. Once your Free Trial ends, your credit card will be charged monthly at the current rate for your chosen Paid Marketing Plan (based on your contact tier and email sends) unless you delete your Mailchimp account, change plans, or change to a Free Marketing Plan. Adding SMS Marketing to your marketing plan during your Free Trial requires a credit card and also unlocks your plan’s full email sending limits based on your contact tier for the duration of your Free Trial. SMS Marketing fees are not included in the Free Trial and you will be charged for the SMS credits you purchase once your SMS application is approved during your Free Trial. See full offer terms . Terms, conditions, pricing, special features, and service and support options subject to change without notice. Related Links: How to Buy a Domain Name: Domain Registration Guide What Is the Difference Between an RFQ vs. RFP? ChatGPT: What to Know About This AI Content Writing Tool Products Why Mailchimp? Product Updates Email Marketing Websites Transactional Email How We Compare GDPR Compliance Security Status Mobile App Resources Marketing Library Free Marketing Tools Marketing Glossary Integrations Directory Community Agencies & Freelancers Developers Events Company Our Story Newsroom Give Where You Live Careers Accessibility Help Contact Us Hire an Expert Help Center Talk to Sales Films, podcasts, and original series that celebrate the entrepreneurial spirit. Check it out This page is now available in other languages. English Español Français Português Deutsch Italiano ©2001-2025 All Rights Reserved. Mailchimp® is a registered trademark of The Rocket Science Group. Apple and the Apple logo are trademarks of Apple Inc. Mac App Store is a service mark of Apple Inc. Google Play and the Google Play logo are trademarks of Google Inc. Privacy | Terms | Legal | Cookie Preferences | 2026-01-13T08:48:25 |
https://docs.devcycle.com/platform/extras/webhooks | Webhooks | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up Home Getting Started Essentials DevCycle Overview Key Features System Architecture Feature Hierarchy Feature Types Platform Feature Flags Experimentation Account Management Security and Guardrails Testing and QA Extras Custom Domains Feature Opt-In Self-Hosted Feature Flags with DevCycle Webhooks Examples Platform Extras Webhooks On this page Webhooks This topic explains how to create and use Webhooks in DevCycle. Webhooks allow you to build your own integrations that subscribe to Feature changes in DevCycle. Use Webhooks to update external ticket trackers, notify teammates of new features, targeting changes, and more. Outbound Webhooks Creating a Webhook To create a Webhook: Navigate to the Integrations page. Navigate to the "Webhooks" section and click + New Webhook . The "Create a Webhook" modal appears. Give the Webhook a human-readable name. (Optional) Give the Webhook a description. Enter a Payload URL. Click Create Webhook . From there, you will be taken to the Webhook details page. Select if you'd like events sent for all Features in your project or a single Feature. Select which events will be sent through the Webhook. Click Save . Example Payload Below is the type definition for the payload that gets sent to the Webhook url: /** * The 'newContents' and 'previousContents' type is a subset of the resource * that was changed */ export type AuditLogChange = { type : string newContents : Record < string , unknown > | null previousContents : Record < string , unknown > | null _environments ? : string [ ] metadata ? : Record < string , unknown > } type User = { name ? : string email : string } type WebhookPayload = { /** * An array of types that were triggered, the 'changes' property * should have all these events in this array */ events : string [ ] /** * The key of the Feature */ key ? : string /** * The key of the project */ projectId : string /** * The version of the payload so we can have different versions * in the future */ version : string /** * The changes that were made */ changes : AuditLogChange [ ] /** * The date this Webhook triggered the URL on */ date : Date /** * The user that triggered the change */ user : User } For example, a user edits a Feature’s key and adds a new variable, the data posted to the user’s Webhook URL would be: { "events" : [ "modifiedFeature" , "addedVariable" ] , "key" : "feature-key" , "date" : "2024-01-16T18:30:42.796Z" , "user" : { "name" : "Jason" , "email" : " [email protected] " } , "version" : "1" "changes" : [ { "type" : "modifiedFeature" , "newContents" : { "key" : "new-feature-key" } , "previousContents" : { "key" : "feature-key" } } , { "type" : "addedVariable" , "newContents" : { ... // new variable object } , "previousContents" : null } , ] } Testing a Webhook To test a Webhook: Navigate to the Integrations page. Navigate to the "Webhooks" section. Click the expand arrows next to the Add integration button. Navigate to the Test section of the Webhook details page. Click Test Connection to verify the Webhook Url is accessible. The API response will be displayed below. Deleting a Webhook To delete a Webhook: Navigate to the Integrations page. Navigate to the "Webhooks" section. Click on the Webhook that you wish to delete. Navigate to the Settings section of the Webhook details page. Click Delete Webhook . A confirmation modal will appear. Click Delete . Inbound Webhooks (Coming Soon) This feature will allow the user to create Webhook urls for certain actions, like turning on/off a Feature in production. If you would like this feature, contact [email protected] ! Edit this page Last updated on Jan 9, 2026 Previous Self-Hosted Feature Flags with DevCycle Next Examples Outbound Webhooks Creating a Webhook Example Payload Testing a Webhook Deleting a Webhook Inbound Webhooks (Coming Soon) DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:25 |
https://www.linkedin.com/posts/suprsend_%F0%9D%97%98%F0%9D%98%85%F0%9D%97%BD%F0%9D%97%BC%F0%9D%97%BF%F0%9D%98%81-%F0%9D%97%A1%F0%9D%97%BC%F0%9D%98%81%F0%9D%97%B6%F0%9D%97%B3%F0%9D%97%B6%F0%9D%97%B0%F0%9D%97%AE%F0%9D%98%81%F0%9D%97%B6%F0%9D%97%BC%F0%9D%97%BB%F0%9D%98%80-%F0%9D%97%97%F0%9D%97%AE%F0%9D%98%81%F0%9D%97%AE-activity-7407802699695652865-ovI6 | Control Your AWS Notifications Data with Custom Dashboards | SuprSend posted on the topic | LinkedIn Agree & Join LinkedIn By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Skip to main content LinkedIn Top Content People Learning Jobs Games Sign in Join now for free Control Your AWS Notifications Data with Custom Dashboards This title was summarized by AI from the post below. SuprSend 19,129 followers 3w Edited Report this post 𝗘𝘅𝗽𝗼𝗿𝘁 𝗡𝗼𝘁𝗶𝗳𝗶𝗰𝗮𝘁𝗶𝗼𝗻𝘀 𝗗𝗮𝘁𝗮 𝘁𝗼 𝗔𝗺𝗮𝘇𝗼𝗻 𝗦𝟯 🚀 Now you can fully own and control your notifications data within your S3 bucket — create custom dashboards, debug delivery issues, or maintain audit trails for compliance. 𝗪𝗵𝗮𝘁'𝘀 𝗶𝗻𝗰𝗹𝘂𝗱𝗲𝗱: • Syncs every 5 minutes in encrypted Parquet files • Messages, Workflow Executions, and Requests • Automatic backfills and hourly partitions • Works natively with Athena, Snowflake, BigQuery, Redshift Confidently build dashboards, surface notification logs to customers, or track entire customer lifecycle end-to-end. Docs in comments 👇 9 1 Comment Like Comment Share Copy LinkedIn Facebook X SuprSend 3w Report this comment Amazon S3: https://docs.suprsend.com/docs/amazon_s3_v2 Like Reply 1 Reaction To view or add a comment, sign in More Relevant Posts Johnathon Smith 1w Report this post One design choice I was intentional about in this project was how data landed in Snowflake. Instead of transforming data on the way in, I focused on getting raw JSON ingested reliably first. Data lands in S3, Snowpipe auto-ingests it into a raw table, and transformations can happen downstream. Separating ingestion from transformation made the pipeline simpler and easier to reason about. Snowflake only worries about loading data, not validating or reshaping it. This approach reinforced something for me. Clean boundaries between stages make systems easier to maintain over time. #dataengineering #snowflake #dataplatforms 1 Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Bodh Analytics & Insights 12 followers 4d Edited Report this post ❓ Ever opened a JSON payload in Snowflake and thought: Where do I even start? Why did my row count suddenly explode? Do I really need FLATTEN… and why OUTER = TRUE? If this feels familiar, you’re definitely not alone. At Bodh Analytics & Insights , we recently built and demoed a structured framework to understand and analyze JSON data in Snowflake — starting with simple JSON, progressing to nested structures, and finally handling real-world complex event payloads. 🚀 Why Snowflake stands out One of Snowflake’s biggest strengths is its native support for semi-structured data: Read JSON directly using VARIANT Navigate objects with dot notation Handle arrays using FLATTEN Preserve data safely with OUTER => TRUE This makes Snowflake a powerful platform for event data, activity logs, APIs, and SaaS integrations. 🧠 What we learned building this framework This didn’t happen overnight. It took time, multiple client requirements, real production payloads, and several iterations to design a clear, step-by-step approach that: Avoids data loss Prevents unexpected row explosion Makes JSON approachable—even for beginners Today, we have a repeatable way to move from “What is this payload?” to analytics-ready tables with confidence. 💡 What’s next? We’re happy to apply this framework to other payloads — across different schemas, industries, and use cases. 👇 How has your experience been with JSON in Snowflake ? Smooth? Painful? Somewhere in between? Would love to hear insights from Kiran Earalli , SANTOSH UBALE , Satish Reddy , and Jainam Soni — please share your experiences 👇 …more “In this walkthrough, I’ll show how we handle JSON in Snowflake—from simple structures to complex, real-world payloads—using FLATTEN and OUTER = TRUE Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Elena Goryainova 3w Report this post Many Snowflake customers realize the value that semantic layer can bring. Yet only some were able to design and implement it without creating the silos - bring the unified business meaning across the entire fleet of tools and applications. That's why I collaborated with SqlDBM 's head of product Serge Gershkovich to produce this article to explain the path from chaos to consensus and how to rebuild the trust by implementing the semantic layer correctly. Check it out on Snowflake Builders Blog: https://lnkd.in/eM9RdXw4 From Chaos to Consensus medium.com 36 6 Comments Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Samapika C 3w Report this post Unique Snowflake DV Flow: 1. Snowpipe Staging - Auto-ingest raw data into transient tables with continuous loads. 2. Raw Vault MERGE - Build HUBs/LINKs/SATs using dynamic MERGE via Streams for hash diffs. 3. Task-Chained Vault 2.0 - Orchestrate Business Vault with serverless Tasks; enable real-time PITs/Bridges. 4. Cortex-Accelerated Views - Virtualize marts with AI-powered semantic views for instant BI. #DataVault2 #Snowflake #DataEng 7 Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in CodeBefore 12 followers 1w Report this post The question wasn’t: “Can we build a data warehouse?” The real question was: “Can we build a data warehouse that combines most SEO data sources in a way that’s actually usable and scalable?” Before thinking about dashboards, features, or users, we treated this as a prototype problem. So we built a POC. Not a product. Not an MVP. A small but real system designed to answer one thing: can this work in reality? We ran it on a self-hosted Kubernetes cluster, used GitOps-style deployments with FluxCD, and connected a stack that reflects real-world constraints: • Airbyte for data ingestion • Airflow for orchestration in Kubernetes • ClickHouse for analytical workloads • dbt-core for transformations In less than a week, the pipeline was running end to end. What did this give us? Not validation of demand. Not product-market fit. Clarity. We understood where complexity lived, what would break at scale, and which assumptions were safe — or not. That’s the role of a prototype. It doesn’t prove that users will love it. It proves that reality won’t surprise you later. If you’re facing a hard technical question and want to validate it with real code before committing, talk to us at > codebefore. Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Johnathon Smith 2w Report this post One of the parts I spent the most time thinking about in my project was error handling. Before any data ever hits the stream, the Lambda function checks that the incoming JSON is readable and that required fields are present. If something is off, that data gets written to a dedicated S3 bucket for bad records and stops there. Only validated data is allowed into Kinesis and downstream systems. Designing it this way made the rest of the pipeline simpler. Snowflake only ever sees data that meets basic expectations, and bad data is still retained for inspection instead of disappearing. It was a good reminder that handling failure paths intentionally is just as important as handling the happy path. #dataengineering #dataquality #cloudarchitecture Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Revolt BI 2,281 followers 4w Report this post If your dashboards are slowing down, costs keep rising, or your team is constantly firefighting… it’s not the tools. It’s the architecture. Most data platforms hide issues like: • Spaghetti SQL • Failing DAGs • Inefficient compute usage • Patchwork models Our Architecture Review gives you a forensic look into your Snowflake, dbt, SQL, and pipelines — and shows exactly where bottlenecks, waste, and failure points come from. You get a clear, prioritized roadmap to stabilize and scale your platform. Revolt BI supports 300+ companies across tech, e-commerce, retail, travel, and finance — helping them build reliable, modern data stacks. 🚀 Find the bottlenecks. Fix the architecture. Review your stack with our experts. 👉 https://lnkd.in/dhgtPd6q 6 Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Gaurang Prajapati 2w Report this post 𝗦𝘁𝗼𝗽 𝘀𝗰𝗵𝗲𝗱𝘂𝗹𝗶𝗻𝗴 𝗽𝗶𝗽𝗲𝗹𝗶𝗻𝗲𝘀, 𝗱𝗲𝗳𝗶𝗻𝗲 𝗳𝗿𝗲𝘀𝗵𝗻𝗲𝘀𝘀. 𝗗𝘆𝗻𝗮𝗺𝗶𝗰 𝗧𝗮𝗯𝗹𝗲𝘀 𝗱𝗼 𝘁𝗵𝗲 𝗿𝗲𝘀𝘁. Dynamic Table is a declarative object where you define what data you want, and Snowflake automatically manages how and when it is refreshed, based on a defined freshness requirement. 𝗪𝗵𝘆 𝗗𝘆𝗻𝗮𝗺𝗶𝗰 𝗧𝗮𝗯𝗹𝗲𝘀 𝗺𝗮𝘁𝘁𝗲𝗿: -Eliminate manual incremental logic -Remove the need to manage Streams and Tasks explicitly -Automatically handle refresh orchestration and dependencies -Provide consistent and predictable data freshness 𝗞𝗲𝘆 𝗳𝗲𝗮𝘁𝘂𝗿𝗲𝘀: -TARGET_LAG defines acceptable data latency -Automatic dependency resolution across Dynamic Tables -Incremental refresh by default, optimized by Snowflake -Built-in failure handling and recovery -Fully integrated with Snowflake compute and storage architecture 𝗖𝗼𝗺𝗺𝗼𝗻 𝘂𝘀𝗲 𝗰𝗮𝘀𝗲𝘀: -Replacing complex Stream + Task pipelines -Building multi-layered data models (staging → business → reporting) -Ensuring SLA-driven freshness for analytics and BI workloads -Simplifying pipeline maintenance in large data platforms 𝗪𝗵𝗲𝗻 𝘁𝗼 𝘂𝘀𝗲 𝗗𝘆𝗻𝗮𝗺𝗶𝗰 𝗧𝗮𝗯𝗹𝗲𝘀: -When data freshness matters more than strict scheduling -When pipelines have multiple downstream dependencies -When you want Snowflake to manage orchestration and optimization 𝘐𝘯 𝘗𝘢𝘳𝘵 02, 𝘐’𝘭𝘭 𝘴𝘩𝘢𝘳𝘦 𝘢 𝘳𝘦𝘢𝘭-𝘵𝘪𝘮𝘦 𝘦𝘹𝘢𝘮𝘱𝘭𝘦 𝘥𝘦𝘮𝘰𝘯𝘴𝘵𝘳𝘢𝘵𝘪𝘯𝘨 𝘵𝘩𝘪𝘴 𝘪𝘯 𝘱𝘳𝘢𝘤𝘵𝘪𝘤𝘦. 302 8 Comments Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Gangxin Li 2w Report this post Towards the end of the year, I wanted to share a recent Snowflake warehouse optimisation experience that I found particularly valuable from a data engineering perspective. The goal was to improve performance and scalability under growing workloads, while significantly reducing cost. High-level outcomes: ✅ ~64% cost reduction in the US region and ~74% in the UK ✅~$26.7k immediate monthly savings achieved right after the optimisation, with ongoing impact ✅End-to-end runtime reduced from ~25 minutes to ~12 minutes ✅Long-running spikes (50+ minutes) eliminated, now consistently under 20 minutes ✅4× improvement in overall warehouse efficiency Rather than going deep into implementation details, I wanted to share a few technical principles that made the biggest difference. Key Snowflake optimisation learnings: 0️⃣ Start from workload characteristics, not warehouse settings Understanding latency expectations, concurrency, ingestion patterns, and data distribution upfront avoids blind tuning later. 1️⃣ Use multi-cluster warehouses intentionally Concurrency, SLAs, and memory pressure matter more than cluster count. Over-scaling can be as harmful as under-scaling. 2️⃣ Let warehouse size scale when memory or I/O becomes the bottleneck Auto-scaling warehouse size helped stabilise performance when smaller sizes consistently spilled to disk. 3️⃣ Isolate workloads by business criticality Combining multi-cluster and auto-scaling, and assigning different models to different warehouses, reduced contention and improved predictability. 4️⃣ SQL and execution plans still matter Reviewing query plans, reducing unnecessary joins, and applying Snowflake-specific optimisations (e.g. directed joins) had outsized impact. 5️⃣ Treat dbt models as production assets Long time windows, unnecessary null checks, and schedules misaligned with business needs quietly drive both cost and latency. 6️⃣ Monitor query behaviour continuously Repeated inefficient queries from users or applications accumulate cost quickly. Alerts and usage analysis are essential. 7️⃣ Alert on abnormal warehouse usage Background jobs or agents can keep warehouses running unintentionally — catching this early prevents silent cost leaks. 8️⃣ Do more for less https://lnkd.in/eYNXx2ba Snowflake optimisation is rarely about a single feature. It’s a system-level exercise that connects business requirements, data modelling, and warehouse design. Announcing New Snowpipe Pricing and 9 Other Ways to Save on Data Engineering Costs snowflake.com 9 Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in WhereScape Data Automation 12,566 followers 3w Report this post Curious what a properly engineered Data Vault looks like in practice? This on-demand walkthrough shows how a full DV 2.0 implementation comes together using metadata and automation, not custom SQL and fragile glue code. In about 30 minutes, you will see hubs, links, satellites, PITs, bridges, ELT workflows, lineage, and orchestration generated end to end from design metadata. See how just 11 source tables are expanded into 60+ governed objects using consistent patterns, automated change handling, and deployment-ready output across Snowflake, Databricks, Microsoft Fabric, SQL Server, and more. ▶️ Watch the recording and see what scalable Data Vault delivery actually looks like: https://ow.ly/rf6e50XK1fJ #DataVault #DV2 #DataEngineering #DataArchitecture #MetadataDriven #Automation #ELT #WhereScape #Snowflake #Databricks #MicrosoftFabric 1 Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in 19,129 followers View Profile Connect Explore content categories Career Productivity Finance Soft Skills & Emotional Intelligence Project Management Education Technology Leadership Ecommerce User Experience Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language Sign in to view more content Create your free account or sign in to continue your search Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . | 2026-01-13T08:48:25 |
https://www.pixpa.com/blog/best-portfolio-websites | 18 Best Portfolio Websites of 2025 Start Free Product The easy, all-in-one website builder for creatives. Build Your Website Create stunning portfolio websites Start an Online Store Sell products, services & digital files Client Galleries Share, proof, sell & deliver images Website Templates Customisable, responsive templates for your website. Sell Images Sell images as prints & downloads Start a Blog Publish a blog to share your stories Photo Gallery Apps Personalised gallery apps for clients Marketing Tools Grow your audience and business SEO Tools Drive more traffic to your site Why Choose Pixpa? Discover the all-in-one website builder to power your online success! Explore Now Made for Creatives Models & Actors Photographers Fashion Designers & Stylists Artists Architects & Interior Designers Illustrators Musicians & Performers Graphic Designers Writers & Authors UI UX Designers Agencies & Freelancers Templates Examples Pricing Resources Why Choose Pixpa? Discover the all-in-one website builder to power your online success! Students & Educators Get upto 55% off on all plans with Pixpa Edu discounts. Agencies & Freelancers Build websites for clients on Pixpa & get exclusive perks. The Pixpa Blog Resources and inspiration for creatives. Help Centre Guides & tutorials on building your Pixpa site. Product Updates Stay updated with everything new on Pixpa Customer Stories Love and feedback from Pixpa’s users Apps & Integrations Power your site with 100+ apps & integrations. Become an Affiliate Partner Promote Pixpa and earn awesome rewards. Hire a Pixpa Expert Get a Pixpa Design Expert to build your website for you, saving you time and effort. Learn More EN English Español Français Deutsch Português Nederlands Italiano Polski Русский Login Start Free Product Build Your Website Create stunning portfolio websites Start an Online Store Sell products, services & digital files Client Galleries Share, proof, sell & deliver images Website Templates Customisable, responsive templates for your website. Sell Images Sell images as prints & downloads Start a Blog Publish a blog to share your stories Photo Gallery Apps Personalised gallery apps for clients Marketing Tools Grow your audience and business SEO Tools Drive more traffic to your site Why Choose Pixpa? Discover the all-in-one website builder to power your online success! Explore Now Made for Creatives Photographers Artists Illustrators Graphic Designers UI UX Designers Models & Actors Fashion Designers & Stylists Architects & Interior Designers Musicians & Performers Writers & Authors Agencies & Freelancers Templates Examples Pricing Resources Why Choose Pixpa? Discover the all-in-one website builder to power your online success! Students & Educators Get 40% off on all plans with Pixpa Edu discounts. Agencies & Freelancers Build websites for clients on Pixpa & get exclusive perks. The Pixpa Blog Resources and inspiration for creatives. Help Centre Guides & tutorials on building your Pixpa site. Product Updates Stay updated with everything new on Pixpa Customer Stories Love and feedback from Pixpa’s users Apps & Integrations Power your site with 100+ apps & integrations. Become an Affiliate Partner Promote Pixpa and earn awesome rewards. Hire a Pixpa Expert Get a Pixpa Design Expert to build your website for you, saving you time and effort. Explore EN English Español Français Deutsch Português Nederlands Italiano Polski Русский Login Start Free All Posts , Photography , portfolio , website-examples , 18 Best Portfolio Websites of 2025 Gurpreet Singh on Feb 12, 2024 17 min read Let us take a look at our picks for the best portfolio websites this year These 24 best portfolio websites are full of stellar web design lessons that can help you level up your portfolio website and make it stand out! There has never been a better time than now to create an online portfolio website. With easy-to-use and affordable portfolio website builders, designing, building and managing your professional portfolio website is now fairly simple and uncomplicated. But what makes an online portfolio website stand out from the crowd? Is it just the visual elements or is there more to making a website unique, distinctive and impactful? What do the best portfolio websites in 2024 look like? Let us try to figure it out! At its most fundamental, a website is a collection of web pages that serve a singular purpose. From business websites to online portfolios, e-commerce websites to personal websites and from blog websites to resume websites, all websites are made for a purpose. The good ones, however, manage to go beyond just being useful or purposeful. In this article we take a look at what makes the greatest websites stand out in 2024. We will also take a moment to appreciate and learn from the top 24 best websites built on Pixpa and understand what makes these websites impactful and unique. Ready to create your professional website with Pixpa? Start Free Trial Here are the top 18 best portfolio website examples for your inspiration 1. Di'Nasia Berry - Model Di’Nasia Berry is a dancer and a model based in Atlanta, Georgia. She perfectly uses her Pixpa-powered model portfolio website to showcase her interest in fashion modeling. She fiddles with colored and black & white photos of herself on the homepage. These are large enough in the grid layout to make for easy navigation and browse the best photos of a fashion artist. A simple menu section at the top gives easy access to her entire portfolio. It is a must-visit for all aspiring models looking to make a splash in the industry. 2. Marco H - Designer Marco is on a mission to make the internet a better place for everyone. He is a jack-of-all-trades guy specializing as a content curator, system engineer, UI/UX designer, web designer, network engineer, solution architect, and community helper. He uses a grid layout to introduce himself in bold letters with a photo of himself. With a few scrolls and not having to go to different menu sections, you can glimpse his expertise and the projects he has worked on. An excellent example of how to showcase yourself when you are an expert in multiple areas. 3. Sebron Snyder - Professional Photographer Sebron is a professional photographer based in Dallas, Texas. The photography portfolio website has a lovely clean template with a menu on the left and a grid layout on the right for the gallery. The menu offers easy navigation with different styles of work and the list of clients on display. The gallery is incredibly eye-catching, with a gallery of high-quality photos being projected. Photographers can get ample inspiration from this Pixpa-powered photography portfolio website. What makes Pixpa ideal for portfolio sites? Pixpa excels as a user-friendly platform designed for creatives. With its sleek templates and easy client interaction tools, it’s perfect for showcasing work. Plus, its e-commerce features let photographers and designers sell their creations directly. Simple, effective, and multifunctional. Ready to create your portfolio website? Get Started 4. Fernando Saiz - Fashion Photographer Fernando Saiz is a fashion and portrait photographer. The homepage of his portfolio leverages Pixpa’s customizable gallery layout to showcase a collection of photos in a grid format. The collection boasts of an unconventional approach to photography, and a series of strange yet striking photos are on display that catch a visitor's attention. Anyone interested in making a career in the fashion industry through photography skills, this is a great portfolio to look at. 5. Elena Klimkin - Lifestyle Photographer Elena Klimkin is a lifestyle photographer and content creator based in Zurich, Switzerland. The homepage keeps it simple with relevant menus on top followed by quick about info and work samples. The portfolio includes the exact category of photography that the visual artist is interested in, such as lifestyle photography, travel photography, brand promotions, etc. The portfolio is especially noticeable for its close-up shots. Do check this out if lifestyle photography is your thing. 6. Samantha Plasencia - sportswear designer Samantha Plasencia is a sportswear designer. The portfolio website’s homepage is clean, with important browsing stations in the menu section and a sizeable sporty-looking image covering the entire screen. The gallery includes a collection of Samantha’s best work in the grid format. The portfolio also makes use of an online store provided by Pixpa. It is an excellent example of a portfolio you should look at to build one for yourself and start selling in minutes. 7. Rou Marcellus - Fashion Photographer Rou Marcellus is a fashion photographer and student based in Atlanta, Georgia in the United States. Rou’s website finds its place on our list because of the vivid yet understated colour blocking effect he achieves on his landing page by using his portfolio gallery. The landing page makes an immediate impact and the strong composition and visuals that characterize Rou’s photography shine through in his website design as well. 8. Andrew Hendrix - Photography Andrew Hendrix’s website is on our list of best websites for 2024 because of its adaptable and responsive design that works just as well on desktop as on mobile. The landing page is divided into four sections that can be easily scrolled through to reach the different parts of Andrew’s website. He also includes a more traditional menu in the header of his website for more information and further navigation. We love to see responsive, mobile-friendly sites and website owners who are mindful of this! 9. Mihailo Vucenic - Graphic Designer Mihailo Vucenic’s design portfolio website uses a dark background and vivid neon tones as highlights. This is highly effective in creating a strong impact on the viewer right as they load the landing page. Scrolling down, you can read Mihailo’s story and what led him down the artistic career path that he has chosen. The brilliant combination of an impactful colour palette, minimalism, and compelling content copy takes Mihailo Vucenic’s portfolio to the next level. 10. JOIO - Life Coach SJ Treharne at JOIO Life Coaching helps people find meaning, purpose and renewed confidence in their lives. Do check out her stunning personal business website. JOIO’s website is a good example of why the best websites tend to use grid patterns and layouts . Grids might seem old fashioned and restricting but they can be used to provide structure to your website and provide a clean, sleek and professional look. 11. Tze Soh - Sustainable & Innovative Residential Architecture Tze Soh is an Australian architect and what we love about his business website is that it gets straight to the point. The architecture website is designed with a very clear vision which helps it look clean, organized, curated and professional. The landing page gives you all the information you need about the architecture firm, its values, and the kinds of projects that it specializes in. 12. Emma Da Silva - Documentary Photographer Emma Da Silva is a documentary photographer based in Paris. Black backgrounds are a particularly effective way of making photographs pop and this is very evident in the landing page of Emma’s website. The landing page uses a photo carousel on a black background which serves to catch the viewer’s eye while also showcasing her work. 13. Cindy Sung - Fashion, Portrait, Lifestyle Photography Cindy Sung’s website is testament to the fact that monotone can work wonders when it comes to web design. Black and white does not have to be boring or mundane. Cindy has taken a simple black and white photograph as the background image for her landing page and it works wonderfully. It draws attention to the center of the page and a carousel of photos that showcases her work. As you scroll down, you get a subtle but effective transition to colors. Cindy’s website is one of our favourites in this list of best 2024 websites. 14. Antoine Rabeau Daudelin - Photographer, Artist Like several other best websites on this list, Antoine Rabeau Daudelin’s website uses striking imagery to showcase his work as full-width banners. Easy navigability, thoughtful content copy and minimalist design aesthetics are some of the other reasons why we believe Antoine’s online portfolio deserves a spot among this list. 15. Escapist Motif- Functional Art Escapist Motif is a Singapore based online store that seeks to bring together functionality and creativity through their art. Their store sells ‘ functional art ’ consisting mainly of custom, hand-binded books and notebooks. The seamless integration of utility and design that Escapist Motif tries to embody in their art is also visible in their website. The website is designed in a minimalist fashion and even though it is primarily an e-commerce site, it tries to showcase the artistry and craftsmanship behind the products as well. This functional artistry is what makes Escapist Motif one of the best websites in the e-commerce category in our opinion. 16. Tricia Reinking - Photographer, Food Stylist Tricia Reinking is a food stylist and photographer based in Florida, United States. What we like about Tricia’s website is that it is very functional but does not sacrifice any design aesthetics. It is a portfolio website and therefore it centers Tricia’s food photography work. The landing page consists of a sleek and modern-looking photo gallery that encourages visitors to explore and gives a good introduction to her work immediately. Like all other portfolio's on this list, it is also a user-friendly and easily navigable website. 17. Chris Collado - Photographer Chris Collado’s website is on our list of best photography websites of 2024. Chris’s landing page uses a column of images from his portfolio that also doubles up as a menu leading to different categories within his portfolio. This is an ingenious way of making the landing page multipurpose. Well organized grid layouts, intuitive navigation etc are some of the other factors that make Chris’s online portfolio stand out and earn his site a place in the best portfolio of 2024. Preview 18. Jeremy Bianco - Portrait Artist If we have learned anything by now it's that monochromatic color palettes are a winning feature for a lot of the best portfolios in 2024. Fine art portrait painter Jeremy Bianco’s artist portfolio website is no different. The monochromatic color theme sets the mood for the website’s landing and also matches his black and white portrait paintings that are displayed on the landing page itself. Apart from being a portfolio, Jeremy’s website also includes a store where he sells prints of his work. Checkout More Portfolio Examples from Pixpa. How to build a Portfolio for Freelancers with Examples How to Make a Digital Marketing Portfolio with Examples Stunning Interior Designer Portfolios 12+ Awesome Illustrator Portfolio Website Examples Best Band and Musician Website Examples Tattoo Apprenticeship Portfolio Website Examples What makes a portfolio website stand out in 2024? Minimalism Attention to detail An impactful landing page Best user experience practices Feature-rich and aesthetic website design Minimalism Minimalism is a key feature of modern web design and for good reason. A less is more approach allows you to concentrate on the most important visual and functional elements of your website. Minimalist websites do not have to be bland or boring. In fact, it takes a great deal of creativity, imagination and good design sensibility to make minimalism work. When done right, minimalism can give your website a clarity of vision and purpose that is the key to creating a meaningful user experience. Apart from visual aesthetics, minimalist websites are also easier to navigate and faster loading. Therefore, avoiding fuss and clutter can not only do wonders for the aesthetics of your website but also add to its functionality. Here are 10 expert tips on aesthetic pictures , using the right techniques and examples. Our article on the 30 best minimalist websites takes a deeper look at why minimalism is the secret behind most best portfolios! Attention to detail It's the little things that matter. Attention to detail is an important component of all design, especially web design. Small touches can play a big role in enhancing user experience. Even something as little as choosing the right font size and consistency in terms of layout and design can play a big role in improving the UX of your website and improving bounce rates. Conversely, a lack of consistency, neglecting to include seemingly inconsequential but important pages like an About Us page or a Contact Us page can have a negative impact on your website’s user experience and cause your bounce rates to go up. A detail-oriented design philosophy can go a long way in helping you build the best website that can both retain user attention and help your website stand out from the crowd. Take a look at our article on the principles of design to understand how the little things come together to create focused, deliberate and impactful visual experiences. If you are looking for inspiration and ideas to start building a website from scratch, here is a step-by-step guide on how to design a website and make it perfect! User Experience Practices What all the websites have in common is a stunning landing page. The landing page or the homepage of your website is the first page that any site visitor will see when they first land on your site. This is your chance to make an impact and make sure that you create lasting impressions. First impressions can often be the make or break factor when it comes to websites. Keep in mind that a portion of people who land on your website will simply close the page and move on. This is called bouncing and if you want to reduce the bounce rates on your website then you need to make sure your landing page can grab a person’s attention and hook them from the very start. A short, attention-grabbing landing page copy, your personal branding and an impactful hero image are excellent website design ideas to make sure your landing page creates the effect you are looking for. An impactful landing page User experience or UX is the way in which users interact with and therefore experience a website or platform. Think about going into a restaurant for dinner. While the main purpose of your visit is the food, your experience of going to the restaurant isn’t determined by the taste of the food alone. The ambience of the restaurant, the decor, the location, the cleanliness and hygiene affect your experience of the restaurant as does the service and the behaviour of the staff and other patrons. Similarly, when a user lands on your website, their experience will be governed by the overall design of your website and whether it has been designed in a way to maximize ease of use, efficiency, navigability, visual aesthetics and more. Good user experience practices also involve trying to make your website inclusive and accessible. Offering translations and multiple language versions of your website, using easy to read fonts and color palettes etc. are good user experience practices that all the best portfolio websites should use in 2024. We have an article on the best UX designer portfolios if you want to take a look at how experts design user experience for websites and other digital platforms and the factors they take into consideration while doing so! Feature rich + aesthetic website design If you want to create the best website in 2024 then you need to marry together function with visuals. It is great to have a functional website and it is wonderful to have a visually stunning website but bringing these two things together is what makes a website truly stand out. When you are looking to create a website that is both feature-rich and attractive, it is important to understand that your website will be only as good as the tools you use to build it. If you need extensive features, functionality and utility alongside stunning designs and attractive templates, then you need to look for a tool that gives you exactly that. Pixpa is an all-in-one, DIY website builder platform that can help you create stunning, professional and feature-rich websites effortlessly and without touching a single line of code. Pixpa comes with a wide range of pixel-perfect, mobile-friendly and responsive templates that can be fully customized to your liking using the intuitive visual editor and a drag and drop page builder. You can also use custom CSS and HTML code to personalize your website and add extra features using a plethora of third party integrations. Pixpa offers a complete solution to website building including full-featured e-commerce tools and online store builder, multiple gallery options, portfolio building tools, a comprehensive client proofing platform, blogging tools, SEO and marketing tools and more. Pixpa can help you build a website that not only stands out but also allows you to share, sell and promote your work, and manage your entire web presence, all from one single platform. And if you are still not fully convinced, here are 25 top reasons why you should try Pixpa as your website builder of choice in 2024! Conclusion These were our top picks for the popular websites of 2024! Clean minimalist design, a focus on good user experience and text-light websites are clearly some of the top web design trends that we are seeing here and we definitely can’t complain. If this has got you wondering about what the design trends in 2024 are going to look like then worry not because we have something just for you. Our article on the top upcoming web design trends is going to be right up your alley. You might also want to check out this detailed article on the best graphic design softwares to help you create your own stunning graphics for your website. The best portfolio websites are created using the best website creation tools. So, if you were looking for the perfect website builder for your needs, look no further. You can sign up for Pixpa’s full-featured, 15 day free trial now. No credit card is required to sign up and no hidden charges. And if you are not satisfied with your experience, Pixpa also offers a 30-day money-back guarantee! So, don’t wait any longer. Start building your dream website this year Start Free Trial Frequently Asked Questions How to Make Your Own Website? It is incredibly easy to create your own website using Pixpa, an all-in-one, DIY website builder. Once you have signed up for a 15-day free trial, you can start building your very own professional website effortlessly and without touching a single line of code. It all starts with picking a template of your choice from Pixpa’s extensive range of mobile-friendly, professional, and responsive templates. From there you can customize your templates to match your needs and requirements and add any features and plugins you like. Pixpa makes website building easy, affordable, and accessible. How much does it cost to build an entire website? You can start building your very own website for free by signing up for a full-featured 15-day free trial with Pixpa. After you have test driven the platform and its features, you can opt to continue building and eventually publish your website for as little as $3/month by subscribing to Pixpa’s Light plan. You can also opt for Expert plan at $10/month or the Business plan at $16/month and get access to exclusive services including a free one-time website set-up service where you can get a Pixpa expert to set up your website for you, just the way you want! You can also check out this article for more detailed information on how much a website costs to build! What website builder do photographers use? Pixpa is favored by photographers all over the world because of its exclusive, photographer-friendly templates and features like e-commerce galleries and a full-featured client-proofing platform. Pixpa provides the perfect all-in-one platform for photographers to share, sell and deliver their work online and manage their photography business all in one place. How do I sell my photos on my website? Pixpa websites allow the perfect solution for users looking to sell their photographs through their website. You can sell your photos either through Pixpa’s e-commerce galleries which merge e-commerce features into your online portfolio itself or through a traditional online store. Pixpa also allows you to sell your photos as prints or digital downloads. You can choose to auto-fulfil print orders through WHCC or Fotomoto or self-fulfil through a custom lab of your choice. What is the best DIY website builder? Pixpa’s easy-to-use platform is the perfect DIY website builder which is suitable for beginners and advanced users alike. You can create a feature-rich professional website in minutes and without any advanced technical knowledge or coding skills. Pixpa’s intuitive visual editor and drag-and-drop page builder make website building a breeze. If you are a more technically skilled user looking for slightly more advanced tools, Pixpa also allows you to use custom CSS and HTML code for advanced customization. Try Pixpa - the easy, all-in-one portfolio website builder loved by photographers & creators. --> Get Started - It's Free --> Explore More Articles See all articles Explore More Articles See all articles How to Create a Tattoo Apprenticeship Portfolio (With Examples) Shankar Gurumoorthy 5 min read Best Band and Musician Portfolio Websites: How to Build One in 2025 Shankar Gurumoorthy 5 min read How to Make a Portfolio Website: A Complete Guide Shankar Gurumoorthy 10 MIN READ We’re Here for You — 24/7 Support Help Centre Access detailed guides, tutorials, and help articles in 20+ languages to solve any issue quickly. Go to Help Center Live Support Our expert team is available 24/7 via live chat and email. Get a fast response, any time. Login & Get Support Hire a Pixpa Expert Need help to set up your Pixpa website? Hire a Pixpa Pro for custom site setup. Hire a Pixpa Expert All-in-one website builder for creatives. Get Started Build Your Website Create stunning portfolio websites Start an Online Store Sell products, services & digital files Sell Images Sell images as prints & downloads Marketing Tools Grow your audience and business Client Galleries Share, proof, sell & deliver images Photo Gallery Apps Personalised gallery apps for clients Start a Blog Publish a blog to share your stories SEO Tools Drive more traffic to your site Explore More Testimonials Great all-in-one service for creatives Epic customer support! The best in the market Amazing value for money Great platform for portfolios Exceedingly happy with Pixpa Customer service is spectacular! My website is gorgeous Clean, simple, cost effective platform I can easily sell 1000s of images Live help is always available within minutes Best website builder for photographers Dedicated at creatives My website looks high-end Awesome customer service My website went live in a day Pixpa checks all the boxes I'm switching everything over to Pixpa Pixpa is "Wordpress be gone" for me 100% recommended Best platform for designers Clean and professional templates Start building your website. Get Started Free 15-day free trial. No credit card required. Beautiful Templates Made for Creatives Awesome Support Really Easy to Use Affordable Pricing Rated as top website builder by creatives for 11+ years. Product Websites Online Stores E-commerce Galleries Client Galleries Marketing Tools Hire a Pixpa Expert Templates Pricing Customer Stories Product Updates Integrations Help Center Status TOUR Creatives Photographers Artists Graphic Designers UI UX Designers Models & Actors Fashion Designers & Stylists Architects & Interior Designers Musicians & Performers Church Website Weddings Illustrators Writers & Authors Showcase Featured Photography Design Art Fashion Weddings Online Stores Architecture Client Galleries About About Pixpa Blog Contact Become an Affiliate Students & Educators Partner Deals Terms of Use Privacy Policy Pixpa is an easy, all-in-one portfolio website builder for photographers & creators to create portfolio websites with a built-in online store, blog, and client galleries. Do more with less time and money. Get our emails on inspiration & tips to grow your creative business. What's new on Pixpa Close We use cookies to deliver a better website experience. By continuing to use this website, you agree to our cookie policy. Got it 5 Create your portfolio website & store Create your portfolio website Start Free | 2026-01-13T08:48:25 |
https://docs.devcycle.com/platform/security-and-guardrails/permissions/#publishers | Roles & Permissions | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up Home Getting Started Essentials DevCycle Overview Key Features System Architecture Feature Hierarchy Feature Types Platform Feature Flags Experimentation Account Management Security and Guardrails Approval Workflows Audit Log Custom Property Schemas Feature Obfuscation Roles & Permissions SDK Visibility Variable Schemas Testing and QA Extras Examples Platform Security and Guardrails Roles & Permissions On this page Roles & Permissions At DevCycle, our permissions model is designed to protect production while supporting secure and scalable team collaboration. We offer flexible, role-based access controls that can be applied both at the Organization and Project level—allowing you to tailor access based on how your teams operate. Permissions are available for Organizations on our Business or Enterprise plans. You can visit our pricing page or contact our support team to learn more about our plans. Permission Levels Overview DevCycle supports multiple levels of permission enforcement: Flat Access (default) : All users have full access across all Projects Basic Permissions : Org-wide roles that protect production Environments (Business and Enterprise plans) Full Role-Based Access Control (RBAC) : Fine-grained permissions managed at the Project level (Enterprise plans only) info Permissions enforcement will apply to all Projects and Production-type Environments within your Organization. Basic Permissions (Organization-Wide Roles) Basic permissions apply at the Organization level and are available to all Business and Enterprise customers. The principle behind basic permissions is to protect Production Environments while keeping permissions and their management as lightweight as possible. This level is perfect for teams that want to be able to move fast but still require some governance protections to be in place. info To enable basic permissions, navigate to your Organization Settings page and enable it under the permissions dropdown. The roles available with Basic Permissions are: Members Can ✅ Configure Development and Staging Environments Configure Inactive Production Environments Cannot ❌ Enable or Disable Production Environments Targeting Configure Active Production Environments When Production is Active , Configure Variables and Variations Manage roles of other users Manage Organization or Project settings Publishers Everything Members can do, plus: Can ✅ Enable or Disable Production Environments Targeting Configure Active Production Environments When Production is Active , Configure Variables and Variations Manage Project settings Cannot ❌ Manage roles of other users Manage Organization settings or billing Owners Everything Publishers can do, plus: Can ✅ Manage roles of all users in the Organization Administer billing Assigning Roles To assign a role to a team member, simply navigate to their profile. If you are an owner, you will be able to assign a new role to the member by using the Role dropdown. After you have selected a role, click "save" and the team member's permissions will be updated. For the user to have the new permission level available to them they will need to generate a new session by logging in again. Full Role-Based Access Control (Project-Level Roles – Enterprise Only) For Organizations managing multiple teams or business units, DevCycle offers Project-level RBAC on Enterprise plans. This allows you to manage roles granularly, granting access only to the specific workspaces your team members need with the requisite roles they need in each of those workspaces. With Role-Based Access Control, you can: Scope access to individual Projects Prevent cross-project visibility and restrict access to only the Projects a user is assigned Align access with your SSO groups and SCIM-based provisioning This enables centralized identity and access management with decentralized control, especially when integrated with providers like Azure AD or Okta. info To enable and configure SSO and SCIM-based provisioning, please contact our support team. Role Matrix The table below outlines actions available to each role across Organization and Project levels. note All actions affecting Production Environments are restricted for roles below Publisher . Action Viewer Member Publisher Project Admin Org Admin Org Owner organization:read:settings ✅ ✅ ✅ ✅ ✅ ✅ organization:write:settings ✅ ✅ organization:read:members ✅ ✅ ✅ ✅ ✅ ✅ organization:write:members ✅ ✅ organization:read:billing ✅ ✅ ✅ ✅ ✅ ✅ organization:write:billing ✅ organization:read:projects ✅ ✅ ✅ project:read ✅ ✅ ✅ ✅ ✅ project:write ✅ project:write:settings ✅ ✅ project:delete ✅ feature:read:staleness ✅ ✅ ✅ feature:read ✅ ✅ ✅ ✅ ✅ feature:write ✅ ✅ ✅ ✅ feature:publish ✅ ✅ ✅ feature:delete ✅ ✅ feature:status:archive ✅ ✅ ✅ ✅ feature:status:complete ✅ ✅ ✅ feature:read:config ✅ ✅ ✅ ✅ ✅ feature:write:config ✅ ✅ ✅ ✅ audience:write ✅ ✅ ✅ ✅ audience:read ✅ ✅ ✅ ✅ ✅ audience:write:prod ✅ ✅ ✅ audience:delete ✅ ✅ variable:read ✅ ✅ ✅ ✅ ✅ variable:write ✅ ✅ ✅ ✅ variable:write:prod ✅ ✅ environment:read ✅ ✅ ✅ ✅ ✅ environment:write ✅ ✅ ✅ ✅ environment:delete ✅ ✅ variation:read ✅ ✅ ✅ ✅ ✅ variation:write ✅ ✅ ✅ ✅ variation:delete ✅ ✅ ✅ ✅ results:read ✅ ✅ ✅ ✅ ✅ user:read ✅ ✅ ✅ ✅ ✅ user:write ✅ ✅ ✅ ✅ ✅ auditlog:read ✅ ✅ ✅ ✅ ✅ customproperty:read ✅ ✅ ✅ ✅ ✅ customproperty:write ✅ ✅ ✅ ✅ customproperty:delete ✅ ✅ ✅ ✅ metric:read ✅ ✅ ✅ ✅ ✅ metric:write ✅ ✅ ✅ ✅ metric:delete ✅ ✅ ✅ ✅ metricassociation:read ✅ ✅ ✅ ✅ ✅ metricassociation:write ✅ ✅ ✅ ✅ metricassociation:delete ✅ ✅ ✅ ✅ project:read:overrides ✅ ✅ ✅ ✅ ✅ project:write:overrides ✅ ✅ ✅ ✅ ✅ webhook:read ✅ ✅ ✅ ✅ ✅ webhook:write ✅ ✅ ✅ ✅ webhook:delete ✅ ✅ ✅ project:read:tokens ✅ ✅ project:write:tokens ✅ Managing Role Mappings with SCIM and SSO For Enterprise customers using identity providers (IdPs) like Azure AD or Okta, DevCycle supports role mapping through SCIM and SSO group-based permissions . Roles can be mapped to IdP groups Users are automatically assigned the correct roles upon login Centralized IT control, local team autonomy This streamlines onboarding and offboarding, and ensures the principle of least privilege is maintained. To get started with Role-Based Access Control, contact our support team. Edit this page Last updated on Jan 9, 2026 Previous Feature Obfuscation Next SDK Visibility Permission Levels Overview Basic Permissions (Organization-Wide Roles) Members Publishers Owners Assigning Roles Full Role-Based Access Control (Project-Level Roles – Enterprise Only) Role Matrix Managing Role Mappings with SCIM and SSO DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:25 |
https://docs.suprsend.com/docs/slack-template#edit-template | Slack Template - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection GETTING STARTED What is SuprSend? Quick Start Guide Best Practices Plan Your Integration Go-live checklist CORE CONCEPTS Templates Design Template Channel Editors Email Template In-App Inbox Template SMS Template Whatsapp Template Android Push Template iOS Push Template Web Push Template Slack Template Microsoft teams Template Testing the Template Handlebars Helpers Internationalization Users Events Workflow Notification Categories Preferences Tenants Lists Broadcast Objects Translations DLT Guidelines Whatsapp Template Guidelines WORKFLOW BUILDER Design Workflow Node List Workflow Settings Trigger Workflow Validate Trigger Payload Tenant Workflows Notification Inbox Overview Multi Tabs React Javascript (Angular, Vuejs etc) React Native Flutter (Headless) PREFERENCE CENTRE Embedded Preference Centre Javascript Angular React VENDOR INTEGRATION GUIDE Overview Email Integrations SMS Integrations Android Push Whatsapp Integrations iOS Push Chat Integrations Vendor Fallback Tenant Vendor INTEGRATIONS Webhook Connectors MONITORING & DEBUGGING Logs Audit Logs Error Guides MANAGE YOUR ACCOUNT Authentication Methods Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Channel Editors Slack Template Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Channel Editors Slack Template OpenAI Open in ChatGPT How to design Slack templates using text editor or JSONNET editor for rich block kit templates. OpenAI Open in ChatGPT Edit Template SuprSend provides two ways to design Slack templates: Text Editor : For simple text-based messages with variable interpolation JSONNET Editor : For rich, interactive templates using Slack’s Block Kit with buttons, images, and complex layouts Text Editor The text editor is ideal for simple text messages with variable content. You can add variables in Handlebars syntax as {{...}} . If the output has special html text, enclose variable in triple curly braces as {{{url}}} to avoid HTML escaping. Sample Template Mock Data Copy Ask AI New Signup request in ABC company UserName: {{user_name}} Email: {{user_email}} Organization: {{org.name}} Domain: {{org.domain}} JSONNET Editor The JSONNET editor enables rich template design using Slack Block Kit Builder . This allows you to create interactive templates with buttons, images, checkboxes, and styled text. It is essentially JSON template where variables can be added in JSONNET syntax as data.variable_name or data["$variable_name"] . Template Examples 1. Simple Text Template JSONNET Template Mock Data Copy Ask AI [ { "type" : "section" , "text" : { "type" : "mrkdwn" , "text" : "New Signup on ABC company" } }, { "type" : "section" , "text" : { "type" : "mrkdwn" , "text" : ">_UserName_: *%(user_name)s* \n >_Email_: *%(email)s* \n >_Organization_: *%(org_name)s* \n >_Domain_: *%(domain)s*" % { user_name : data.user_name , email : data.user_email , org_name : data.org.name , domain : data.org.domain } } }, { "type" : "divider" } ] 2. With Buttons: Approval Request Template Mock Data Copy Ask AI [ { "type" : "section" , "text" : { "type" : "mrkdwn" , "text" : "Share access requested for *<%(document_link)s|%(document_name)s>*" % { document_link : data.document_link , document_name : data.document_name } } }, { "type" : "section" , "fields" : [ { "type" : "mrkdwn" , "text" : "*Requested by:* \n " + data.requester_name }, { "type" : "mrkdwn" , "text" : "*When:* \n " + data.submitted_at }, { "type" : "mrkdwn" , "text" : "*Reason:* \n " + data.access_reason } ] }, { "type" : "actions" , "elements" : [ { "type" : "button" , "text" : { "type" : "plain_text" , "emoji" : true , "text" : "Approve" }, "style" : "primary" , "value" : "approve_access" }, { "type" : "button" , "text" : { "type" : "plain_text" , "emoji" : true , "text" : "Deny" }, "style" : "danger" , "value" : "deny_access" } ] } ] 3. With Image: Anomaly Alert Template Mock Data Copy Ask AI [ { "type" : "section" , "text" : { "type" : "mrkdwn" , "text" : ":warning: *High Error Rate Detected* \n Our system has experienced a spike in errors over the last *30 minutes*." } }, { "type" : "section" , "text" : { "type" : "mrkdwn" , "text" : "The error rate has significantly increased, impacting reliability. \n Please investigate immediately to avoid service degradation." } }, { "type" : "image" , "title" : { "type" : "plain_text" , "text" : "Request vs Failure Trend (Last 6 Hours)" , "emoji" : true }, "image_url" : data.image_url , "alt_text" : "Graph showing high error rate spike" }, { "type" : "section" , "fields" : [ { "type" : "mrkdwn" , "text" : "*Impacted Services:* \n " + data.impacted_services }, { "type" : "mrkdwn" , "text" : "*Time Range:* \n " + data.time_range }, { "type" : "mrkdwn" , "text" : "*Error Rate:* \n " + data.error_rate } ] }, { "type" : "divider" }, { "type" : "context" , "elements" : [ { "type" : "mrkdwn" , "text" : "🔍 View logs: <%(log_url)s|Open in Monitoring Tool> \n 📊 See metrics dashboard: <%(dashboard_url)s|Error Trends>" % { log_url : data.log_url , dashboard_url : data.dashboard_url } } ] } ] 4. With Array List: Pending Task Digest (Batched Alert) Template Mock Data Copy Ask AI [ { "type" : "section" , "text" : { "type" : "mrkdwn" , "text" : "Hi " + data [ "$recipient" ] .name + " :wave:" } }, { "type" : "section" , "text" : { "type" : "mrkdwn" , "text" : "You have " +data [ "$batched_events_count" ] + " *pending tasks* for today:" } }, { "type" : "rich_text" , "elements" : [ { "type" : "rich_text_list" , "style" : "bullet" , "indent" : 0 , "elements" : [ { "type" : "rich_text_section" , "elements" : [ { "type" : "text" , "text" : task.title + " (" + task.status + ")" } ] } for task in data [ "$batched_events" ] ] } ] }, { "type" : "actions" , "elements" : [ { "type" : "button" , "text" : { "type" : "plain_text" , "text" : "View Pending tasks" , "emoji" : true }, "url" : "https://app.company.com/tasks" , "value" : "task_url" } ] } ] Adding dynamic content Here’s how you can different types of variables in both handlebars and JSONNET syntax. Variable Type Handlebars Syntax JSONNET Syntax Parent Level variables {{user_name}} data.user_name Nested Object {{org.name}} data.org.name Print Array element at Index {{task_list.[0].task_name}} data.task_list[0].task_name Recipient {{$recipient.name}} data["$recipient"].name Actor {{$actor.name}} data["$actor"].name Tenant {{$tenant.brand_name}} data["$tenant"].brand_name Print each item in the Array Handlebars JSONNET Copy Ask AI {{#each task_list}} {{task_name}}: {{task_description}} {{/each}} Conditional Logic Handlebars JSONNET Copy Ask AI {{#if is_new_org}} New Organization {{else}} Existing Organization {{/if}} Batched Template Handlebars JSONNET Copy Ask AI Total events: {{$batched_events_count}} {{#each $batched_events}} {{item}} {{/each}} Preview Template Add mock JSON data using the Mock data button for all variables used in the template Click Load Preview to see the rendered template For JSONNET templates, click View in Slack Block Kit to see the actual Slack UI preview You must add mock data for all variables in your template. Missing mock data will cause rendering errors and prevent the preview from loading. Publish Template Once your template is ready, click Publish Draft and provide a version name to publish it. The published template becomes the live version and will be used whenever the associated workflow is triggered. Test Template Use this option to send a test message in Slack and preview how it will appear in user’s device. Click the Test button, then enter the user’s distinct_id and select the Slack channel where the test message should be sent. Template testing only uses the published Live version, so make sure to publish your changes before testing. Promote to Production You can clone template across workspaces by using Clone -> Outside Template option. Clone -> Within template can be used to clone within different languages and versions of the same template. Best Practice : Always design templates in your staging workspace first, then promote them to production. This ensures thorough testing of the changes without impacting end users. Was this page helpful? Yes No Suggest edits Raise issue Previous Microsoft teams Template How to design simple MS Teams template using markdown editor or use JSONNET editor to replicate Microsoft's adaptive card design. Next ⌘ I x github linkedin youtube Powered by On this page Edit Template Text Editor JSONNET Editor Template Examples Adding dynamic content Preview Template Publish Template Test Template Promote to Production | 2026-01-13T08:48:25 |
https://docs.devcycle.com/integrations/#__docusaurus_skipToContent_fallback | Integrations | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up On this page Integrations Welcome to DevCycle Integrations! Here you will find all of the various first party tools made with the DevCycle APIs, as well as third party integrations to connect DevCycle to the tools of your needs. Contributing to DevCycle or creating a new Integration: If you would like to contribute to an existing integration or tool, all of DevCycle's tools and integrations are open source on the DevCycle Github repository. Further, if you'd like to create a new tool or integration, a great starting point is DevCycle's Management API which allows you to modify and interact with features and more within a DevCycle project, as well as the DevCycle Bucketing API which is used to serve users features and variables (and powers the DevCycle SDKs!) Observability Dynatrace Monitor and analyze your feature flags with Dynatrace observability platform. OpenTelemetry Monitor and analyze your feature flags with OpenTelemetry. Snowflake Data Sharing Access your Organization's Event data on Snowflake Google Analytics Send DevCycle Feature/Variation data from Tag Manager to Google Analytics 4 for A/B test analysis Rollbar Enhance error logging with DevCycle Feature and Variable data IDE Plugins VSCode Extension Use DevCycle directly in Visual Studio Code. Interoperability OpenFeature Use DevCycle with the OpenFeature Flagging Standard. Feature Flag Importer Import resources from other feature flag providers. Webhooks Connect apps and services to DevCycle. Vercel Edge Config Upload DevCycle configurations to Vercel Edge Config for faster retrieval Code Analysis GitHub: Flag Code Usages Display code snippets for each variable used in a project. GitHub: Flag Change Insights Display added/removed flags on each Pull Request. Bitbucket: Flag Code Usages Display code snippets for each variable used in a project. Bitbucket: Flag Change Insights Display added/removed flags on each Pull Request. GitLab: Flag Code Usages Display code snippets for each variable used in a project. GitLab: Flag Change Insights Display added/removed flags on each Merge Request. Collaboration Tools Slack Connect DevCycle to your Slack workspace to track Feature updates. DevOps Jira: Flag Management Link Jira tickets directly to DecCycle features Terraform Provider Manage projects, features and more with Terraform Edit this page Last updated on Jan 9, 2026 Observability IDE Plugins Interoperability Code Analysis Collaboration Tools DevOps DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:25 |
https://leanpub.com/agileplaybookfortechnicalcommunicators | An Agile Playbook for Technical… [Leanpub PDF/iPad/Kindle] Leanpub Header Leanpub Navigation Skip to main content Go to Leanpub.com Leanpub Store Readers Authors Services Filter All Books Bundles Courses Tracks Filter All Books Bundles Courses Tracks An Agile Playbook for Technical Communicators A Guide for Technical Communicators Working with Agile Teams Luke Pivac Luke Pivac This book is for Technical Communicators and Agile beginners. It explains Agile, its benefits, concepts, workflows, and team collaboration for success. It covers how Agile documentation differs from Waterfall and details the role and value of an Agile Technical Communicator in a team. Luke Pivac This book is for Technical Communicators and Agile beginners. It explains Agile, its benefits, concepts, workflows, and team collaboration for success. It covers how Agile documentation differs from Waterfall and details the role and value of an Agile Technical Communicator in a team. Minimum price $10.99 Suggested price $11.45 You pay $11.45 Author earns $9.16 You pay $ Add to Cart Add to Wishlist ...Or Buy With Credits! Get A Reader Membership You can get credits with a paid monthly or annual Reader Membership , or you can buy them here . PDF EPUB 90 Readers 93 Pages 18,230 Words Table of Contents Read Sample Online About About Author Contents About About the Book With the ever-growing demand for highly skilled professionals in cross-functional teams, navigating Agile workflows can be challenging—especially for Technical Communicators. This book is your ultimate guide to mastering Agile, transforming your everyday work life, and unlocking new opportunities. Discover how to work more effectively with your team and align your technical communication deliverables with your team’s sprint goals. Along the way, you'll uncover how technical communication in Agile can open doors to a wide range of opportunities. Packed with Agile best practices and my own first-hand insights, this book offers a wealth of knowledge and practical tips. Core Concepts In An Agile Playbook for Technical Communicators, you will learn: What Agile is and the incredible benefits of using it, along with the occasional pain points. The basic concepts of Agile and its key features. The dynamics of a typical Agile workflow. How cross-functional teams collaborate in Agile environments. The unique characteristics of product and user documentation in Agile compared to traditional methods. The vital role of an Agile Technical Communicator. Invaluable tips on adding maximum value as an “Agile” Technical Communicator. For Everyone Even if you're not a Technical Communicator or Documentation Specialist, this book covers essential Agile concepts that will be beneficial for anyone new to Agile and working with Agile Teams Share this book Categories Teamwork Scrum Technical Communication Agile Lean Product Management Scrum Leadership Leadership Digital Transformation Feedback Email the Author Author About the Author Luke Pivac Luke has over a decade of experience with diverse companies, from high-tech firms to major banks. A thought leader in Agile, with publications on Bookboon and the Institute of Project Management, he helps professionals master Agile practices. Based in Auckland, New Zealand, Luke combines theory and practice to share Agile insights while working on projects, writing, and enjoying family life. Episode 244 An Interview with Luke Pivac Contents Table of Contents Introduction Getting Familiar with Agile Terms The Difference between Agile and Scrum Agile Concepts The Problem with Waterfall About the Agile Manifesto Agile Values Agile Principles Benefits of the Agile Approach Pitfalls of the Agile Framework The Agile Mindset The Core Values of the Agile Mindset Benefits of an Agile Mindset Developing Your Agile Mindset Skills The Agile Mindset and the Team What the Agile Mindset Means for the Agile Technical Communicator Agile Frameworks Describing Kanban Differences Between Kanban and Scrum Describing Scrum Scrum Roles Scrum Events Agile Documentation Difference Between Product and User Documentation Minimizing Documentation Value Focused Lean Documentation Criteria User Documentation Questions to Ask CRUFT Formula Just In Time Documentation Documenting With Your Team Documentation Review Cycle Challenges for Agile Technical Communicators Key Takeaways from Agile Documentation Documentation User Stories Sub-task Documentation to a User Story Documentation to Have its own User Story Use User Stories to Drive User Advocacy Splitting User Stories User Story Communication Tips when Working with Stakeholders Tracking Documentation User Stories on a Task Board Building Better Agile Relationships Building Relationships Working with Key Agile Roles Working with the Product Owner Working with the Scrum Master Working with the Development Team Being a Great Collaborator Professional Integrity Focus on Making your Job Easier Find Your Role in the Scrum Team Getting Past the Uncertainty Collaborating With Your Team Questions and Answers Daily Challenges Does Agile work? Quality of the Scrum Master Documenting Before the Sprint Agile and BAU — How Does That Work? Communities of Practice Waterfall Inside a Sprint Agile Solutions for Slow Document Review Feedback Documents Overlapping Within Sprints Next Steps Summary Future of Agile The Leanpub 60 Day 100% Happiness Guarantee Within 60 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks . Now, this is technically risky for us, since you'll have the book or course files either way. But we're so confident in our products and services, and in our authors and readers, that we're happy to offer a full money back guarantee for everything we sell. You can only find out how good something is by trying it, and because of our 100% money back guarantee there's literally no risk to do so! So, there's no reason not to click the Add to Cart button, is there? See full terms... Earn $8 on a $10 Purchase, and $16 on a $20 Purchase We pay 80% royalties on purchases of $7.99 or more , and 80% royalties minus a 50 cent flat fee on purchases between $0.99 and $7.98 . You earn $8 on a $10 sale, and $16 on a $20 sale . So, if we sell 5000 non-refunded copies of your book for $20 , you'll earn $80,000 . (Yes, some authors have already earned much more than that on Leanpub.) In fact, authors have earned over $14 million writing, publishing and selling on Leanpub. Learn more about writing on Leanpub Free Updates. DRM Free. If you buy a Leanpub book, you get free updates for as long as the author updates the book! Many authors use Leanpub to publish their books in-progress, while they are writing them. All readers get free updates, regardless of when they bought the book or how much they paid (including free). Most Leanpub books are available in PDF (for computers) and EPUB (for phones, tablets and Kindle). The formats that a book includes are shown at the top right corner of this page. Finally, Leanpub books don't have any DRM copy-protection nonsense, so you can easily read them on any supported device. Learn more about Leanpub's ebook formats and where to read them Write and Publish on Leanpub You can use Leanpub to easily write, publish and sell in-progress and completed ebooks and online courses! Leanpub is a powerful platform for serious authors, combining a simple, elegant writing and publishing workflow with a store focused on selling in-progress ebooks. Leanpub is a magical typewriter for authors: just write in plain text, and to publish your ebook, just click a button. (Or, if you are producing your ebook your own way, you can even upload your own PDF and/or EPUB files and then publish with one click!) It really is that easy. Learn more about writing on Leanpub Footer Publish Early, Publish Often Links Store Featured Books Bundles Courses Tracks Podcast Redeem a Token Services Author Quickstart AccessibilityPro CourseAI GlobalAuthor IndexAI Launch Quickstart Marketing Packages Publish on Amazon TranslateAI Organizations Learn More Authors Author Memberships Create Book Create Bundle Create Course Create Track Author Support Author FAQ Author Help Center Leanpub Authors Forum The Leanpub Manual The LFM Manual The Markua Manual API Docs More Partner Program Causes Accessibility Readers Reader Memberships Buy Credits Reader FAQ Help Center Essays AI Services (2024) Imagine a world... (2022) The Lean Publishing Definition (2013) The Lean Publishing Manifesto (2010) Legal Terms of Service Copyright Policy Privacy Policy Refund Policy Copyright and reCAPTCHA Leanpub is copyright © 2010- 2026 Ruboss Technology Corp . All rights reserved. This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply . | 2026-01-13T08:48:25 |
https://docs.devcycle.com/platform/security-and-guardrails/feature-obfuscation/ | Feature Obfuscation | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up Home Getting Started Essentials DevCycle Overview Key Features System Architecture Feature Hierarchy Feature Types Platform Feature Flags Experimentation Account Management Security and Guardrails Approval Workflows Audit Log Custom Property Schemas Feature Obfuscation Roles & Permissions SDK Visibility Variable Schemas Testing and QA Extras Examples Platform Security and Guardrails Feature Obfuscation On this page Feature Obfuscation Feature flags are often used to hide upcoming features before release. Normally, not showing the feature on a UI is enough to conceal it from users. However, in some cases it may be important to ensure that no trace of the feature can be found in the code that is shipped to users. This is particularly important on the web, where end-users can easily see all the source code for the page. Even when the code is obfuscated, any strings containing text from the new feature will still be present in the bundle. From that, intrepid users can often infer the nature of a feature they can't access, which may lead to sensitive or strategic information being leaked. To prevent this, DevCycle supports a feature allowing you to obfuscate all the Variable keys used in your code in Web platforms (React, Next.js, Javascript etc.) to keep their names private. Next.js users can also take advantage of our SDK's Conditional Deferred Rendering feature, which will strip out any source code for features the user isn't eligible for, reducing bundle size while also keeping the feature's details private. To use this feature, follow the setup guide below: Requirements This feature is only available for web platforms. It is not available for mobile or server-side SDKs. The following SDKs support obfuscation: Javascript React Next.js The unobfuscated data will still be available via the mobile and server SDK tokens. If you have a need for obfuscation on mobile, let us know in the community discord. Using the feature requires use of the DevCycle CLI . Follow the setup guide in the CLI documentation to install it and initialize in your repository. Setup In order to use obfuscation, the first step is to pass the enableObfuscation setting in your DevCycle SDK initialization options. This process will vary by SDK, but here is an example for React: import { withDevCycleProvider } from '@devcycle/react-client-sdk' function App ( ) { return < TheRestofYourApp /> } export default withDevCycleProvider ( { sdkKey : '<DEVCYCLE_CLIENT_SDK_KEY>' , // add this setting options : { enableObfuscation : true } } ) ( App , ) With obfuscation enabled, you can use the DevCycle CLI to generate a set of constants which correspond to your project's Variable keys. To do so, run the following command: dvc generate types --obfuscate If using React or Next.js, add the --react flag: dvc generate types --obfuscate --react The result will be a generated file containing type definitions and constants for all your project's Variables, with the keys obfuscated. The obfuscation process is done automatically using a key stored in your project's data, which is only known to the DevCycle Management API and the DevCycle CLI. An example of the generated file output you might expect is shown below.: // devcycleTypes.ts /* key: my-first-variable created by: Sally Smith created on: 2024-03-01 */ export const MY_FIRST_VARIABLE = 'dvc_obfs_3499747d616cfb0ac00bda26273e3577d5508f1ecaf2f1f07a2546' as ObfuscatedKey < 'my-first-variable' > /* key: my-second-variable created by: Joe Shmo created on: 2024-03-01 */ export const MY_SECOND_VARIABLE = 'dvc_obfs_359f6c73757fe30a9950ce39333c2329915a900893b3fbf164' as ObfuscatedKey < 'my-second-variable' > info The generated file also includes Typescript definitions of each Variable, which allows you to make your DevCycle usage type-safe by enforcing the correct datatype for each Variable. When using an enum schema , the types will also enforce that one of the allowed values is used. For more information, see the documentation for Typescript with the Javascript SDK The names of the constants will be automatically determined based on each Variable's key. If two Variable keys resolve to the same constant name, the CLI will append a number to the end of the constant name to avoid conflicts. The original Variable key will be preserved in the comment above the constant, so you can identify one constant from another. Now, in each place where a DevCycle Variable is evaluated, you can use the generated constants in place of direct strings. The constants have been automatically assigned to the obfuscated keys, so there will be no plain strings containing your Variable keys in code. For example: Before: import { useVariableValue } from '@devcycle/react-client-sdk' function MyComponent ( ) { const myFirstVariable = useVariableValue ( 'my-first-variable' , false ) const mySecondVariable = useVariableValue ( 'my-second-variable' , false ) return < div > { myFirstVariable } { mySecondVariable } </ div > } After: import { MY_FIRST_VARIABLE , MY_SECOND_VARIABLE , useVariableValue } from './devcycle' function MyComponent ( ) { const myFirstVariable = useVariableValue ( MY_FIRST_VARIABLE , false ) const mySecondVariable = useVariableValue ( MY_SECOND_VARIABLE , false ) return < div > { myFirstVariable } { mySecondVariable } </ div > } As long as your production build process is set up to uglify your production code, any trace of the original DevCycle Variable names will disappear. That's it! Requiring Obfuscation As an extra measure of safety, you can require obfuscation in your DevCycle project settings. This will prevent requests for SDK configuration using a client SDK key from obtaining unobfuscated keys, by requiring that the SDK is initialized with "enableObfuscation". It is recommended to require obfuscation when creating a new DevCycle project. If you are adding obfuscation to an existing project, you may want to leave this setting off until you have updated your code to use obfuscated keys, otherwise existing applications will no longer be able to receive a DevCycle configuration. Development Workflow and CI When using obfuscation, it is necessary to ensure that the generated constants are kept up to date with your project's set of possible Variable keys. There are different ways to accomplish this depending on your specific workflow, but in general we recommend committing the generated devcycleTypes file to source control and regenerating the file when a new Variable is added to DevCycle. To accomplish this more automatically, you can run the generator as part of a command which builds and runs your code in a local environment. This will ensure that each time you run the local code, the file is updated with the latest Variables. Archiving Variables When you archive a Variable in DevCycle, it will no longer appear in the generated output from the CLI. Make sure that Variables are no longer used in your code before archiving. Conditional Deferred Rendering Next.js users can take this a step further by also withholding any application source code that won't be used when a user is ineligible for a feature. This can improve page load performance while also hiding implementation details of features from users who shouldn't see them. To use this feature, follow the documentation for Conditional Deferred Rendering . When passing the Variable key to be evaluated, make sure to pass the obfuscated constant generated by the CLI. Edit this page Last updated on Jan 9, 2026 Previous Custom Property Schemas Next Roles & Permissions Requirements Setup Requiring Obfuscation Development Workflow and CI Archiving Variables Conditional Deferred Rendering DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:25 |
https://twitter.com/hashtag/APIIntersection?src=hash&ref_src=twsrc%5Etfw | JavaScript is not available. We’ve detected that JavaScript is disabled in this browser. Please enable JavaScript or switch to a supported browser to continue using x.com. You can see a list of supported browsers in our Help Center. Help Center Terms of Service Privacy Policy Cookie Policy Imprint Ads info © 2026 X Corp. Something went wrong, but don’t fret — let’s give it another shot. Try again Some privacy related extensions may cause issues on x.com. Please disable them and try again. | 2026-01-13T08:48:25 |
https://docs.devcycle.com/integrations/slack/ | Integration for Slack | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up On this page Integration for Slack This guide explains how to set up and use the DevCycle App for Slack. You can use the DevCycle App for Slack to keep track of and monitor feature flags within your team's Slack workspace. Setup Navigate to the Settings page in the DevCycle Dashboard, click on Integrations in the side navigation bar, and click View on the Integration for Slack. Click on the Add to Slack button and connect the DevCycle App for Slack with your workspace. Once the DevCycle app has been added, you can now subscribe to Feature changes on a project-level or by individual Feature(s). First, navigate to the Slack channel where you would like to have the Slack messages to be posted. To add a subscription for project-level changes, use the command /devcycle subscribe project-key . To find a project's respective key, go to your organization's Project Settings page and copy the key under the Project name. To add a subscription for individual feature changes, use the command /devcycle subscribe project-key [-f feature-key] . To add a subscription for a project or feature changes on a specific environment, add the flag [-e environment-key] to the command. For example, All Project changes for the specified Environment: /devcycle subscribe project-key [-e environment-key] All Feature changes that impact the specified Environment: /devcycle subscribe project-key [-f feature-key] [-e environment-key] Once you've susbcribed, you're all set! Go ahead and make some changes to a Feature then check your Slack Channel for notifications. Example Slack Message The View Project [Name] button will take you to the project that the Feature belongs to. The View Changes on Feature will take you to the Audit Log entry with more details about the Feature modification. Slack Commands /devcycle [ subscribe | unsubscribe | list | help ] /dvc [ subscribe | unsubscribe | list | help ] Private Channels To use the DevCycle Integration for Slack in private channels, you must invite the DevCycle App to the channel. Uninstall the DevCycle App for Slack In the case that you connected the DevCycle app for Slack to the wrong workspace or would like to remove it, please follow the instructions in this Slack Help Center article . Edit this page Last updated on Jan 9, 2026 Setup Example Slack Message Slack Commands Private Channels Uninstall the DevCycle App for Slack DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:25 |
https://www.linkedin.com/posts/suprsend_%F0%9D%97%A7%F0%9D%98%86%F0%9D%97%BD%F0%9D%97%B2-%F0%9D%98%80%F0%9D%97%AE%F0%9D%97%B3%F0%9D%97%B2-%F0%9D%98%84%F0%9D%97%BC%F0%9D%97%BF%F0%9D%97%B8%F0%9D%97%B3%F0%9D%97%B9%F0%9D%97%BC%F0%9D%98%84-%F0%9D%98%81%F0%9D%97%BF%F0%9D%97%B6-activity-7415021972293881856-Mq3D | SuprSend Supports Schema-Driven Type Generation for Workflow Triggers | SuprSend posted on the topic | LinkedIn Agree & Join LinkedIn By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Skip to main content LinkedIn Top Content People Learning Jobs Games Sign in Join now for free SuprSend Supports Schema-Driven Type Generation for Workflow Triggers This title was summarized by AI from the post below. SuprSend 19,129 followers 4d Report this post 𝗧𝘆𝗽𝗲-𝘀𝗮𝗳𝗲 𝘄𝗼𝗿𝗸𝗳𝗹𝗼𝘄 𝘁𝗿𝗶𝗴𝗴𝗲𝗿𝘀 𝗶𝗻 𝗦𝘂𝗽𝗿𝗦𝗲𝗻𝗱 🧩 Triggering workflows with loosely typed payloads often leads to bugs that only show up at runtime. To reduce that risk, SuprSend now supports schema-driven type generation for workflow triggers. You define the payload structure once as a JSON schema in SuprSend. From there, the CLI generates strongly-typed interfaces that you can use directly in your application code. What this improves: • Catch invalid payloads during development instead of production • Get IDE autocomplete and immediate feedback while coding • Keep workflow payloads consistent as schemas evolve • Avoid manually maintaining type definitions Type generation is available for 𝗧𝘆𝗽𝗲𝗦𝗰𝗿𝗶𝗽𝘁, 𝗣𝘆𝘁𝗵𝗼𝗻, 𝗚𝗼, 𝗝𝗮𝘃𝗮, 𝗞𝗼𝘁𝗹𝗶𝗻, 𝗦𝘄𝗶𝗳𝘁, 𝗮𝗻𝗱 𝗗𝗮𝗿𝘁. Docs in the comments. 7 1 Comment Like Comment Share Copy LinkedIn Facebook X SuprSend 4d Report this comment https://docs.suprsend.com/docs/type-generation Like Reply 1 Reaction To view or add a comment, sign in More Relevant Posts Marcus Neufeldt 3w Report this post The most powerful automation stack isn't "No-Code" or "Code." It's both. I use n8n and Make often. They're excellent for observability, the whole team can see exactly how data flows. But for the build phase? I prefer the raw leverage of code. The video below shows a tool I built this afternoon. I actually built something similar in early 2025 .. way before n8n workflow posts became LinkedIn engagement bait. Here's the problem: LLMs can generate basic n8n workflows, but they hallucinate nodes constantly. It's hit or miss whether you get something that actually runs. My fix: pull all native n8n nodes into a vector database, feed only the relevant ones to the LLM, validate the output. Done. Prompt in. Production-ready JSON out. Python handles the complexity. n8n handles the execution. This solves the biggest bottleneck in automation: manual friction. Dragging boxes one by one is slow. Generating architecture with code is instant. …more 1 Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Hema Thapa 6d Report this post Refactoring is 50% logic, 50% labeling. 🏷️ Most "complex" bugs don't start with bad logic—they start with unclear naming. If your function is named processData(), you’re forcing the next developer to read every line of your code just to understand its intent. Think of your code like a spice rack: Without labels, Red Chilli powder and Kashmiri Mirch look identical. One wrong guess, and the entire "dish" is ruined. Stop "Handling" and start "Defining": ❌ The "Mystery" Names: processData() handleRequest() ✅ The "Clean Code" Names: calculateTotalAmount() validateUserCredentials() The Professional Standard: Naming isn't just a "soft skill"—it’s a tool for reducing mental strain. Refactoring Tip: Sometimes the most high-impact PR you can submit isn't a logic rewrite. It’s hitting "rename option" to rename a variable until the code reads like a story, not a puzzle. The Goal: Clear naming doesn't just make code "pretty"—it makes it safe. What’s one "mystery" function name you’ve encountered (or written!) recently? 👇 #CleanCode #SoftwareEngineering #Refactoring #ProgrammingTips View C2PA information 13 Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Julius Haas 3w Report this post Cursor launched a Debug Mode to help you actually debug bugs. Hopefully this will end the endless back-and-forth of: “Please make sure not to repeat this error XY” and “Yes, Julius. You’re right” 😅 It works by forming multiple hypotheses, instrumenting your code with runtime logs, and walking you through reproducing and verifying the fix with real execution data. Read more: https://lnkd.in/gpKRWWVK Introducing Debug Mode: Agents with runtime logs cursor.com 9 1 Comment Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Yaki Aslan 1w Report this post TL;DR: I built a tool to test Rive files at runtime. It lets you poke at state machines and data bindings to see how they'll actually behave in an app before you start coding. Rive At Singit I spend a lot of time implementing Rive files in the product, and I kept hitting the same wall: things work fine in the editor, but then they get weird at runtime. It’s usually state machines or data bindings behaving unexpectedly or events/inputs not firing when they should. I looked for something online to help with this, but the apps I found felt pretty limited or just weren't comfortable to use for actual debugging. I ended up building a little tool to help me debug this stuff, and I figured I’d share it here in case anyone else finds it useful. Basically, it’s a tool where you can load a .riv file and just poke at it before you actually start writing any implementation code. What you can do with it: -Upload and test multiple .riv files at once -Switch between multiple artboards in the same file -Inspect and control state machines and inputs -Trigger events and transitions manually -Explore data bindings and runtime values -View real time Events and their properties -Test complex files -Reset runtime state to reproduce edge cases -Generate code snippets -Summaries files for handoff -Experiment safely before shipping to production I’ve been using this tool to review files from other designers and to generate snippets when ready to hand things off to engineering. It’s not meant to replace the editor or anything like that, it just helps bridge the gap between the design and the final app. It’s still pretty early, but it has saved me a lot of back-and-forth. If you’re working with Rive and want to test your files before you ship them, feel free to give it a try. [ https://www.rivelab.app/ ] (Just a disclaimer: I’m not affiliated with the Rive team, I just use their stuff a lot.) …more 34 13 Comments Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Vijaykumar Singh 1w Report this post Victor v0.3.0 is out — and it’s our most important release of 2025. After a year of iterating, learning, and refactoring in the open, this release finally delivers what we set out to prove: AI agents don’t have to become architectural monoliths as they scale. What shipped: Imports reduced 68 → <20 (71% ↓) Protocol-first architecture end to end 5 verticals fully decoupled 14K+ TDD - 100% passing ✅ The real win? Adding new AI agent capabilities no longer requires touching core framework code. That’s a huge unlock — and a strong way to close out 2025: cleaner boundaries, faster iteration, and architecture that won’t fight us next year. This is what sustainable AI agent architecture looks like. 🔗 Full release notes: https://lnkd.in/ggsWZ38v #AIAgents #SoftwareArchitecture #OpenSource #AIEngineering #Python Release Victor v0.3.0 - Domain-Framework Decoupling Release · vjsingh1984/victor github.com 5 Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Gianpiero Massa Tofo 2w Edited Report this post Never felt this much behind as a programmer — Andrej Karpathy. I've never felt this much behind as a programmer. The profession is being dramatically refactored as the bits contributed by the programmer are increasingly sparse and between. I have a sense that I could be 10X more powerful if I just properly string together what has become available over the last ~year and a failure to claim the boost feels decidedly like skill issue. There's a new programmable layer of abstraction to master (in addition to the usual layers below) involving agents, subagents, their prompts, contexts, memory, modes, permissions, tools, plugins, skills, hooks, MCP, LSP, slash commands, workflows, IDE integrations, and a need to build an all-encompassing mental model for strengths and pitfalls of fundamentally stochastic, fallible, unintelligible and changing entities suddenly intermingled with what used to be good old fashioned engineering. Clearly some powerful alien tool was handed around except it comes with no manual and everyone has to figure out how to hold it and operate it, while the resulting magnitude 9 earthquake is rocking the profession. Roll up your sleeves to not fall behind. — We just really just added the line jumps, for readability. — Skin in the game with Paolo Massa Tofo 4 1 Comment Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Venkatakumar Chembati 4d Report this post “Programs must be written for people to read, and only incidentally for machines to execute.” – Harold Abelson We focus so much on getting the code to work that we forget to make it readable. Clean code is about clarity, maintainability, and respect for the next developer who reads your work (which might just be future you). 𝗕𝗮𝗱 𝗖𝗼𝗱𝗲: public void d(int a, int b){ int x = a + b; if(x > 10){ System.out.println ("OK"); } } This code technically works, However it tells nothing about what is "a" and "b" and why it is being done. This makes the developers hard to read and often takes much time in debugging. 𝗖𝗹𝗲𝗮𝗻 𝗖𝗼𝗱𝗲: public void notifyIfAboveThreshold(int currentValue, int threshold){ int total = currentValue + threshold; if (total > MAX_THRESHOLD_VALUE) { System.out.println ("Threshold reached! Taking action..."); } } Now the method name, parameter names and the logic describe the purpose clearly. Anyone reading it immediately understands what it does. Write code that speaks clearly, not cryptically. Code for humans first — machines will always understand. 8 Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Ravi Kiran 6d Report this post "CLI coding agent" undersells it. Claude Code. Codex CLI. Gemini CLI. They're not just code tools. They're terminal-native general-purpose agents. → Filesystem access → Command execution → Agentic planning → Tool orchestration Useful for ANY workflow that needs automation + reasoning. Calling them "coding" tools is like calling a Swiss Army knife a "blade." If you're only using them to write code, you're leaving 70% on the table. 8 Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Sudhanshu Sharma ✨ 2w Edited Report this post Bring intelligent automation to your Claude Code workflows, without the token bloat. Claude code plugins, a comprehensive system that lets Claude Code build, orchestrate and automate faster ⚡ Free and open-source! → 99 specialized AI agents → 15 multi-agent orchestrators → 107 specialized skills + 71 dev tools → Granular plugins for minimal token usage Some great use cases: #1 - I want full-stack features automated → orchestrate 7+ agents for complex development, like user authentication with OAuth2. #2 - I need robust security → multi-agent security assessment with SAST, dependency scanning, and AI-powered code review. #3 - I'm building with Python → scaffold production-ready FastAPI projects with async patterns, activating specialized skills for testing and package management. #4 - I need to optimize model costs → leverage the three-tier model strategy (Opus → Sonnet → Haiku) for optimal performance and efficiency. Check out the free, open-source repo: → https://lnkd.in/dxAZeuec ---- ♻️ If this was useful, repost it so others can benefit too. Follow me for more post like this 32 Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Saisreeram Kakaraparthi 1w Report this post A small .ToList() taught me a performance lesson today. While solving a problem, I initially wrote this: if (nums.Distinct().ToList().Count != nums.Length) return true; It worked, but the runtime was 18ms. Later, I changed it slightly: if (nums.Distinct().Count() != nums.Length) return true; Same logic. Runtime dropped to 13ms. That small change made me stop and think. What was really happening? LINQ follows deferred execution. LINQ doesn’t execute anything immediately. It just builds a query. In my first version: • Distinct() built the query • .ToList() forced execution immediately • The entire sequence was iterated • A new list was created in memory • Then Count was read from that list In the second version: • Distinct() still didn’t run immediately • Count() triggered execution • The sequence was iterated once • No intermediate list, no extra allocation A simple reminder for me: • LINQ is lazy by default • ToList() is not free • Small choices affect performance Next time I write ToList(), I’ll pause and think about what’s happening under the hood. #CSharp #DotNet #LINQ #PerformanceMatters #LearningInPublic #SoftwareEngineering 9 2 Comments Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in 19,129 followers View Profile Connect Explore content categories Career Productivity Finance Soft Skills & Emotional Intelligence Project Management Education Technology Leadership Ecommerce User Experience Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language Sign in to view more content Create your free account or sign in to continue your search Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . | 2026-01-13T08:48:25 |
https://www.linkedin.com/posts/suprsend_%F0%9D%97%9F%F0%9D%97%9C%F0%9D%97%A9%F0%9D%97%98-%F0%9D%97%9B%F0%9D%97%BC%F0%9D%98%80%F0%9D%98%81%F0%9D%97%B2%F0%9D%97%B1-%F0%9D%97%A3%F0%9D%97%BF%F0%9D%97%B2%F0%9D%97%B3%F0%9D%97%B2%F0%9D%97%BF%F0%9D%97%B2%F0%9D%97%BB%F0%9D%97%B0%F0%9D%97%B2-activity-7410683576045891584-M5EH | SuprSend Preference Page for Global User Control | SuprSend posted on the topic | LinkedIn Agree & Join LinkedIn By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Skip to main content LinkedIn Top Content People Learning Jobs Games Sign in Join now SuprSend Preference Page for Global User Control This title was summarized by AI from the post below. SuprSend 19,129 followers 2w Report this post [𝗟𝗜𝗩𝗘] 𝗛𝗼𝘀𝘁𝗲𝗱 𝗣𝗿𝗲𝗳𝗲𝗿𝗲𝗻𝗰𝗲 𝗣𝗮𝗴𝗲: 𝗥𝗲𝗮𝗱𝘆-𝘁𝗼-𝘂𝘀𝗲 𝘂𝘀𝗲𝗿 𝘀𝗲𝘁𝘁𝗶𝗻𝗴𝘀 🌍 SuprSend now gives you a ready-made Preference Page where users can manage how they receive notifications. Just link to it from your emails or SMS — no need to build or maintain your own preference system. It’s designed to help you stay compliant while giving users better control over their communication. We’ve now added full localization support so these pages work seamlessly for global audiences. What’s new: • Pages adapt automatically to the user’s locale • Category names, descriptions, and sections are rendered dynamically • Static page text is localized • Smart fallback when a regional language isn’t available If you’re sending notifications across regions, this makes preference management clearer for users and easier to scale for teams. Preview link in the comments. 5 Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in More Relevant Posts M.A. Utsav 1mo Report this post Google is upgrading Translate and related features with Gemini so translations sound more natural, work live in your headphones, and support more language-learning tools. 1 Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Gennady Novik 4w Report this post Today #Google is finally revamping Google Translate, infusing it with Gemini capabilities in order to improve translations, especially on phrases with nuanced meanings like idioms, local expressions, or slang. https://vist.ly/4ijv2 Google Translate is now powered by Gemini, includes live translations on headphones gsmarena.com 1 Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Arthur Pentecoste 4d Report this post 40% of your traffic might be qualified. And still completely blocked from buying. Not because of price. Not because of product. Because of language. Localization isn’t a “nice to have.” It’s a visibility layer. If users can’t fully understand your site, they don’t explore, they don’t trust, and they don’t convert, even when the product fits their need perfectly. Most brands think this is a translation problem. It’s actually a revenue problem. Swipe to see how language friction silently kills conversion and where the real headroom is hiding. 9 2 Comments Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Canvasflow Ltd 97 followers 4d Report this post If you're looking to expand your customer base beyond borders, consider having a multilingual site. Here's why: 7 in 10 people prefer to read product reviews in their native language. So if you want to conquer foreign markets or appeal to different language speakers in your country, consider building a multi-lingual website. Your thoughts? Find more benefits of having a multilingual website here: https://heyor.ca/0kbDKV #MultilingualWebsite #WebsiteLocalisation #LanguageDiversity Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Andrew Brown 4d Report this post If you're looking to expand your customer base beyond borders, consider having a multilingual site. Here's why: 7 in 10 people prefer to read product reviews in their native language. So if you want to conquer foreign markets or appeal to different language speakers in your country, consider building a multi-lingual website. Your thoughts? Find more benefits of having a multilingual website here: https://heyor.ca/0kbDKV #MultilingualWebsite #WebsiteLocalisation #LanguageDiversity 1 Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Mohit Bansal 1w Edited Report this post ❌ Ever broken your Flutter localization just by editing a .arb file? As localization scales, large ARB files become difficult to manage, and collaboration with translators or non-technical stakeholders often leads to errors and broken keys. 🚀 Introducing arb_excel_converter_tool (v1.1.1) A simple and effective solution that converts ARB ↔ Excel seamlessly—making Flutter localization safer, cleaner, and easier to maintain. ✨ Why it’s useful Convert .arb files to Excel for easy review and collaboration Convert Excel back to .arb without breaking localization keys Ideal for working with translators and non-technical teams Saves time and reduces manual errors 📦 Package: arb_excel_converter_tool 🔗 Pub.dev : https://lnkd.in/gkYRqVn2 🔗 GitHub (v1.1.1): https://lnkd.in/gXY4TafJ 🛠 Perfect for Flutter projects with multi-language support. If you’re working on localization-heavy apps, this can significantly improve your workflow. #Flutter #Localization #Dart #MobileDevelopment #DeveloperTools #i18n GitHub - mohititian/arb_excel_converter_tool github.com 7 Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in SaaSili.Digital 12 followers 3w Report this post Global Growth Breaks on Language Most SaaS products are built to scale globally. Most SaaS messages are not. Teams expand with English-first content and assume translation will fix it later. It rarely does. Buyers don’t just read your message. They decide, almost instantly, whether it feels like it was written for them. If it feels foreign, trust drops. Word-for-word translation keeps meaning, but often loses intent. And intent is what drives action in SaaS. Local markets respond to tone, familiarity, and clarity, not perfect grammar. When messaging feels native, performance shifts quickly. Engagement rises. Replies increase. Pipeline follows. The real mistake isn’t translating. It’s treating language as an afterthought. Global GTM works best when localisation is built in from day one, not bolted on once expansion starts. If your message isn’t immediately understood, it won’t convert. Takeaway: Global scale demands local language. Anything less creates friction. SaaSili.Digital turns one SaaS message into swipeable, localised carousels built to perform across markets. #SaaSMarketing #GlobalGTM #B2BSaaS #Localization #ContentStrategy #DemandGen #LinkedInMarketing #SaaSiliDigital Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Souvik Banerjee 4w Report this post Google Launches Live Headphone Translation and New Gemini Enhancements in Google Translate #gadget Source: https://ift.tt/BVoPm5R I am excited to share our latest blog post highlighting the innovative features recently launched by Google in Google Translate. This post delves into the new Live Headphone Translation capability, which offers real-time spoken translations through headphones, effectively preserving the speaker's tone and rhythm for enhanced clarity. In addition to this groundbreaking feature, we explore the incorporation of Gemini enhancements that improve translation intelligence by managing context-rich phrases and idiomatic expressions with greater accuracy. Moreover, Google's expansion of language-learning functionalities across nearly 20 additional countries promises to transform how users engage with new languages. These advancements are set to redefine multilingual communication and learning experiences. To read more about these pivotal changes, visit the link: [Google Launches Live Headphone Translation and New Gemini Enhancements in Google Translate]( https://ift.tt/BVoPm5R ). Stay informed on how technology continues to bridge communication gaps worldwide. #rswebsols #GoogleTranslate #RealTimeTranslation #HeadphoneTech #GeminiAI #LanguageLearning Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Natchi Lazarus 1w Report this post Google Translate Integrates Gemini for Improved Live Translation Google Translate now includes Gemini for enhanced translation capabilities, featuring live speech-to-speech translation. This advancement allows for real-time communication in multiple languages, which could be particularly beneficial for multilingual congregations. You simply have to ask your congregation to download the Google Translate app on their phone, wear a headphone and follow along in the language of their choice. 3 1 Comment Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Tarun Chandrasekhar 3w Report this post Global brands aren’t just translating—they’re reinventing the way they connect. Localization has shifted from a creative afterthought to a strategic data discipline. Why? Because delivering accurate, relevant, and compliant content worldwide takes more than words—it takes structured, governed data. Hear Helen Grimster break it down in our on-demand webinar with Forrester on 2026 predictions: 👉 https://lnkd.in/dm65a_EJ 7 Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in 19,129 followers View Profile Connect Explore content categories Career Productivity Finance Soft Skills & Emotional Intelligence Project Management Education Technology Leadership Ecommerce User Experience Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language Sign in to view more content Create your free account or sign in to continue your search Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . | 2026-01-13T08:48:25 |
https://docs.devcycle.com/integrations/bitbucket/feature-usage-action/ | Bitbucket: Feature Flag Code Usages | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up On this page Bitbucket: Feature Flag Code Usages Get the integration on the Bitbucket Marketplace Bitbucket Pipelines Pipe: DevCycle Code References Code References of DevCycle Variables pushed to DevCycle With this Bitbucket pipeline, your DevCycle dashboard will be updated to display code snippets for each DevCycle variable usage within your project. Note: This is intended to run when pushing changes to your main branch Example Output YAML Definition Add the following snippet to your bitbucket-pipelines.yml file: branches : main : - step : script : - pipe : devcyclehq/bitbucket - code - refs - pipe : 1.0.3 variables : PROJECT_KEY : '<string>' CLIENT_ID : '<string>' CLIENT_SECRET : '<string>' Variables To add variables to be used in the bitbucket-pipelines.yml , an admin must add Repository Variables in Repository Settings > Repository Variables , and then add all necessary variables as secured variables Variable Usage PROJECT_KEY (*) Your DevCycle project key, see Projects CLIENT_ID (*) Your organization's API client ID, see Organization Settings CLIENT_SECRET (*) Your organization's API client secret, see Organization Settings (*) = required variable. Prerequisites Create a new Project & a new Feature Grab the PROJECT_KEY in Projects , and find your specific project name & key Grab the CLIENT_ID in Settings , under API AUTHENTICATION Grab the CLIENT_SECRET in Settings , under API AUTHENTICATION Examples Example: - pipe : devcyclehq/bitbucket - code - refs - pipe : 1.0.3 variables : PROJECT_KEY : $PROJECT_KEY CLIENT_ID : $CLIENT_ID CLIENT_SECRET : $CLIENT_SECRET Support The pipe is maintained by [email protected] . If you are reporting an issue, please include: the version of the pipe relevant logs and error messages steps to reproduce Edit this page Example Output YAML Definition Variables Prerequisites Examples Support DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:25 |
https://docs.devcycle.com/platform/testing-and-qa/debug-tools/evaluation-lookup | Evaluation Lookup | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up Home Getting Started Essentials DevCycle Overview Key Features System Architecture Feature Hierarchy Feature Types Platform Feature Flags Experimentation Account Management Security and Guardrails Testing and QA Debug Tools Evaluation Lookup Point-in-time Simulation Live Events Web Debugger Self-Targeting Extras Examples Platform Testing and QA Debug Tools Evaluation Lookup On this page Evaluation Lookup The Evaluation Lookup debugging tool lets you view historical Variable Evaluation data for your users. It shows which Features and Variables a user received at a given point in time, along with the reasoning behind that configuration. warning Ad blockers may prevent you from seeing events sent to DevCycle, as such the Debug Tools may not show the full picture of events. Why use it? Verify that a user received a specific Feature, Variable or Variation. Understand the reason behind why a user did or did not receive a Feature, Variable, or Variation. Audit all Features, Variables, and Variations a user received during a specific time period, with the option to filter results further. Usage Evaluation Lookup allows you to see Variable Evaluations for a given user. To start, input a user_id , select an Environment and pick a date range, and it will return all the evaluations in that given timeframe. There are also optional parameters you can filter by, such as Variable key, Feature name, SDK Type, and Platform. Results Once you run a search, Variable Evaluations are returned along with the latest set of User Information for the specified user_id . The results table shows: The Variable that was evaluated The Timestamp for when it was triggered The Feature and Variation that was received with a link to the Feature if available The Evaluation Reason We’ll break down both sections below. User Information When expanded, this section displays the latest set of user data evaluated for the specified user_id . Any Custom Properties you’ve included will also be displayed here. Coming soon, users will have the ability to Simulate a configuration request at any point in time. This will let you see which Features or Variables a user would receive under a specific configuration at a given moment in time. Evaluations The results table displays all Variable Evaluations for the selected user_id and date range. Each entry includes the Variable key, associated Feature, received Variation, and the reason it was or was not targeted. When viewing details for a Variable Evaluation, you’ll also see the raw data from the DevCycle SDK that populates the table. Edit this page Last updated on Jan 9, 2026 Previous Variable Schemas Next Point-in-time Simulation Usage Results User Information Evaluations DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:25 |
https://www.linkedin.com/legal/user-agreement?trk=d_checkpoint_rp_requestPasswordReset_ft_user_agreement | User Agreement | LinkedIn Skip to main content User Agreement Summary of User Agreement Privacy Policy Professional Community Policies Cookie Policy Copyright Policy Regional Info EU Notice California Privacy Disclosure U.S. State Privacy Laws User Agreement Summary of User Agreement Privacy Policy Professional Community Policies Cookie Policy Copyright Policy Regional Info EU Notice California Privacy Disclosure U.S. State Privacy Laws User Agreement Effective on November 3, 2025 Our mission is to connect the world’s professionals to allow them to be more productive and successful. Our services are designed to promote economic opportunity for our members by enabling you and millions of other professionals to meet, exchange ideas, learn, and find opportunities or employees, work, and make decisions in a network of trusted relationships. Table of Contents: Introduction Obligations Rights and Limits Disclaimer and Limit of Liability Termination Governing Law and Dispute Resolution General Terms LinkedIn “Dos and Don’ts” Complaints Regarding Content How To Contact Us Introduction 1.1 Contract When you use our Services you agree to all of these terms. Your use of our Services is also subject to our Cookie Policy and our Privacy Policy, which covers how we collect, use, share, and store your personal information. By creating a LinkedIn account or accessing or using our Services (described below), you are agreeing to enter into a legally binding contract with LinkedIn (even if you are using third party credentials or using our Services on behalf of a company). If you do not agree to this contract (“Contract” or “User Agreement”), do not create an account or access or otherwise use any of our Services. If you wish to terminate this Contract at any time, you can do so by closing your account and no longer accessing or using our Services. As a Visitor or Member of our Services, the collection, use, and sharing of your personal data is subject to our Privacy Policy , our Cookie Policy and other documents referenced in our Privacy Policy , and updates. You acknowledge and have read our Privacy Policy . Services This Contract applies to LinkedIn.com, LinkedIn-branded apps, and other LinkedIn-related sites, apps, communications, and other services that state that they are offered under this Contract (“Services”), including the offsite collection of data for those Services, such as via our ads and the “Apply with LinkedIn” and “Share with LinkedIn” plugins. LinkedIn and other Key Terms You are entering into this Contract with LinkedIn (also referred to as “we” and “us”). Designated Countries . We use the term “Designated Countries” to refer to countries in the European Union (EU), European Economic Area (EEA), and Switzerland. If you reside in the “Designated Countries”, you are entering into this Contract with LinkedIn Ireland Unlimited Company (“LinkedIn Ireland”) and LinkedIn Ireland will be the controller of your personal data provided to, or collected by or for, or processed in connection with our Services. If you reside outside of the “Designated Countries”, you are entering into this Contract with LinkedIn Corporation (“LinkedIn Corp.”) and LinkedIn Corp. will be the controller of (or business responsible for) your personal data provided to, or collected by or for, or processed in connection with our Services. Affiliates . Affiliates are companies controlling, controlled by or under common control with us, including, for example, LinkedIn Ireland, LinkedIn Corporation, LinkedIn Singapore and Microsoft Corporation or any of its subsidiaries (e.g., Github, Inc.). Social Action . Actions that members take on our services such as likes, comments, follows, sharing content. Content . Content includes, for example, feed posts, feedback, comments, profiles, articles (and contributions), group posts, job postings, messages (including InMails), videos, photos, audio, and/or PDFs. 1.2 Members and Visitors This Contract applies to Members and Visitors. When you register and join the LinkedIn Services, you become a “Member”. If you have chosen not to register for our Services, you may access certain features as a “Visitor.” 1.3 Changes We may make changes to this Contract. We may modify this Contract, our Privacy Policy and our Cookie Policy from time to time. If we materially change these terms or if we are legally required to provide notice, we will provide you notice through our Services, or by other means, to provide you the opportunity to review the changes before they become effective. However, we may not always provide prior notice of changes to these terms (1) when those changes are legally required to be implemented with immediate effect, or (2) when those changes relate to a newly launched service or feature. We agree that changes cannot be retroactive. If you object to any of these changes, you may close your account . Your continued use of our Services after we publish or send a notice about our changes to these terms means that you are consenting to the updated terms as of their effective date. 2. Obligations 2.1 Service Eligibility Here are some promises that you make to us in this Contract: You’re eligible to enter into this Contract and you are at least our “Minimum Age.” The Services are not for use by anyone under the age of 16. To use the Services, you agree that: (1) you must be the "Minimum Age" (described below) or older; (2) you will only have one LinkedIn account, which must be in your real name; and (3) you are not already restricted by LinkedIn from using the Services. Creating an account with false information is a violation of our terms, including accounts registered on behalf of others or persons under the age of 16. “Minimum Age” means 16 years old. However, if law requires that you must be older in order for LinkedIn to lawfully provide the Services to you without parental consent (including using your personal data) then the Minimum Age is such older age. Learn More 2.2 Your Account You will keep your password a secret You will not share your account with anyone else and will follow our policies and the law. Members are account holders. You agree to: (1) protect against wrongful access to your account (e.g., use a strong password and keep it confidential); (2) not share or transfer your account or any part of it (e.g., sell or transfer the personal data of others by transferring your connections); and (3) follow the law, our list of Dos and Don’ts (below), and our Professional Community Policies . Learn More You are responsible for anything that happens through your account unless you close it or report misuse. As between you and others (including your employer), your account belongs to you. However, if the Services were purchased by another party for you to use in connection with your work for them (e.g., Recruiter seat or LinkedIn Learning subscription bought by your employer), the party paying for such Service has the right to control access to and get reports on your use of such paid Service; however, they do not have rights to your personal account. 2.3 Payment You’ll honor your payment obligations and you are okay with us storing your payment information. You understand that there may be fees and taxes that are added to our prices. Refunds are subject to our policy, and we may modify our prices and those modified prices will apply prospectively. If you buy any of our paid Services, you agree to pay us the applicable fees and taxes and you agree to the additional terms specific to the paid Services. Failure to pay these fees will result in the termination of your paid Services. Also, you agree that: Your purchase may be subject to foreign exchange fees or differences in prices based on location (e.g., exchange rates). We may store and continue billing your payment method (e.g., credit card), even after it has expired, to avoid interruptions in your paid Services and to use it to pay for other Services you may buy. If your primary payment method fails, we may automatically charge a secondary payment method, if you have provided one. You may update or change your payment method. Learn more If you purchase a subscription, your payment method automatically will be charged at the start of each subscription period for the fees and taxes applicable to that period. To avoid future charges, cancel before the renewal date. Learn how to cancel or suspend your paid subscription Services. We may modify our prices effective prospectively upon reasonable notice to the extent allowed under the law. All of your paid Services are subject to LinkedIn’s refund policy . We may calculate taxes payable by you based on the billing information that you provide us. You can get a copy of your invoice through your LinkedIn account settings under “ Purchase History ”. 2.4 Notices and Messages You’re okay with us providing notices and messages to you through our websites, apps, and contact information. If your contact information is out of date, you may miss out on important notices. You agree that we will provide notices and messages to you in the following ways: (1) within the Services or (2) sent to the contact information you provided us (e.g., email, mobile number, physical address). You agree to keep your contact information up to date. Please review your settings to control and limit the types of messages you receive from us. 2.5 Sharing When you share information on our Services, others can see, copy and use that information. Our Services allow sharing of information (including content) in many ways, such as through your profile, posts, articles, group posts, links to news articles, job postings, messages, and InMails. Depending on the feature and choices you make, information that you share may be seen by other Members, Visitors, or others (on or off of the Services). Where we have made settings available, we will honor the choices you make about who can see content or other information (e.g., message content to your addressees, sharing content only to LinkedIn connections, restricting your profile visibility from search tools, or opting not to notify others of your LinkedIn profile update). For job searching activities, we default to not notifying your connections or the public. So, if you apply for a job through our Services or opt to signal that you are interested in a job, our default is to share it only with the job poster. To the extent that laws allow this, we are not obligated to publish any content or other information on our Services and can remove it with or without notice. 3. Rights and Limits 3.1. Your License to LinkedIn You own all of your original content that you provide to us, but you also grant us a non-exclusive license to it. We’ll honor the choices you make about who gets to see your content, including how it can be used for ads. As between you and LinkedIn, you own your original content that you submit or post to the Services. You grant LinkedIn and our Affiliates the following non-exclusive license to the content and other information you provide (e.g., share, post, upload, and/or otherwise submit) to our Services: A worldwide, transferable and sublicensable right to use, copy, modify, distribute, publicly perform and display, host, and process your content and other information without any further consent, notice and/or compensation to you or others. These rights are limited in the following ways: You can end this license for specific content by deleting such content from the Services, or generally by closing your account, except (a) to the extent you (1) shared it with others as part of the Services and they copied, re-shared it or stored it, (2) we had already sublicensed others prior to your content removal or closing of your account, or (3) we are required by law to retain or share it with others, and (b) for the reasonable time it takes to remove the content you delete from backup and other systems. We will not include your content in advertisements for the products and services of third parties to others without your separate consent (including sponsored content). However, without compensation to you or others, ads may be served near your content and other information, and your social actions may be visible and included with ads, as noted in the Privacy Policy. If you use a Service feature, we may mention that with your name or photo to promote that feature within our Services, subject to your settings. We will honor the audience choices for shared content (e.g., “Connections only”). For example, if you choose to share your post to "Anyone on or off LinkedIn” (or similar): (a) we may make it available off LinkedIn; (b) we may enable others to publicly share onto third-party services (e.g., a Member embedding your post on a third party service); and/or (c) we may enable search tools to make that public content findable though their services. Learn More While we may edit and make format changes to your content (such as translating or transcribing it, modifying the size, layout or file type, and removing or adding labels or metadata), we will take steps to avoid materially modifying the meaning of your expression in content you share with others. Because you own your original content and we only have non-exclusive rights to it, you may choose to make it available to others, including under the terms of a Creative Commons license . You and LinkedIn agree that if content includes personal data, it is subject to our Privacy Policy. You and LinkedIn agree that we may access, store, process, and use any information (including content and/or personal data) that you provide in accordance with the terms of the Privacy Policy and your choices (including settings). By submitting suggestions or other feedback regarding our Services to LinkedIn, you agree that LinkedIn can use and share (but does not have to) such feedback for any purpose without compensation to you. You promise to only provide content and other information that you have the right to share and that your LinkedIn profile will be truthful. You agree to only provide content and other information that does not violate the law or anyone’s rights (including intellectual property rights). You have choices about how much information to provide on your profile but also agree that the profile information you provide will be truthful. LinkedIn may be required by law to remove certain content and other information in certain countries. 3.2 Service Availability We may change or limit the availability of some features, or end any Service. We may change, suspend or discontinue any of our Services. We may also limit the availability of features, content and other information so that they are not available to all Visitors or Members (e.g., by country or by subscription access). We don’t promise to store or show (or keep showing) any information (including content) that you’ve shared. LinkedIn is not a storage service. You agree that we have no obligation to store, maintain or provide you a copy of any content or other information that you or others provide, except to the extent required by applicable law and as noted in our Privacy Policy. 3.3 Other Content, Sites and Apps Your use of others’ content and information posted on our Services, is at your own risk. Others may offer their own products and services through our Services, and we aren’t responsible for those third-party activities. Others’ Content: By using the Services, you may encounter content or other information that might be inaccurate, incomplete, delayed, misleading, illegal, offensive, or otherwise harmful. You agree that we are not responsible for content or other information made available through or within the Services by others, including Members. While we apply automated tools to review much of the content and other information presented in the Services, we cannot always prevent misuse of our Services, and you agree that we are not responsible for any such misuse. You also acknowledge the risk that others may share inaccurate or misleading information about you or your organization, and that you or your organization may be mistakenly associated with content about others, for example, when we let connections and followers know you or your organization were mentioned in the news. Members have choices about this feature . Others’ Products and Services: LinkedIn may help connect you to other Members (e.g., Members using Services Marketplace or our enterprise recruiting, jobs, sales, or marketing products) who offer you opportunities (on behalf of themselves, their organizations, or others) such as offers to become a candidate for employment or other work or offers to purchase products or services. You acknowledge that LinkedIn does not perform these offered services, employ those who perform these services, or provide these offered products. You further acknowledge that LinkedIn does not supervise, direct, control, or monitor Members in the making of these offers, or in their providing you with work, delivering products or performing services, and you agree that (1) LinkedIn is not responsible for these offers, or performance or procurement of them, (2) LinkedIn does not endorse any particular Member’s offers, and (3) LinkedIn is not an agent or employment agency on behalf of any Member offering employment or other work, products or services. With respect to employment or other work, LinkedIn does not make employment or hiring decisions on behalf of Members offering opportunities and does not have such authority from Members or organizations using our products. For Services Marketplace , (a) you must be at least 18 years of age to procure, offer, or perform services, and (b) you represent and warrant that you have all the required licenses and will provide services consistent with the relevant industry standards and our Professional Community Policies . Others’ Events: Similarly, LinkedIn may help you register for and/or attend events organized by Members and connect with other Members who are attendees at such events. You agree that (1) LinkedIn is not responsible for the conduct of any of the Members or other attendees at such events, (2) LinkedIn does not endorse any particular event listed on our Services, (3) LinkedIn does not review and/or vet any of these events or speakers, and (4) you will adhere to the terms and conditions that apply to such events. 3.4 Limits We have the right to limit how you connect and interact on our Services. LinkedIn reserves the right to limit your use of the Services, including the number of your connections and your ability to contact other Members. LinkedIn reserves the right to restrict, suspend, or terminate your account if you breach this Contract or the law or are misusing the Services (e.g., violating any of the Dos and Don’ts or Professional Community Policies ). We can also remove any content or other information you shared if we believe it violates our Professional Community Policies or Dos and Don’ts or otherwise violates this Contract. Learn more about how we moderate content. 3.5 Intellectual Property Rights We’re providing you notice about our intellectual property rights. LinkedIn reserves all of its intellectual property rights in the Services. Trademarks and logos used in connection with the Services are the trademarks of their respective owners. LinkedIn, and “in” logos and other LinkedIn trademarks, service marks, graphics and logos used for our Services are trademarks or registered trademarks of LinkedIn. 3.6 Recommendations and Automated Processing We use data and other information about you to make and order relevant suggestions and to generate content for you and others. Recommendations: We use the data and other information that you provide and that we have about Members and content on the Services to make recommendations for connections, content, ads, and features that may be useful to you. We use that data and other information to recommend and to present information to you in an order that may be more relevant for you. For example, that data and information may be used to recommend jobs to you and you to recruiters and to organize content in your feed in order to optimize your experience and use of the Services. Keeping your profile accurate and up to date helps us to make these recommendations more accurate and relevant. Learn More Generative AI Features: By using the Services, you may interact with features we offer that automate content generation for you. The content that is generated might be inaccurate, incomplete, delayed, misleading or not suitable for your purposes. Please review and edit such content before sharing with others. Like all content you share on our Services, you are responsible for ensuring it complies with our Professional Community Policies , including not sharing misleading information. The Services may include content automatically generated and shared using tools offered by LinkedIn or others off LinkedIn. Like all content and other information on our Services, regardless of whether it's labeled as created by “AI”, be sure to carefully review before relying on it. 4. Disclaimer and Limit of Liability 4.1 No Warranty This is our disclaimer of legal liability for the quality, safety, or reliability of our Services. LINKEDIN AND ITS AFFILIATES MAKE NO REPRESENTATION OR WARRANTY ABOUT THE SERVICES, INCLUDING ANY REPRESENTATION THAT THE SERVICES WILL BE UNINTERRUPTED OR ERROR-FREE, AND PROVIDE THE SERVICES (INCLUDING CONTENT, OUTPUT AND INFORMATION) ON AN “AS IS” AND “AS AVAILABLE” BASIS. TO THE FULLEST EXTENT PERMITTED UNDER APPLICABLE LAW, LINKEDIN AND ITS AFFILIATES DISCLAIM ANY IMPLIED OR STATUTORY WARRANTY, INCLUDING ANY IMPLIED WARRANTY OF TITLE, ACCURACY, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. If you plan to use content, output and information for any reason, it is your responsibility to verify its accuracy and fitness for your purposes, because any content, output and information on the service may not reflect accurate, complete, or current information. 4.2 Exclusion of Liability These are the limits of legal liability we may have to you. TO THE FULLEST EXTENT PERMITTED BY LAW (AND UNLESS LINKEDIN HAS ENTERED INTO A SEPARATE WRITTEN AGREEMENT THAT OVERRIDES THIS CONTRACT), LINKEDIN AND ITS AFFILIATES, WILL NOT BE LIABLE IN CONNECTION WITH THIS CONTRACT FOR LOST PROFITS OR LOST BUSINESS OPPORTUNITIES, REPUTATION (E.G., OFFENSIVE OR DEFAMATORY STATEMENTS), LOSS OF DATA (E.G., DOWN TIME OR LOSS, USE OF, OR CHANGES TO, YOUR INFORMATION OR CONTENT) OR ANY INDIRECT, INCIDENTAL, CONSEQUENTIAL, SPECIAL OR PUNITIVE DAMAGES. LINKEDIN AND ITS AFFILIATES WILL NOT BE LIABLE TO YOU IN CONNECTION WITH THIS CONTRACT FOR ANY AMOUNT THAT EXCEEDS (A) THE TOTAL FEES PAID OR PAYABLE BY YOU TO LINKEDIN FOR THE SERVICES DURING THE TERM OF THIS CONTRACT, IF ANY, OR (B) US $1000. 4.3 Basis of the Bargain; Exclusions The limitations of liability in this Section 4 are part of the basis of the bargain between you and LinkedIn and shall apply to all claims of liability (e.g., warranty, tort, negligence, contract and law) even if LinkedIn or its affiliates has been told of the possibility of any such damage, and even if these remedies fail their essential purpose. THESE LIMITATIONS OF LIABILITY DO NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY OR FOR FRAUD, GROSS NEGLIGENCE OR INTENTIONAL MISCONDUCT, OR IN CASES OF NEGLIGENCE, WHERE A MATERIAL OBLIGATION HAS BEEN BREACHED. A MATERIAL OBLIGATION BEING AN OBLIGATION WHICH FORMS A PREREQUISITE TO OUR DELIVERY OF SERVICES AND ON WHICH YOU MAY REASONABLY RELY, BUT ONLY TO THE EXTENT THAT THE DAMAGES WERE DIRECTLY CAUSED BY THE BREACH AND WERE FORESEEABLE UPON CONCLUSION OF THIS CONTRACT AND TO THE EXTENT THAT THEY ARE TYPICAL IN THE CONTEXT OF THIS CONTRACT. 5. Termination We can each end this Contract, but some rights and obligations survive. Both you and LinkedIn may terminate this Contract at any time with notice to the other. On termination, you lose the right to access or use the Services. The following shall survive termination: Our rights to use and disclose your feedback; Section 3 (subject to 3.1.1); Sections 4, 6, 7, and 8.2 of this Contract; and Any amounts owed by either party prior to termination remain owed after termination. You can visit our Help Center to learn about how to close your account 6. Governing Law and Dispute Resolution In the unlikely event we end up in a legal dispute, depending on where you live, you and LinkedIn agree to resolve it in California courts using California law, Dublin, Ireland courts using Irish law, or as otherwise provided in this section. If you live in the Designated Countries, the laws of Ireland govern all claims related to LinkedIn's provision of the Services, but this shall not deprive you of the mandatory consumer protections under the law of the country to which we direct your Services where you have habitual residence. With respect to jurisdiction, you and LinkedIn agree to choose the courts of the country to which we direct your Services where you have habitual residence for all disputes arising out of or relating to this User Agreement, or in the alternative, you may choose the responsible court in Ireland. If you are a business user within the scope of Article 6(12) of the EU Digital Markets Act (“DMA”) and have a dispute arising out of or in connection with Article 6(12) of the DMA, you may also utilize the alternative dispute resolution mechanism available in the Help Center . For others outside of Designated Countries, including those who live outside of the United States: You and LinkedIn agree that the laws of the State of California, U.S.A., excluding its conflict of laws rules, shall exclusively govern any dispute relating to this Contract and/or the Services. You and LinkedIn both agree that all claims and disputes can be litigated only in the federal or state courts in Santa Clara County, California, USA, and you and LinkedIn each agree to personal jurisdiction in those courts. You may have additional rights of redress and appeal for some decisions made by LinkedIn that impact you. 7. General Terms Here are some important details about the Contract. If a court with authority over this Contract finds any part of it unenforceable, you and we agree that the court should modify the terms to make that part enforceable while still achieving its intent. If the court cannot do that, you and we agree to ask the court to remove that unenforceable part and still enforce the rest of this Contract. This Contract (including additional terms that may be provided by us when you engage with a feature of the Services) is the only agreement between us regarding the Services and supersedes all prior agreements for the Services. If we don't act to enforce a breach of this Contract, that does not mean that LinkedIn has waived its right to enforce this Contract. You may not assign or transfer this Contract (or your membership or use of Services) to anyone without our consent. However, you agree that LinkedIn may assign this Contract to its affiliates or a party that buys it without your consent. There are no third-party beneficiaries to this Contract. You agree that the only way to provide us legal notice is at the addresses provided in Section 10. 8. LinkedIn “Dos and Don’ts” LinkedIn is a community of professionals. This list of “Dos and Don’ts” along with our Professional Community Policies limits what you can and cannot do on our Services, unless otherwise explicitly permitted by LinkedIn in a separate writing (e.g., through a research agreement). 8.1. Dos You agree that you will: Comply with all applicable laws, including, without limitation, privacy laws, intellectual property laws, anti-spam laws, export control laws, laws governing the content shared, and other applicable laws and regulatory requirements; Provide accurate contact and identity information to us and keep it updated; Use your real name on your profile; and Use the Services in a professional manner. 8.2. Don’ts You agree that you will not : Create a false identity on LinkedIn, misrepresent your identity, create a Member profile for anyone other than yourself (a real person), or use or attempt to use another’s account (such as sharing log-in credentials or copying cookies); Develop, support or use software, devices, scripts, robots or any other means or processes (such as crawlers, browser plugins and add-ons or any other technology) to scrape or copy the Services, including profiles and other data from the Services; Override any security feature or bypass or circumvent any access controls or use limits of the Services (such as search results, profiles, or videos); Copy, use, display or distribute any information (including content) obtained from the Services, whether directly or through third parties (such as search tools or data aggregators or brokers), without the consent of the content owner (such as LinkedIn for content it owns); Disclose information that you do not have the consent to disclose (such as confidential information of others (including your employer); Violate the intellectual property rights of others, including copyrights, patents, trademarks, trade secrets or other proprietary rights. For example, do not copy or distribute (except through the available sharing functionality) the posts or other content of others without their permission, which they may give by posting under a Creative Commons license; Violate the intellectual property or other rights of LinkedIn, including, without limitation, (i) copying or distributing our learning videos or other materials, (ii) copying or distributing our technology, unless it is released under open source licenses; or (iii) using the word “LinkedIn” or our logos in any business name, email, or URL except as provided in the Brand Guidelines ; Post (or otherwise share) anything that contains software viruses, worms, or any other harmful code; Reverse engineer, decompile, disassemble, decipher or otherwise attempt to derive the source code for the Services or any related technology that is not open source; Imply or state that you are affiliated with or endorsed by LinkedIn without our express consent (e.g., representing yourself as an accredited LinkedIn trainer); Rent, lease, loan, trade, sell/re-sell or otherwise monetize the Services or related data or access to the same, without LinkedIn’s consent; Deep-link to our Services for any purpose other than to promote your profile or a Group on our Services, without LinkedIn’s consent; Use bots or other unauthorized automated methods to access the Services, add or download contacts, send or redirect messages, create, comment on, like, share, or re-share posts, or otherwise drive inauthentic engagement; Engage in “framing”, “mirroring”, or otherwise simulating the appearance or function of the Services; Overlay or otherwise modify the Services or their appearance (such as by inserting elements into the Services or removing, covering, or obscuring an advertisement included on the Services); Interfere with the operation of, or place an unreasonable load on, the Services (e.g., spam, denial of service attack, viruses, manipulating algorithms); Violate the Professional Community Policies , certain third party terms where applicable, or any additional terms concerning a specific Service that are provided when you sign up for or start using such Service; Use our Services to do anything that is unlawful, misleading, discriminatory, fraudulent or deceitful (e.g. manipulated media that wrongfully depicts a person saying or doing something they did not say or do); and/or Misuse our reporting or appeals process, including by submitting duplicative, fraudulent or unfounded reports, complaints or appeals. 9. Complaints Regarding Content Contact information for complaints about content provided by our Members. We ask that you report content and other information that you believe violates your rights (including intellectual property rights), our Professional Community Policies or otherwise violates this Contract or the law. To the extent we can under law, we may remove or restrict access to content, features, services, or information, including if we believe that it’s reasonably necessary to avoid harm to LinkedIn or others, violates the law or is reasonably necessary to prevent misuse of our Services. We reserve the right to take action against serious violations of this Contract, including by implementing account restrictions for significant violations. We respect the intellectual property rights of others. We require that information shared by Members be accurate and not in violation of the intellectual property rights or other rights of third parties. We provide a policy and process for complaints concerning content shared, and/or trademarks used, by our Members. 10. How To Contact Us Our Contact information. Our Help Center also provides information about our Services. For general inquiries, you may contact us online . For legal notices or service of process, you may write us at these addresses . LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language | 2026-01-13T08:48:25 |
https://www.facebook.com/policies?ref=pf | Facebook 약관 및 정책 약관 및 정책 회원님이 알아야 하는 내용을 한곳에 모았습니다. 업무 방식 서비스 약관 Facebook 사용 시 동의해야 하는 약관입니다. 개인정보처리방침 저희가 수집하는 정보와 이용 방식입니다. 커뮤니티 규정 금지된 행위와 악용 사례 신고 방법을 확인해보세요. 서비스 약관 개인정보처리방침 Privacy Shield 알림 커뮤니티 규정 정책 더 보기 | 2026-01-13T08:48:25 |
https://socket.io/docs/v4/namespaces/#__docusaurus_skipToContent_fallback | Namespaces | Socket.IO Skip to main content Latest blog post (July 25, 2024): npm package provenance . Socket.IO Docs Guide Tutorial Examples Emit cheatsheet Server API Client API Ecosystem Help Troubleshooting Stack Overflow GitHub Discussions Slack News Blog Twitter Tools CDN Admin UI About FAQ Changelog Roadmap Become a sponsor 4.x 4.x 3.x 2.x Changelog English English Español Français Português (Brasil) 中文（中国） Search Socket.IO Documentation Server Client Events Adapters Advanced Namespaces Custom parser Admin UI Usage with PM2 Load testing Performance tuning Migrations Miscellaneous Advanced Namespaces Version: 4.x On this page Namespaces A Namespace is a communication channel that allows you to split the logic of your application over a single shared connection (also called "multiplexing"). Introduction Each namespace has its own: event handlers io . of ( "/orders" ) . on ( "connection" , ( socket ) => { socket . on ( "order:list" , ( ) => { } ) ; socket . on ( "order:create" , ( ) => { } ) ; } ) ; io . of ( "/users" ) . on ( "connection" , ( socket ) => { socket . on ( "user:list" , ( ) => { } ) ; } ) ; rooms const orderNamespace = io . of ( "/orders" ) ; orderNamespace . on ( "connection" , ( socket ) => { socket . join ( "room1" ) ; orderNamespace . to ( "room1" ) . emit ( "hello" ) ; } ) ; const userNamespace = io . of ( "/users" ) ; userNamespace . on ( "connection" , ( socket ) => { socket . join ( "room1" ) ; // distinct from the room in the "orders" namespace userNamespace . to ( "room1" ) . emit ( "holà" ) ; } ) ; middlewares const orderNamespace = io . of ( "/orders" ) ; orderNamespace . use ( ( socket , next ) => { // ensure the socket has access to the "orders" namespace, and then next ( ) ; } ) ; const userNamespace = io . of ( "/users" ) ; userNamespace . use ( ( socket , next ) => { // ensure the socket has access to the "users" namespace, and then next ( ) ; } ) ; Possible use cases: you want to create a special namespace that only authorized users have access to, so the logic related to those users is separated from the rest of the application const adminNamespace = io . of ( "/admin" ) ; adminNamespace . use ( ( socket , next ) => { // ensure the user has sufficient rights next ( ) ; } ) ; adminNamespace . on ( "connection" , socket => { socket . on ( "delete user" , ( ) => { // ... } ) ; } ) ; your application has multiple tenants so you want to dynamically create one namespace per tenant const workspaces = io . of ( / ^\/\w+$ / ) ; workspaces . on ( "connection" , socket => { const workspace = socket . nsp ; workspace . emit ( "hello" ) ; } ) ; Main namespace Until now, you interacted with the main namespace, called / . The io instance inherits all of its methods: io . on ( "connection" , ( socket ) => { } ) ; io . use ( ( socket , next ) => { next ( ) } ) ; io . emit ( "hello" ) ; // are actually equivalent to io . of ( "/" ) . on ( "connection" , ( socket ) => { } ) ; io . of ( "/" ) . use ( ( socket , next ) => { next ( ) } ) ; io . of ( "/" ) . emit ( "hello" ) ; Some tutorials may also mention io.sockets , it's simply an alias for io.of("/") . io . sockets === io . of ( "/" ) Custom namespaces To set up a custom namespace, you can call the of function on the server-side: const nsp = io . of ( "/my-namespace" ) ; nsp . on ( "connection" , socket => { console . log ( "someone connected" ) ; } ) ; nsp . emit ( "hi" , "everyone!" ) ; Client initialization Same-origin version: const socket = io ( ) ; // or io("/"), the main namespace const orderSocket = io ( "/orders" ) ; // the "orders" namespace const userSocket = io ( "/users" ) ; // the "users" namespace Cross-origin/Node.js version: const socket = io ( "https://example.com" ) ; // or io("https://example.com/"), the main namespace const orderSocket = io ( "https://example.com/orders" ) ; // the "orders" namespace const userSocket = io ( "https://example.com/users" ) ; // the "users" namespace In the example above, only one WebSocket connection will be established, and the packets will automatically be routed to the right namespace. Please note that multiplexing will be disabled in the following cases: multiple creation for the same namespace const socket1 = io ( ) ; const socket2 = io ( ) ; // no multiplexing, two distinct WebSocket connections different domains const socket1 = io ( "https://first.example.com" ) ; const socket2 = io ( "https://second.example.com" ) ; // no multiplexing, two distinct WebSocket connections usage of the forceNew option const socket1 = io ( ) ; const socket2 = io ( "/admin" , { forceNew : true } ) ; // no multiplexing, two distinct WebSocket connections Dynamic namespaces It is also possible to dynamically create namespaces, either with a regular expression: io . of ( / ^\/dynamic-\d+$ / ) ; or with a function: io . of ( ( name , auth , next ) => { next ( null , true ) ; // or false, when the creation is denied } ) ; You can have access to the new namespace in the connection event: io . of ( / ^\/dynamic-\d+$ / ) . on ( "connection" , ( socket ) => { const namespace = socket . nsp ; } ) ; The return value of the of() method is what we call the parent namespace, from which you can: register middlewares const parentNamespace = io . of ( / ^\/dynamic-\d+$ / ) ; parentNamespace . use ( ( socket , next ) => { next ( ) } ) ; The middleware will automatically be registered on each child namespace. broadcast events const parentNamespace = io . of ( / ^\/dynamic-\d+$ / ) ; parentNamespace . emit ( "hello" ) ; // will be sent to users in /dynamic-1, /dynamic-2, ... caution Existing namespaces have priority over dynamic namespaces. For example: // register "dynamic-101" namespace io . of ( "/dynamic-101" ) ; io . of ( / ^\/dynamic-\d+$ / ) . on ( "connection" , ( socket ) => { // will not be called for a connection on the "dynamic-101" namespace } ) ; Complete API The complete API exposed by the Namespace instance can be found here . Edit this page Last updated on Nov 15, 2025 Previous Azure Service Bus adapter Next Custom parser Introduction Main namespace Custom namespaces Client initialization Dynamic namespaces Complete API Documentation Guide Tutorial Examples Server API Client API Help Troubleshooting Stack Overflow GitHub Discussions Slack News Blog Twitter Tools CDN Admin UI About FAQ Changelog Roadmap Become a sponsor Copyright © 2026 Socket.IO | 2026-01-13T08:48:25 |
https://twitter.com/latestFromTV?ref_src=twsrc%5Etfw | JavaScript is not available. We’ve detected that JavaScript is disabled in this browser. Please enable JavaScript or switch to a supported browser to continue using x.com. You can see a list of supported browsers in our Help Center. Help Center Terms of Service Privacy Policy Cookie Policy Imprint Ads info © 2026 X Corp. Something went wrong, but don’t fret — let’s give it another shot. Try again Some privacy related extensions may cause issues on x.com. Please disable them and try again. | 2026-01-13T08:48:25 |
https://docs.devcycle.com/sdk/server-side-sdks/node/node-openfeature | Node.js OpenFeature Provider | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up SDK Overview SDK Lifecycle SDK Features Client-side SDKS Server-side SDKS Node.js SDK Installation Getting Started Usage OpenFeature Typescript Bootstrapping / SSR Example App NestJS SDK PHP SDK Go SDK Ruby SDK Python SDK Java SDK .NET SDK SDK Proxy Server-side SDKS Node.js SDK OpenFeature On this page OpenFeature Provider AI-Powered Install MCP Install Follow the MCP Getting Started guide to quickly set up the DevCycle MCP server and connect your AI tool. Run this prompt: "Install DevCycle into this app" 📦 Install in Cursor 📦 Install in VS Code claude mcp add --transport http devcycle https://mcp.devcycle.com/mcp AI Prompt Copy Prompt OpenFeature is an open standard that provides a vendor-agnostic, community-driven API for feature flagging that works with DevCycle. DevCycle provides a NodeJS implementation of the OpenFeature Provider interface directly from the SDK using the DevCycleProvider class. Usage Installation Install the DevCycle NodeJS Server SDK which includes the OpenFeature Server SDK as a dependency NPM npm install --save @devcycle/nodejs-server-sdk Yarn yarn add @devcycle/nodejs-server-sdk Getting Started Create the DevCycleProvider and set it as the provider for OpenFeature: import { OpenFeature , Client } from '@openfeature/server-sdk' import { DevCycleProvider } from '@devcycle/nodejs-server-sdk' const { DEVCYCLE_SERVER_SDK_KEY } = process . env ... // Create the DevCycleProvider const devcycleProvider = new DevCycleProvider ( DEVCYCLE_SERVER_SDK_KEY ) // Set the provider for OpenFeature await OpenFeature . setProviderAndWait ( devcycleProvider ) // Create the OpenFeature client openFeatureClient = OpenFeature . getClient ( ) Evaluate a Variable Use a Variable value by creating the EvaluationContext, then passing the Variable key, default value, and EvaluationContext to one of the OpenFeature flag evaluation methods. // Set the context for the OpenFeature client, you can use 'targetingKey' or 'user_id' const context = { targetingKey : 'node_sdk_test' } // Retrieve a boolean flag from the OpenFeature client const boolFlag = await openFeatureClient . getBooleanValue ( 'boolean-flag' , false , context , ) Tracking Events You can use the OpenFeature track method to track events which will be sent to DevCycle as custom events. Calling track will queue the event, which will be sent in batches to the DevCycle servers. const context = { targetingKey : 'node_sdk_test' } openFeatureClient . track ( 'custom-event' , context , { target : 'event-target' , value : 100 , metaDataField : 'value' , } ) To track custom events with OpenFeature you are required to set the first argument as the event name, and pass the EvaluationContext as the second argument. The event name will be used as the event's type in DevCycle, and you can optionally set a value / target / date as defined in the DevCycleEvent Typescript Schema . Any additional properties will be added to the event as metaData fields. Passing DevCycleOptions to the DevCycleProvider Ensure that you pass any custom DevCycleOptions set on the DevCycleClient instance to the DevCycleProvider constructor const options = { logger : dvcDefaultLogger ( { level : 'debug' } ) } const devcycleProvider = new DevCycleProvider ( DEVCYCLE_SERVER_SDK_KEY , options ) await OpenFeature . setProviderAndWait ( devcycleProvider ) Accessing the DevCycleClient If you need to access the underlying DevCycleClient from the provider, it is exposed using provider.devcycleClient : const devcycleProvider = new DevCycleProvider ( DEVCYCLE_SERVER_SDK_KEY ) await OpenFeature . setProviderAndWait ( devcycleProvider ) ... const allFeatures = devcycleProvider . devcycleClient . allFeatures ( dvcUser ) Required TargetingKey For DevCycle SDK to work we require either a targetingKey or user_id to be set on the OpenFeature context. This is used to identify the user as the user_id for a DevCycleUser in DevCycle. Context properties to DevCycleUser The provider will automatically translate known DevCycleUser properties from the OpenFeature context to the DevCycleUser object. DevCycleUser TypeScript Interface For example all these properties will be set on the DevCycleUser : openFeatureClient . setContext ( { user_id : 'user_id' , email : ' [email protected] ' , name : 'name' , language : 'en' , country : 'CA' , appVersion : '1.0.11' , appBuild : 1000 , customData : { custom : 'data' } , privateCustomData : { private : 'data' } , } ) Context properties that are not known DevCycleUser properties will be automatically added to the customData property of the DevCycleUser . Context Limitations DevCycle only supports flat JSON Object properties used in the Context. Non-flat properties will be ignored. For example obj will be ignored: openFeatureClient . setContext ( { user_id : 'user_id' , obj : { key : 'value' } , } ) JSON Flag Limitations The OpenFeature spec for JSON flags allows for any type of valid JSON value to be set as the flag value. For example the following are all valid default value types to use with OpenFeature: // Invalid JSON values for the DevCycle SDK, will return defaults openFeatureClient . getObjectValue ( 'json-flag' , [ 'arry' ] ) openFeatureClient . getObjectValue ( 'json-flag' , 610 ) openFeatureClient . getObjectValue ( 'json-flag' , false ) openFeatureClient . getObjectValue ( 'json-flag' , 'string' ) openFeatureClient . getObjectValue ( 'json-flag' , null ) However, these are not valid types for the DevCycle SDK, the DevCycle SDK only supports JSON Objects: // Valid JSON Object as the default value, will be evaluated by the DevCycle SDK openFeatureClient . getObjectValue ( 'json-flag' , { default : 'value' } ) Edit this page Last updated on Jan 9, 2026 Previous Usage Next Typescript AI-Powered Install Usage Installation Getting Started Evaluate a Variable Tracking Events Passing DevCycleOptions to the DevCycleProvider Accessing the DevCycleClient Required TargetingKey Context properties to DevCycleUser Context Limitations JSON Flag Limitations DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:25 |
https://www.linkedin.com/posts/activity-7415021972293881856-uK9F | SuprSend Supports Schema-Driven Type Generation for Workflow Triggers | SuprSend posted on the topic | LinkedIn Agree & Join LinkedIn By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Skip to main content LinkedIn Top Content People Learning Jobs Games Sign in Join now SuprSend Supports Schema-Driven Type Generation for Workflow Triggers This title was summarized by AI from the post below. SuprSend 19,129 followers 4d Report this post 𝗧𝘆𝗽𝗲-𝘀𝗮𝗳𝗲 𝘄𝗼𝗿𝗸𝗳𝗹𝗼𝘄 𝘁𝗿𝗶𝗴𝗴𝗲𝗿𝘀 𝗶𝗻 𝗦𝘂𝗽𝗿𝗦𝗲𝗻𝗱 🧩 Triggering workflows with loosely typed payloads often leads to bugs that only show up at runtime. To reduce that risk, SuprSend now supports schema-driven type generation for workflow triggers. You define the payload structure once as a JSON schema in SuprSend. From there, the CLI generates strongly-typed interfaces that you can use directly in your application code. What this improves: • Catch invalid payloads during development instead of production • Get IDE autocomplete and immediate feedback while coding • Keep workflow payloads consistent as schemas evolve • Avoid manually maintaining type definitions Type generation is available for 𝗧𝘆𝗽𝗲𝗦𝗰𝗿𝗶𝗽𝘁, 𝗣𝘆𝘁𝗵𝗼𝗻, 𝗚𝗼, 𝗝𝗮𝘃𝗮, 𝗞𝗼𝘁𝗹𝗶𝗻, 𝗦𝘄𝗶𝗳𝘁, 𝗮𝗻𝗱 𝗗𝗮𝗿𝘁. Docs in the comments. 7 1 Comment Like Comment Share Copy LinkedIn Facebook X SuprSend 4d Report this comment https://docs.suprsend.com/docs/type-generation Like Reply 1 Reaction To view or add a comment, sign in More Relevant Posts Marcus Neufeldt 3w Report this post The most powerful automation stack isn't "No-Code" or "Code." It's both. I use n8n and Make often. They're excellent for observability, the whole team can see exactly how data flows. But for the build phase? I prefer the raw leverage of code. The video below shows a tool I built this afternoon. I actually built something similar in early 2025 .. way before n8n workflow posts became LinkedIn engagement bait. Here's the problem: LLMs can generate basic n8n workflows, but they hallucinate nodes constantly. It's hit or miss whether you get something that actually runs. My fix: pull all native n8n nodes into a vector database, feed only the relevant ones to the LLM, validate the output. Done. Prompt in. Production-ready JSON out. Python handles the complexity. n8n handles the execution. This solves the biggest bottleneck in automation: manual friction. Dragging boxes one by one is slow. Generating architecture with code is instant. …more 1 Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Hema Thapa 6d Report this post Refactoring is 50% logic, 50% labeling. 🏷️ Most "complex" bugs don't start with bad logic—they start with unclear naming. If your function is named processData(), you’re forcing the next developer to read every line of your code just to understand its intent. Think of your code like a spice rack: Without labels, Red Chilli powder and Kashmiri Mirch look identical. One wrong guess, and the entire "dish" is ruined. Stop "Handling" and start "Defining": ❌ The "Mystery" Names: processData() handleRequest() ✅ The "Clean Code" Names: calculateTotalAmount() validateUserCredentials() The Professional Standard: Naming isn't just a "soft skill"—it’s a tool for reducing mental strain. Refactoring Tip: Sometimes the most high-impact PR you can submit isn't a logic rewrite. It’s hitting "rename option" to rename a variable until the code reads like a story, not a puzzle. The Goal: Clear naming doesn't just make code "pretty"—it makes it safe. What’s one "mystery" function name you’ve encountered (or written!) recently? 👇 #CleanCode #SoftwareEngineering #Refactoring #ProgrammingTips View C2PA information 13 Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Julius Haas 3w Report this post Cursor launched a Debug Mode to help you actually debug bugs. Hopefully this will end the endless back-and-forth of: “Please make sure not to repeat this error XY” and “Yes, Julius. You’re right” 😅 It works by forming multiple hypotheses, instrumenting your code with runtime logs, and walking you through reproducing and verifying the fix with real execution data. Read more: https://lnkd.in/gpKRWWVK Introducing Debug Mode: Agents with runtime logs cursor.com 9 1 Comment Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Yaki Aslan 1w Report this post TL;DR: I built a tool to test Rive files at runtime. It lets you poke at state machines and data bindings to see how they'll actually behave in an app before you start coding. Rive At Singit I spend a lot of time implementing Rive files in the product, and I kept hitting the same wall: things work fine in the editor, but then they get weird at runtime. It’s usually state machines or data bindings behaving unexpectedly or events/inputs not firing when they should. I looked for something online to help with this, but the apps I found felt pretty limited or just weren't comfortable to use for actual debugging. I ended up building a little tool to help me debug this stuff, and I figured I’d share it here in case anyone else finds it useful. Basically, it’s a tool where you can load a .riv file and just poke at it before you actually start writing any implementation code. What you can do with it: -Upload and test multiple .riv files at once -Switch between multiple artboards in the same file -Inspect and control state machines and inputs -Trigger events and transitions manually -Explore data bindings and runtime values -View real time Events and their properties -Test complex files -Reset runtime state to reproduce edge cases -Generate code snippets -Summaries files for handoff -Experiment safely before shipping to production I’ve been using this tool to review files from other designers and to generate snippets when ready to hand things off to engineering. It’s not meant to replace the editor or anything like that, it just helps bridge the gap between the design and the final app. It’s still pretty early, but it has saved me a lot of back-and-forth. If you’re working with Rive and want to test your files before you ship them, feel free to give it a try. [ https://www.rivelab.app/ ] (Just a disclaimer: I’m not affiliated with the Rive team, I just use their stuff a lot.) …more 34 13 Comments Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Vijaykumar Singh 1w Report this post Victor v0.3.0 is out — and it’s our most important release of 2025. After a year of iterating, learning, and refactoring in the open, this release finally delivers what we set out to prove: AI agents don’t have to become architectural monoliths as they scale. What shipped: Imports reduced 68 → <20 (71% ↓) Protocol-first architecture end to end 5 verticals fully decoupled 14K+ TDD - 100% passing ✅ The real win? Adding new AI agent capabilities no longer requires touching core framework code. That’s a huge unlock — and a strong way to close out 2025: cleaner boundaries, faster iteration, and architecture that won’t fight us next year. This is what sustainable AI agent architecture looks like. 🔗 Full release notes: https://lnkd.in/ggsWZ38v #AIAgents #SoftwareArchitecture #OpenSource #AIEngineering #Python Release Victor v0.3.0 - Domain-Framework Decoupling Release · vjsingh1984/victor github.com 5 Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Gianpiero Massa Tofo 2w Edited Report this post Never felt this much behind as a programmer — Andrej Karpathy. I've never felt this much behind as a programmer. The profession is being dramatically refactored as the bits contributed by the programmer are increasingly sparse and between. I have a sense that I could be 10X more powerful if I just properly string together what has become available over the last ~year and a failure to claim the boost feels decidedly like skill issue. There's a new programmable layer of abstraction to master (in addition to the usual layers below) involving agents, subagents, their prompts, contexts, memory, modes, permissions, tools, plugins, skills, hooks, MCP, LSP, slash commands, workflows, IDE integrations, and a need to build an all-encompassing mental model for strengths and pitfalls of fundamentally stochastic, fallible, unintelligible and changing entities suddenly intermingled with what used to be good old fashioned engineering. Clearly some powerful alien tool was handed around except it comes with no manual and everyone has to figure out how to hold it and operate it, while the resulting magnitude 9 earthquake is rocking the profession. Roll up your sleeves to not fall behind. — We just really just added the line jumps, for readability. — Skin in the game with Paolo Massa Tofo 4 1 Comment Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Venkatakumar Chembati 4d Report this post “Programs must be written for people to read, and only incidentally for machines to execute.” – Harold Abelson We focus so much on getting the code to work that we forget to make it readable. Clean code is about clarity, maintainability, and respect for the next developer who reads your work (which might just be future you). 𝗕𝗮𝗱 𝗖𝗼𝗱𝗲: public void d(int a, int b){ int x = a + b; if(x > 10){ System.out.println ("OK"); } } This code technically works, However it tells nothing about what is "a" and "b" and why it is being done. This makes the developers hard to read and often takes much time in debugging. 𝗖𝗹𝗲𝗮𝗻 𝗖𝗼𝗱𝗲: public void notifyIfAboveThreshold(int currentValue, int threshold){ int total = currentValue + threshold; if (total > MAX_THRESHOLD_VALUE) { System.out.println ("Threshold reached! Taking action..."); } } Now the method name, parameter names and the logic describe the purpose clearly. Anyone reading it immediately understands what it does. Write code that speaks clearly, not cryptically. Code for humans first — machines will always understand. 8 Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Ravi Kiran 6d Report this post "CLI coding agent" undersells it. Claude Code. Codex CLI. Gemini CLI. They're not just code tools. They're terminal-native general-purpose agents. → Filesystem access → Command execution → Agentic planning → Tool orchestration Useful for ANY workflow that needs automation + reasoning. Calling them "coding" tools is like calling a Swiss Army knife a "blade." If you're only using them to write code, you're leaving 70% on the table. 8 Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Sudhanshu Sharma ✨ 2w Edited Report this post Bring intelligent automation to your Claude Code workflows, without the token bloat. Claude code plugins, a comprehensive system that lets Claude Code build, orchestrate and automate faster ⚡ Free and open-source! → 99 specialized AI agents → 15 multi-agent orchestrators → 107 specialized skills + 71 dev tools → Granular plugins for minimal token usage Some great use cases: #1 - I want full-stack features automated → orchestrate 7+ agents for complex development, like user authentication with OAuth2. #2 - I need robust security → multi-agent security assessment with SAST, dependency scanning, and AI-powered code review. #3 - I'm building with Python → scaffold production-ready FastAPI projects with async patterns, activating specialized skills for testing and package management. #4 - I need to optimize model costs → leverage the three-tier model strategy (Opus → Sonnet → Haiku) for optimal performance and efficiency. Check out the free, open-source repo: → https://lnkd.in/dxAZeuec ---- ♻️ If this was useful, repost it so others can benefit too. Follow me for more post like this 32 Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Saisreeram Kakaraparthi 1w Report this post A small .ToList() taught me a performance lesson today. While solving a problem, I initially wrote this: if (nums.Distinct().ToList().Count != nums.Length) return true; It worked, but the runtime was 18ms. Later, I changed it slightly: if (nums.Distinct().Count() != nums.Length) return true; Same logic. Runtime dropped to 13ms. That small change made me stop and think. What was really happening? LINQ follows deferred execution. LINQ doesn’t execute anything immediately. It just builds a query. In my first version: • Distinct() built the query • .ToList() forced execution immediately • The entire sequence was iterated • A new list was created in memory • Then Count was read from that list In the second version: • Distinct() still didn’t run immediately • Count() triggered execution • The sequence was iterated once • No intermediate list, no extra allocation A simple reminder for me: • LINQ is lazy by default • ToList() is not free • Small choices affect performance Next time I write ToList(), I’ll pause and think about what’s happening under the hood. #CSharp #DotNet #LINQ #PerformanceMatters #LearningInPublic #SoftwareEngineering 9 2 Comments Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in 19,129 followers View Profile Connect Explore content categories Career Productivity Finance Soft Skills & Emotional Intelligence Project Management Education Technology Leadership Ecommerce User Experience Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language Sign in to view more content Create your free account or sign in to continue your search Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . | 2026-01-13T08:48:25 |
https://www.linkedin.com/products/categories/push-notification-software?trk=organization_guest_main_product_card_category_link | Best Push Notification Software | Products | LinkedIn Skip to main content LinkedIn Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Clear text Used by Used by Marketing Manager (4) Software Engineer (4) Office Manager (3) Chief Marketing Officer (3) Finance Specialist (2) See all products Find top products in Push Notification Software category Software used to send messages directly from a server to a user's computer or mobile device. - Send messages through desktop applications, mobile apps, or the web browser - Notify at any time after opt-in, regardless of whether applications are in use or recently visited - Personalize reminders, offers, and updates based on users' needs, preferences, and activity - Measure accuracy and effectiveness with click-through rates, conversions, and other metrics 104 results SuprSend Push Notification Software by SuprSend SuprSend is a notification infrastructure as a service platform for easily creating, managing, and delivering notifications to your end users. SuprSend has all the features set which enable you to send notifications in a reliable and scalable manner, as well as take care of end-user experience, thereby eliminating the need to build any notification service in-house. Benefits of using SuprSend as your notification stack are that: * You do not have to do any vendor integrations for channels in your code. You can easily add/remove/prioritize vendors and channels from your SuprSend account, * You can design powerful templates for all channels together and manage them from a single place, * You can leverage powerful features to experiment fast with notifications and take care of end-user experience without writing a single line of code. View product MAS Push Notification Software by Protecmedia The editorial push notifications and analytics system. The push notification and analytics solution for a better understanding of your audience: Get the RFV reader profile score and follow every content performance by author, topic or section. Track your objectives and the use of adblockers. View product Batch Push Notification Software by Batch The Batch platform is known and loved by over 400 clients worldwide, helping modern marketing teams easily set up profitable omnichannel customer engagement strategies (with an average ROI of 600%). These strategies include:
- A single customer view and a powerful data model so you can collect and centralise customer insights in real time,
- A simple marketing automation platform to handle all your workflows and campaigns in a matter of minutes,
- Complementary centralised channels (app push notifications, in-app messaging, web push notifications, emails) that deliver just the right message to the right segment. View product PUSH Push Notification Software by edna 𝗣𝘂𝘀𝗵 𝗻𝗼𝘁𝗶𝗳𝗶𝗰𝗮𝘁𝗶𝗼𝗻𝘀 provide a direct path for businesses to reach their clients with information that is valuable for them. They help to increase app usage and provide greater customer engagement through timely, customized messaging. They can be used to send transactional and behavior-based alerts, reminders and retention-based messages, promotional offers, as well as location-based messages. 𝗥𝗶𝗰𝗵 𝗽𝘂𝘀𝗵: edna’s rich push capabilities enable clients to get really creative with their messages by adding images, buttons, emojis, gifs, etc. 𝗚𝗲𝗼-𝘁𝗮𝗿𝗴𝗲𝘁𝗶𝗻𝗴: The customer’s real-time location data can be leveraged to share exclusive offers for shoppers in the vicinity of a showroom, and also to share helpful travel-based information. 𝗗𝗲𝗲𝗽 𝗹𝗶𝗻𝗸𝗶𝗻𝗴: Deep links help to minimize customer efforts by leading them directly to a specific page on the app. View product Netmera Push Notification Software by Netmera With Netmera mobile marketing automation you can understand user behaviour and act on it in real time, no opportunities missed. View product Find products trusted by professionals in your network See which products are used by connections in your network and those that share similar job titles Sign in to view full insights MantraNet - Suas consultas ao Siscomex Mantra com mais rapidez e praticidade Push Notification Software by e.Mix MantraNet is a system that streamlines queries to Siscomex Mantra based on automation and alerts related to the steps that occur during the air transport of cargo, tracking aircrafts from the airport of origin to the airport of arrival. With MantraNet it is also possible to automate queries to obtain information on road and maritime imports. View product PushOwl Push Notification Software by PushOwl PushOwl is an Omnichannel marketing app built exclusively for Shopify stores, combining Email, SMS & Push notifications to help merchants recover lost sales and grow revenue. - Consumption-based pricing: Pay only for what you use, with strong ROI - Abandoned cart recovery: Automated reminders to recover lost sales - Back-in-stock & price drop alerts: Notify customers when products return or prices change - Personalized segmentation: Target campaigns based on customer behavior and preferences - Unlimited subscribers: Grow your list with no caps, even on the free plan - Easy Shopify integration: Set up campaigns quickly with no coding required - Advanced automation: Automate workflows for orders, shipping, and promotions - Real-time analytics: Track campaign performance and optimize strategies - 24/7 support: Dedicated team for fast troubleshooting and guidance View product Alertas y notificaciones inteligentes en Whatsapp Push Notification Software by Jelou AI Programa cualquier experiencia digital diseñando y entrenando con Inteligencia Artificial. Envía recomendaciones y notificaciones programadas en base al comportamiento de tus usuarios. View product Notix Push Notification Software by AdTech Holding A leading push notification service for websites and apps with unbeatable user subscription and delivery rates: 30% higher compared to similar services. View product iZooto Web Push Notifications Push Notification Software by iZooto Reduce dependency on Google and Facebook with Web push notifications. With Google’s constant updates and Facebook’s algorithm changes, it has become tiresome to reach and engage with an audience. Engaging with users has been tricky as you do not own an audience. Web push notifications is a permission-based marketing channel, that lets you build and own the audience. Push notifications work across devices and are delivered on browsers in real-time, even when your users are not on your site. Power your editorial team to send breaking news and retarget them to your website. iZooto not only helps in increase engagements but also lets publishers monetize their audience - Not just with ads but also with subscriptions. “After using iZooto for several days, it made me think that this could be the replacement for the lost traffic from Facebook. Currently, iZooto increases my traffic by more than 20% every month.” - Jomar, CEO @ PhilNews View product See more How it works Explore Discover the best product for your need from a growing catalog of 25,000 products and categories trusted by LinkedIn professionals Learn Evaluate new tools, explore trending products in your industry and see who in your network is skilled in the product Grow Join communities of product users to learn best practices, celebrate your progress and accelerate your career LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English Language | 2026-01-13T08:48:25 |
https://www.linkedin.com/checkpoint/lg/login?session_redirect=https%3A%2F%2Fwww%2Elinkedin%2Ecom%2FshareArticle%3Fmini%3Dtrue%26url%3Dhttps%253A%252F%252Fdev%2Eto%252Fcodebunny20%252Flooking-for-help-if-possible-im-stuck-on-my-trackmyhrt-app-medication-symptom-tracker-38fa%26title%3D%25F0%259F%258C%2588%2520Looking%2520for%2520help%2520if%2520possible%253A%2520I%25E2%2580%2599m%2520Stuck%2520on%2520My%2520TrackMyHRT%2520App%2520%2528Medication%2520%252B%2520Symptom%2520Tracker%2529%26summary%3DHey%2520devs%2520%25E2%2580%2594%2520I%25E2%2580%2599m%2520working%2520on%2520a%2520small%252C%2520offline%252C%2520privacy%25E2%2580%2591first%2520desktop%2520app%2520called%2520TrackMyHRT%252C%2520and%2520I%25E2%2580%2599ve%2520hit%2E%2E%2E%26source%3DDEV%2520Community&fromSignIn=true&trk=hb_signin | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T08:48:25 |
https://www.linkedin.com/company/suprsend/#main-content | SuprSend | LinkedIn Skip to main content LinkedIn Top Content People Learning Jobs Games Sign in Join now for free SuprSend Software Development San Francisco, CA 19,129 followers Communication Infrastructure for dev & product teams See jobs Follow View all 17 employees Report this company About us SuprSend is a central communication stack for easily creating, managing and delivering notifications to your end users on multiple channels. Our single notification API has all the features set, which enables you to send notifications in a reliable and scalable manner and take care of end user experience, thereby eliminating the need to develop any notification service in-house for transactional/engagement notifications. Website https://www.suprsend.com/ External link for SuprSend Industry Software Development Company size 11-50 employees Headquarters San Francisco, CA Type Privately Held Founded 2021 Specialties notifications, android push, ios push, email, sms, whatsapp, slack, Microsoft teams, Telegram, App Inbox, A/B Experiments, web push, RCS, preferences management, batching & digests, notification infrastructure, twilio, template builder, inapp inbox, and react sdk Products SuprSend SuprSend Push Notification Software SuprSend is a notification infrastructure as a service platform for easily creating, managing, and delivering notifications to your end users. SuprSend has all the features set which enable you to send notifications in a reliable and scalable manner, as well as take care of end-user experience, thereby eliminating the need to build any notification service in-house. Benefits of using SuprSend as your notification stack are that: * You do not have to do any vendor integrations for channels in your code. You can easily add/remove/prioritize vendors and channels from your SuprSend account, * You can design powerful templates for all channels together and manage them from a single place, * You can leverage powerful features to experiment fast with notifications and take care of end-user experience without writing a single line of code. Locations Primary San Francisco, CA 94104, US Get directions Bengaluru, KA 560102, IN Get directions Employees at SuprSend Deepak Deolalikar Samuel Sunderaraj Gaurav Verma Sathya Nellore Sampat See all employees Updates SuprSend reposted this SuprSend 19,129 followers 4d Report this post 𝗧𝘆𝗽𝗲-𝘀𝗮𝗳𝗲 𝘄𝗼𝗿𝗸𝗳𝗹𝗼𝘄 𝘁𝗿𝗶𝗴𝗴𝗲𝗿𝘀 𝗶𝗻 𝗦𝘂𝗽𝗿𝗦𝗲𝗻𝗱 🧩 Triggering workflows with loosely typed payloads often leads to bugs that only show up at runtime. To reduce that risk, SuprSend now supports schema-driven type generation for workflow triggers. You define the payload structure once as a JSON schema in SuprSend. From there, the CLI generates strongly-typed interfaces that you can use directly in your application code. What this improves: • Catch invalid payloads during development instead of production • Get IDE autocomplete and immediate feedback while coding • Keep workflow payloads consistent as schemas evolve • Avoid manually maintaining type definitions Type generation is available for 𝗧𝘆𝗽𝗲𝗦𝗰𝗿𝗶𝗽𝘁, 𝗣𝘆𝘁𝗵𝗼𝗻, 𝗚𝗼, 𝗝𝗮𝘃𝗮, 𝗞𝗼𝘁𝗹𝗶𝗻, 𝗦𝘄𝗶𝗳𝘁, 𝗮𝗻𝗱 𝗗𝗮𝗿𝘁. Docs in the comments. 7 1 Comment Like Comment Share SuprSend 19,129 followers 4d Report this post 𝗧𝘆𝗽𝗲-𝘀𝗮𝗳𝗲 𝘄𝗼𝗿𝗸𝗳𝗹𝗼𝘄 𝘁𝗿𝗶𝗴𝗴𝗲𝗿𝘀 𝗶𝗻 𝗦𝘂𝗽𝗿𝗦𝗲𝗻𝗱 🧩 Triggering workflows with loosely typed payloads often leads to bugs that only show up at runtime. To reduce that risk, SuprSend now supports schema-driven type generation for workflow triggers. You define the payload structure once as a JSON schema in SuprSend. From there, the CLI generates strongly-typed interfaces that you can use directly in your application code. What this improves: • Catch invalid payloads during development instead of production • Get IDE autocomplete and immediate feedback while coding • Keep workflow payloads consistent as schemas evolve • Avoid manually maintaining type definitions Type generation is available for 𝗧𝘆𝗽𝗲𝗦𝗰𝗿𝗶𝗽𝘁, 𝗣𝘆𝘁𝗵𝗼𝗻, 𝗚𝗼, 𝗝𝗮𝘃𝗮, 𝗞𝗼𝘁𝗹𝗶𝗻, 𝗦𝘄𝗶𝗳𝘁, 𝗮𝗻𝗱 𝗗𝗮𝗿𝘁. Docs in the comments. 7 1 Comment Like Comment Share SuprSend 19,129 followers 2w Report this post [𝗟𝗜𝗩𝗘] 𝗛𝗼𝘀𝘁𝗲𝗱 𝗣𝗿𝗲𝗳𝗲𝗿𝗲𝗻𝗰𝗲 𝗣𝗮𝗴𝗲: 𝗥𝗲𝗮𝗱𝘆-𝘁𝗼-𝘂𝘀𝗲 𝘂𝘀𝗲𝗿 𝘀𝗲𝘁𝘁𝗶𝗻𝗴𝘀 🌍 SuprSend now gives you a ready-made Preference Page where users can manage how they receive notifications. Just link to it from your emails or SMS — no need to build or maintain your own preference system. It’s designed to help you stay compliant while giving users better control over their communication. We’ve now added full localization support so these pages work seamlessly for global audiences. What’s new: • Pages adapt automatically to the user’s locale • Category names, descriptions, and sections are rendered dynamically • Static page text is localized • Smart fallback when a regional language isn’t available If you’re sending notifications across regions, this makes preference management clearer for users and easier to scale for teams. Preview link in the comments. 5 Like Comment Share SuprSend 19,129 followers 3w Edited Report this post 𝗘𝘅𝗽𝗼𝗿𝘁 𝗡𝗼𝘁𝗶𝗳𝗶𝗰𝗮𝘁𝗶𝗼𝗻𝘀 𝗗𝗮𝘁𝗮 𝘁𝗼 𝗔𝗺𝗮𝘇𝗼𝗻 𝗦𝟯 🚀 Now you can fully own and control your notifications data within your S3 bucket — create custom dashboards, debug delivery issues, or maintain audit trails for compliance. 𝗪𝗵𝗮𝘁'𝘀 𝗶𝗻𝗰𝗹𝘂𝗱𝗲𝗱: • Syncs every 5 minutes in encrypted Parquet files • Messages, Workflow Executions, and Requests • Automatic backfills and hourly partitions • Works natively with Athena, Snowflake, BigQuery, Redshift Confidently build dashboards, surface notification logs to customers, or track entire customer lifecycle end-to-end. Docs in comments 👇 9 1 Comment Like Comment Share SuprSend 19,129 followers 1mo Report this post We're #hiring a new UI / UX Designer in Bengaluru, Karnataka. Apply today or share this post with your network. UI / UX Designer SuprSend, Bengaluru, Karnataka, India 7 Like Comment Share SuprSend 19,129 followers 1mo Edited Report this post 𝗖𝗮𝘁𝗲𝗴𝗼𝗿𝘆 𝗧𝗿𝗮𝗻𝘀𝗹𝗮𝘁𝗶𝗼𝗻𝘀 𝗳𝗼𝗿 𝗣𝗿𝗲𝗳𝗲𝗿𝗲𝗻𝗰𝗲 𝗖𝗲𝗻𝘁𝗲𝗿𝘀 🌍 In pursuit of seamless translations: preference categories now display in your user's locale. 𝗪𝗵𝗮𝘁 𝘁𝗵𝗶𝘀 𝗺𝗲𝗮𝗻𝘀: • One preference center works globally (no separate versions for each region) • Users make informed choices when they see categories in their preferred language • Add translations through Dashboard, API, or CLI • Smart fallback logic ensures something always displays (es-mx → es → en) If you're shipping notifications to a multilingual audience, this removes friction for both your users and your team. Docs in comments below 👇 13 1 Comment Like Comment Share SuprSend 19,129 followers 1mo Report this post 𝗛𝗼𝘄 𝗖𝗿𝗮𝘇𝘆𝗚𝗮𝗺𝗲𝘀 𝗖𝘂𝘁 𝗡𝗼𝘁𝗶𝗳𝗶𝗰𝗮𝘁𝗶𝗼𝗻 𝗗𝗲𝗽𝗹𝗼𝘆𝗺𝗲𝗻𝘁 𝗳𝗿𝗼𝗺 𝗪𝗲𝗲𝗸𝘀 𝘁𝗼 𝗛𝗼𝘂𝗿𝘀 CrazyGames serves 45M+ monthly players across 3,000+ browser games. But their in-house notification system held them back. 🎮 𝗧𝗵𝗲 𝗽𝗿𝗼𝗯𝗹𝗲𝗺: Building notifications required heavy engineering involvement. Even small template changes meant creating dev tickets and took 2 weeks to deploy. Product teams couldn't personalize or experiment fast without developer time. 𝗪𝗵𝗮𝘁 𝗰𝗵𝗮𝗻𝗴𝗲𝗱: CrazyGames adopted SuprSend to abstract notification development out of code. Templates, logic, and workflows shifted entirely to Product & Design. They also connected their database to SuprSend, allowing teams to create targeted cohorts by writing SQL — no data exports, no syncing delays, no engineering bottlenecks. 𝗧𝗵𝗲 𝗿𝗲𝘀𝘂𝗹𝘁: • Notification launches: weeks → hours • Self-serve campaigns with personalized game recommendations • A/B testing across email, push, and in-app — all unified • Product teams operate independently 🎥 Watch Jonas (VP of Product, CrazyGames) full story link in comments below. 33 4 Comments Like Comment Share SuprSend 19,129 followers 1mo Report this post We're #hiring a new Founders’ Office – Product Marketing in Bengaluru, Karnataka. Apply today or share this post with your network. Product Marketing Manager SuprSend, Bengaluru, Karnataka, India 9 1 Comment Like Comment Share SuprSend 19,129 followers 1mo Edited Report this post 𝗜𝗻𝘁𝗿𝗼𝗱𝘂𝗰𝗶𝗻𝗴 𝗧𝗿𝗮𝗻𝘀𝗹𝗮𝘁𝗶𝗼𝗻𝘀 𝗶𝗻 𝗡𝗼𝘁𝗶𝗳𝗶𝗰𝗮𝘁𝗶𝗼𝗻𝘀 Maintaining separate notification templates for every language doesn't scale. Change one template and you update all language versions manually. Translations solve this. Write one template that works across all languages. SuprSend automatically serves the right language based on user locale, with intelligent fallbacks. What's included: • Upload existing JSON translation files & manage through CLI/API • Smart translation keys with automatic language selection • Dynamic variables and pluralization handling • Namespaced keys to organize by feature • Change history with rollback support Documentation in the comments 👇 13 4 Comments Like Comment Share SuprSend 19,129 followers 1mo Report this post We're #hiring a new Product Manager in Bengaluru, Karnataka. Apply today or share this post with your network. Product Manager SuprSend, Bengaluru, Karnataka, India 4 Like Comment Share Join now to see what you are missing Find people you know at SuprSend Browse recommended jobs for you View all updates, news, and articles Join now Similar pages SuperSend Software Development Las Vegas, Nevada Crew Technology, Information and Internet Keploy 🐰 Technology, Information and Internet San Franciso, California KubeSense Software Development Austin, Texas Gushwork Software Development Brooklyn, New York Robylon AI Software Development San Francisco, California Cube Technology, Information and Internet Palo Alto, California Klaar Software Development San Francisco, California Bik.ai Technology, Information and Internet Zime Data Infrastructure and Analytics San Jose, CA Show more similar pages Show fewer similar pages Browse jobs Engineer jobs 555,845 open jobs Product Marketer jobs 9,108 open jobs Marketing Manager jobs 106,879 open jobs Scientist jobs 48,969 open jobs Machine Learning Engineer jobs 148,937 open jobs Developer jobs 258,935 open jobs Marketer jobs 37,677 open jobs Intelligence Specialist jobs 7,156 open jobs Intern jobs 71,196 open jobs Python Developer jobs 46,642 open jobs Senior Product Marketing Manager jobs 11,129 open jobs Analyst jobs 694,057 open jobs Manager jobs 1,880,925 open jobs Associate Product Manager jobs 76,300 open jobs General Engineer jobs 54,597 open jobs Software Engineer jobs 300,699 open jobs Associate jobs 1,091,945 open jobs Account Manager jobs 121,519 open jobs Marketing Specialist jobs 49,178 open jobs Digital Marketing Manager jobs 17,135 open jobs Show more jobs like this Show fewer jobs like this Funding SuprSend 1 total round Last Round Seed Oct 14, 2022 External Crunchbase Link for last round of funding US$ 1.0M Investors BoldCap + 4 Other investors See more info on crunchbase More searches More searches Engineer jobs Developer jobs Marketing Manager jobs Machine Learning Engineer jobs Intelligence Specialist jobs Scientist jobs Associate Product Manager jobs Analyst jobs Software Engineer jobs Intern jobs Product Management Intern jobs Talent Specialist jobs Global Marketing Manager jobs Consultant jobs Marketing Lead jobs Marketing Specialist jobs Product Marketer jobs Writer jobs Frontend Developer jobs Program Management Intern jobs Product Manager jobs Associate Project Manager jobs Network Developer jobs Account Manager jobs Digital Marketing Manager jobs Manager jobs Product Engineer jobs Senior Developer jobs Application Engineer jobs Customer Service Technician jobs Advocate jobs Linux Developer jobs Security Administrator jobs Web Developer jobs Senior Software Engineer jobs Full Stack Engineer jobs Data Scientist jobs Curriculum Developer jobs Sales Trainer jobs Science Specialist jobs Web Development Specialist jobs Security Engineer jobs Software Engineer Intern jobs Staff Software Engineer jobs Technology Engineer jobs Lead Software Engineer jobs Research Software Engineer jobs Business Development Associate jobs Technician jobs Content Specialist jobs iOS Developer jobs Senior Product Manager jobs User Interface Designer jobs PHP Developer jobs Product Designer jobs Director jobs Bookkeeper jobs User Experience Designer jobs Operations Engineer jobs Founder jobs LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language Agree & Join LinkedIn By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Sign in to see who you already know at SuprSend Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . | 2026-01-13T08:48:25 |
https://docs.devcycle.com/integrations/google-analytics-4 | Sending DevCycle Data as a Custom Event to Google Analytics 4 (GTM Specific) | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up On this page Sending DevCycle Data as a Custom Event to Google Analytics 4 (GTM Specific) Transition from Google Optimize This guide enables you to integrate DevCycle feature flags with Google Analytics 4 (GA4) for A/B testing and experimentation using Google Tag Manager (GTM). If you are a former Google Optimize customer transitioning to GA4, this guide is specific to GTM implementations. GTM Elements: Tags, Variables, and Triggers Below is a description of Google Tag Manager's tags, variables, and triggers. For more in-depth understanding, consult Google's official documentation . Tags execute specified functionality, such as sending data to GA4 or initializing DevCycle. Variables serve as placeholders for predefined values, which in this guide store the feature and variation data. Triggers are conditions that, when met, execute actions defined in Tags. Google Tag Manager (GTM) Configuration Step 1: Create a New Tag for DevCycle Initialization and Feature Flag Configuration Values Navigate to your GTM workspace and access the "Tags" section. Create a new tag and name it "DevCycle Initialization & Feature Flag Configuration Values". Choose "Custom HTML" for "Tag Configuration". Insert a script to push a custom event named set_user_properties (or any name of your choosing) to the dataLayer with the parameters: featureName: {{featureName}} and variation: {{variation}} . This script can be found below. < script > let user = { isAnonymous : true } ; let devcycleOptions = { logLevel : "debug" } ; let devcycleClient = DevCycle . initializeDevCycle ( "<SDK_KEY>" , // Replace with your specific DevCycle SDK Key user , devcycleOptions ) ; devcycleClient . onClientInitialized ( ) . then ( function ( ) { let features = devcycleClient . allFeatures ( ) ; pushData ( features ) ; } ) ; function pushData ( featuresConfig ) { let arr = [ ] ; // JSON to Array for ( let i in featuresConfig ) { arr . push ( [ i , featuresConfig [ i ] ] ) ; } // Push to dataLayer for ( let j = 0 ; j < arr . length ; j ++ ) { let featureName = arr [ j ] [ 0 ] . replaceAll ( "-" , "_" ) ; let currentVariation = arr [ j ] [ 1 ] [ "variationName" ] . replaceAll ( "-" , "_" ) ; window . dataLayer . push ( { event : "set_user_properties" , // Can be any event name you want featureName : featureName , variationName : currentVariation , } ) ; } } < / script > For “Triggering", select the “Window Loaded” option as the firing trigger. Step 2: Configure GTM Variables Navigate to the “Variable” section. In “User-Defined Variables", create a new variable. Choose “Data Layer Variable” for "Variable Type". Enter “featureName” for "Data Layer Variable Name". Repeat to create another variable and name it “variationName". Step 3: Create Tag to Send Custom Events Option 1: Setup via Google Tag In your GTM workspace, navigate to "Tags" and create a new one. Name it "GA4_Custom_User_Properties". Select "Google Tag" for "Tag Configuration". Provide your Tag ID for your Google Analytics instance. Under "Shared event settings", add a new Parameter with the featureName variable you created as the "Event Parameter", and your variationName variable as the "value". Option 2: Send Custom Events to Google Analytics 4 In your GTM workspace, navigate to "Tags" and create a new one. Name it "GA4_Custom_User_Properties". Select "GA4 Event" for "Tag Configuration." In "Configuration Tag", choose your existing GA4 Configuration Tag. Input set_user_properties for "Event Name" (or the event name you chose). Step 4: Define Trigger for the new Tag Within the tag you just setup, create a new "Firing Trigger" in "Triggering". Create a new trigger and set the trigger type to "Custom Event" or to another trigger of your choice. Name the event (if applicable) as set_user_properties (Or the event name you chose in your custom HTML). Step 5: Publish Changes Before hitting "Submit", it's crucial to validate that your configurations are working as intended. Use GTM's "Preview" mode for this. How to Validate your setup with GTM's Preview Mode Click on "Preview" at the top right of the GTM interface. This will open a new browser tab, where you'll navigate to your website. Perform actions that should trigger the tag you've configured. Check the GTM Preview pane that appears at the bottom of your website. It should show the tags that are fired upon your actions. Specifically, confirm that your DevCycle feature and variation data is correctly passed to GA4 tags. When you've confirmed that your data is being passed in correctly, publish your changes by clicking on "Submit"! Google Analytics 4 Configuration Reporting in Google Analytics 4 Navigate to "Reports" > "Library" > "New Report". Choose the metric for analysis under "Event Metric". Select the feature property under "Dimension," e.g., DevCycle_featureNameA . If the dimension doesn't exist: Go to "Admin" > "Custom definitions" > "Create custom dimension". Set the scope to Event and name the event parameter according to your feature. Contributing to DevCycle or Creating a New Integration: DevCycle's tools and integrations are open source and can be found on the DevCycle GitHub repository . For new integrations, refer to DevCycle's Management API and DevCycle Bucketing API . Edit this page Last updated on Jan 9, 2026 Transition from Google Optimize GTM Elements: Tags, Variables, and Triggers Google Tag Manager (GTM) Configuration Step 1: Create a New Tag for DevCycle Initialization and Feature Flag Configuration Values Step 2: Configure GTM Variables Step 3: Create Tag to Send Custom Events Step 4: Define Trigger for the new Tag Step 5: Publish Changes Google Analytics 4 Configuration Reporting in Google Analytics 4 DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:25 |
https://docs.devcycle.com/sdk/server-side-sdks/node/node-bootstrapping | Bootstrapping / Server-Side Rendering | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up SDK Overview SDK Lifecycle SDK Features Client-side SDKS Server-side SDKS Node.js SDK Installation Getting Started Usage OpenFeature Typescript Bootstrapping / SSR Example App NestJS SDK PHP SDK Go SDK Ruby SDK Python SDK Java SDK .NET SDK SDK Proxy Server-side SDKS Node.js SDK Bootstrapping / SSR On this page Bootstrapping and Server-Side Rendering info If you are using Next.js, we recommend using the Next.js SDK instead of this option. When using a server rendering framework such as Remix, Nuxt, or SvelteKit, you will likely be rendering content on the server and sending it to the client for hydration. When feature flagging is involved, you need to make sure that rendering on the server uses the same flag values as the client. It is also important to avoid the performance impact of the initial client-side DevCycle configuration fetch that would normally have to occur when the page is first loaded. To support these use-cases, the Node.js SDK provides functionality for generating client-side configurations on the server, for use during server-side rendering as well as bootstrapping on the client. To use it, you must also have the DevCycle JS Client SDK installed in your server application. Follow the setup docs for that SDK to get started. To enable this feature, initialize a Node.js client on the server and enable client bootstrapping mode: // devcycle.ts import { initializeDevCycle } from '@devcycle/nodejs-server-sdk' export const devcycleClient = await initializeDevCycle ( '<DEVCYCLE_SERVER_SDK_KEY>' , { enableClientBootstrapping : true , } ) . onClientInitialized ( ) This will instruct the SDK to keep a copy of the client configuration up-to-date in addition to the server configuration. Now, call the client's method for obtaining the bootstrapping config, using the user data representing the current request. You should also pass the userAgent from the request, which allows the SDK to determine some built-in attributes about the user: const user = { user_id : 'some user data' } const bootstrapConfig = await devcycleClient . getClientBootstrapConfig ( user , userAgent ) Calling this method will run a fast, local evaluation of your project's Targeting Rules using a cached copy of the configuration. You can expect the same level of performance as with any server-side evaluation. Now pass the result in wherever you initialize your DevCycle client SDK. For example with the React SDK: import { DevCycleProvider } from '@devcycle/react-client-sdk' export default function App ( ) { return ( < DevCycleProvider options = { { sdkKey : bootstrapConfig . clientSDKKey , bootstrapConfig : bootstrapConfig , user : user } } > < TheRestofYourApp /> </ DevCycleProvider > ) } Make sure you also pass the same "user" that was used to obtain the bootstrap config. You must also provide the client SDK key so that the client-side SDK can initialize. The SDK key you should use is available as the sdkKey field of the bootstrap config. Example Here is an example that connects all these pieces in Remix with the React SDK: // app/root.tsx import type { LoaderFunctionArgs } from "@remix-run/node" import { json } from "@remix-run/node" import { DevCycleProvider } from '@devcycle/react-client-sdk' import { devcycleClient } from '../devcycle' export async function loader ( { request , } : LoaderFunctionArgs ) { const user = await getUser ( request ) ; const userAgent = request . headers . get ( 'user-agent' ) ; const config = await devcycleClient . getClientBootstrapConfig ( user , userAgent ) ; return json ( { user , config } ) ; } export default function Component ( ) { const data = useLoaderData < typeof loader > ( ) ; return ( < DevCycleProvider options = { { sdkKey : data . config . clientSDKKey , bootstrapConfig : data . config , user : data . user } } > < TheRestofYourApp /> </ DevCycleProvider > ) ; } Once these pieces are in place, Remix will supply the component with the client configuration for the current user. It can then be provided to the React SDK by passing it to the bootstrapConfig option of the DevCycleProvider . From this point downwards in the component tree, the React SDK will return Variable values from this bootstrapped config during server-side rendering, and will hydrate with the same configuration on the client. To see this in action, check out the Remix bootstrapping example application . Edit this page Last updated on Jan 9, 2026 Previous Typescript Next Example App Example DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:25 |
https://t.co/h3OqdTZoCW | JavaScript is not available. We’ve detected that JavaScript is disabled in this browser. Please enable JavaScript or switch to a supported browser to continue using x.com. You can see a list of supported browsers in our Help Center. Help Center Terms of Service Privacy Policy Cookie Policy Imprint Ads info © 2026 X Corp. Something went wrong, but don’t fret — let’s give it another shot. Try again Some privacy related extensions may cause issues on x.com. Please disable them and try again. | 2026-01-13T08:48:25 |
https://vi-vn.facebook.com/login/identify/?ctx=recover&from_login_screen=0 | Quên mật khẩu | Không thể đăng nhập | Facebook Tìm tài khoản của bạn Tìm tài khoản của bạn Vui lòng nhập email hoặc số di động để tìm kiếm tài khoản của bạn. Hủy Tìm kiếm Tiếng Việt 한국어 English (US) Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch Đăng ký Đăng nhập Messenger Facebook Lite Video Meta Pay Cửa hàng trên Meta Meta Quest Ray-Ban Meta Meta AI Nội dung khác do Meta AI tạo Instagram Threads Trung tâm thông tin bỏ phiếu Chính sách quyền riêng tư Trung tâm quyền riêng tư Giới thiệu Tạo quảng cáo Tạo Trang Nhà phát triển Tuyển dụng Cookie Lựa chọn quảng cáo Điều khoản Trợ giúp Tải thông tin liên hệ lên & đối tượng không phải người dùng Cài đặt Nhật ký hoạt động Meta © 2026 | 2026-01-13T08:48:25 |
https://www.assemblyai.com/docs?utm_source=devto&utm_medium=challenge&utm_campaign=streaming_challenge&utm_content=support | AssemblyAI Documentation | AssemblyAI | Documentation Gemini 3 Pro now available in LLM Gateway! Learn more Search / Ask AI Sign In Documentation API Reference Cookbooks FAQ Playground Changelog Roadmap Documentation API Reference Cookbooks FAQ Playground Changelog Roadmap Getting started Overview Transcribe a pre-recorded audio file Transcribe streaming audio Models Models Pre-recorded Speech-to-text Streaming Speech-to-text Evaluations Voice AI Platform Speech Understanding Guardrails LLM Gateway Deployment Security Integrations Build with AssemblyAI Build a Voice Agent Build a Meeting Notetaker Build a Medical Scribe Migration guides Sign In Light On this page Quickstart Products Getting started AssemblyAI Documentation Copy page Build with our leading Speech AI models Industry-leading models on a developer-first API Your AI product strategy depends on the foundation that powers it. Make sure you build on the best. Quickstart Transcribe an audio file Learn how to transcribe audio files with our SDK Transcribe streaming audio Learn how to transcribe live audio from a microphone Apply LLMs to audio Learn how to analyze audio content with LLMs Cookbooks Get started quickly with our use-case specific cookbooks Products Speech-to-Text Models for converting audio files, video files, and live speech into text. LLM Gateway LLM Gateway is a framework for applying Large Language Models (LLMs) to spoken data. Audio Intelligence Models for interpreting audio for business and personal workflows. Need help? Talk to our Support team. · Join our Discord community · Check status page · See changelog Transcribe a pre-recorded audio file Learn how to transcribe and analyze an audio file. Next Built with | 2026-01-13T08:48:25 |
https://www.linkedin.com/company/suprsend?trk=organization_guest_main-feed-card-text | SuprSend | LinkedIn Skip to main content LinkedIn Top Content People Learning Jobs Games Sign in Join now SuprSend Software Development San Francisco, CA 19,129 followers Communication Infrastructure for dev & product teams See jobs Follow Discover all 17 employees Report this company About us SuprSend is a central communication stack for easily creating, managing and delivering notifications to your end users on multiple channels. Our single notification API has all the features set, which enables you to send notifications in a reliable and scalable manner and take care of end user experience, thereby eliminating the need to develop any notification service in-house for transactional/engagement notifications. Website https://www.suprsend.com/ External link for SuprSend Industry Software Development Company size 11-50 employees Headquarters San Francisco, CA Type Privately Held Founded 2021 Specialties notifications, android push, ios push, email, sms, whatsapp, slack, Microsoft teams, Telegram, App Inbox, A/B Experiments, web push, RCS, preferences management, batching & digests, notification infrastructure, twilio, template builder, inapp inbox, and react sdk Products SuprSend SuprSend Push Notification Software SuprSend is a notification infrastructure as a service platform for easily creating, managing, and delivering notifications to your end users. SuprSend has all the features set which enable you to send notifications in a reliable and scalable manner, as well as take care of end-user experience, thereby eliminating the need to build any notification service in-house. Benefits of using SuprSend as your notification stack are that: * You do not have to do any vendor integrations for channels in your code. You can easily add/remove/prioritize vendors and channels from your SuprSend account, * You can design powerful templates for all channels together and manage them from a single place, * You can leverage powerful features to experiment fast with notifications and take care of end-user experience without writing a single line of code. Locations Primary San Francisco, CA 94104, US Get directions Bengaluru, KA 560102, IN Get directions Employees at SuprSend Deepak Deolalikar Samuel Sunderaraj Gaurav Verma Sathya Nellore Sampat See all employees Updates SuprSend reposted this SuprSend 19,129 followers 4d Report this post 𝗧𝘆𝗽𝗲-𝘀𝗮𝗳𝗲 𝘄𝗼𝗿𝗸𝗳𝗹𝗼𝘄 𝘁𝗿𝗶𝗴𝗴𝗲𝗿𝘀 𝗶𝗻 𝗦𝘂𝗽𝗿𝗦𝗲𝗻𝗱 🧩 Triggering workflows with loosely typed payloads often leads to bugs that only show up at runtime. To reduce that risk, SuprSend now supports schema-driven type generation for workflow triggers. You define the payload structure once as a JSON schema in SuprSend. From there, the CLI generates strongly-typed interfaces that you can use directly in your application code. What this improves: • Catch invalid payloads during development instead of production • Get IDE autocomplete and immediate feedback while coding • Keep workflow payloads consistent as schemas evolve • Avoid manually maintaining type definitions Type generation is available for 𝗧𝘆𝗽𝗲𝗦𝗰𝗿𝗶𝗽𝘁, 𝗣𝘆𝘁𝗵𝗼𝗻, 𝗚𝗼, 𝗝𝗮𝘃𝗮, 𝗞𝗼𝘁𝗹𝗶𝗻, 𝗦𝘄𝗶𝗳𝘁, 𝗮𝗻𝗱 𝗗𝗮𝗿𝘁. Docs in the comments. 7 1 Comment Like Comment Share SuprSend 19,129 followers 4d Report this post 𝗧𝘆𝗽𝗲-𝘀𝗮𝗳𝗲 𝘄𝗼𝗿𝗸𝗳𝗹𝗼𝘄 𝘁𝗿𝗶𝗴𝗴𝗲𝗿𝘀 𝗶𝗻 𝗦𝘂𝗽𝗿𝗦𝗲𝗻𝗱 🧩 Triggering workflows with loosely typed payloads often leads to bugs that only show up at runtime. To reduce that risk, SuprSend now supports schema-driven type generation for workflow triggers. You define the payload structure once as a JSON schema in SuprSend. From there, the CLI generates strongly-typed interfaces that you can use directly in your application code. What this improves: • Catch invalid payloads during development instead of production • Get IDE autocomplete and immediate feedback while coding • Keep workflow payloads consistent as schemas evolve • Avoid manually maintaining type definitions Type generation is available for 𝗧𝘆𝗽𝗲𝗦𝗰𝗿𝗶𝗽𝘁, 𝗣𝘆𝘁𝗵𝗼𝗻, 𝗚𝗼, 𝗝𝗮𝘃𝗮, 𝗞𝗼𝘁𝗹𝗶𝗻, 𝗦𝘄𝗶𝗳𝘁, 𝗮𝗻𝗱 𝗗𝗮𝗿𝘁. Docs in the comments. 7 1 Comment Like Comment Share SuprSend 19,129 followers 2w Report this post [𝗟𝗜𝗩𝗘] 𝗛𝗼𝘀𝘁𝗲𝗱 𝗣𝗿𝗲𝗳𝗲𝗿𝗲𝗻𝗰𝗲 𝗣𝗮𝗴𝗲: 𝗥𝗲𝗮𝗱𝘆-𝘁𝗼-𝘂𝘀𝗲 𝘂𝘀𝗲𝗿 𝘀𝗲𝘁𝘁𝗶𝗻𝗴𝘀 🌍 SuprSend now gives you a ready-made Preference Page where users can manage how they receive notifications. Just link to it from your emails or SMS — no need to build or maintain your own preference system. It’s designed to help you stay compliant while giving users better control over their communication. We’ve now added full localization support so these pages work seamlessly for global audiences. What’s new: • Pages adapt automatically to the user’s locale • Category names, descriptions, and sections are rendered dynamically • Static page text is localized • Smart fallback when a regional language isn’t available If you’re sending notifications across regions, this makes preference management clearer for users and easier to scale for teams. Preview link in the comments. 5 Like Comment Share SuprSend 19,129 followers 3w Edited Report this post 𝗘𝘅𝗽𝗼𝗿𝘁 𝗡𝗼𝘁𝗶𝗳𝗶𝗰𝗮𝘁𝗶𝗼𝗻𝘀 𝗗𝗮𝘁𝗮 𝘁𝗼 𝗔𝗺𝗮𝘇𝗼𝗻 𝗦𝟯 🚀 Now you can fully own and control your notifications data within your S3 bucket — create custom dashboards, debug delivery issues, or maintain audit trails for compliance. 𝗪𝗵𝗮𝘁'𝘀 𝗶𝗻𝗰𝗹𝘂𝗱𝗲𝗱: • Syncs every 5 minutes in encrypted Parquet files • Messages, Workflow Executions, and Requests • Automatic backfills and hourly partitions • Works natively with Athena, Snowflake, BigQuery, Redshift Confidently build dashboards, surface notification logs to customers, or track entire customer lifecycle end-to-end. Docs in comments 👇 9 1 Comment Like Comment Share SuprSend 19,129 followers 1mo Report this post We're #hiring a new UI / UX Designer in Bengaluru, Karnataka. Apply today or share this post with your network. UI / UX Designer SuprSend, Bengaluru, Karnataka, India 7 Like Comment Share SuprSend 19,129 followers 1mo Edited Report this post 𝗖𝗮𝘁𝗲𝗴𝗼𝗿𝘆 𝗧𝗿𝗮𝗻𝘀𝗹𝗮𝘁𝗶𝗼𝗻𝘀 𝗳𝗼𝗿 𝗣𝗿𝗲𝗳𝗲𝗿𝗲𝗻𝗰𝗲 𝗖𝗲𝗻𝘁𝗲𝗿𝘀 🌍 In pursuit of seamless translations: preference categories now display in your user's locale. 𝗪𝗵𝗮𝘁 𝘁𝗵𝗶𝘀 𝗺𝗲𝗮𝗻𝘀: • One preference center works globally (no separate versions for each region) • Users make informed choices when they see categories in their preferred language • Add translations through Dashboard, API, or CLI • Smart fallback logic ensures something always displays (es-mx → es → en) If you're shipping notifications to a multilingual audience, this removes friction for both your users and your team. Docs in comments below 👇 13 1 Comment Like Comment Share SuprSend 19,129 followers 1mo Report this post 𝗛𝗼𝘄 𝗖𝗿𝗮𝘇𝘆𝗚𝗮𝗺𝗲𝘀 𝗖𝘂𝘁 𝗡𝗼𝘁𝗶𝗳𝗶𝗰𝗮𝘁𝗶𝗼𝗻 𝗗𝗲𝗽𝗹𝗼𝘆𝗺𝗲𝗻𝘁 𝗳𝗿𝗼𝗺 𝗪𝗲𝗲𝗸𝘀 𝘁𝗼 𝗛𝗼𝘂𝗿𝘀 CrazyGames serves 45M+ monthly players across 3,000+ browser games. But their in-house notification system held them back. 🎮 𝗧𝗵𝗲 𝗽𝗿𝗼𝗯𝗹𝗲𝗺: Building notifications required heavy engineering involvement. Even small template changes meant creating dev tickets and took 2 weeks to deploy. Product teams couldn't personalize or experiment fast without developer time. 𝗪𝗵𝗮𝘁 𝗰𝗵𝗮𝗻𝗴𝗲𝗱: CrazyGames adopted SuprSend to abstract notification development out of code. Templates, logic, and workflows shifted entirely to Product & Design. They also connected their database to SuprSend, allowing teams to create targeted cohorts by writing SQL — no data exports, no syncing delays, no engineering bottlenecks. 𝗧𝗵𝗲 𝗿𝗲𝘀𝘂𝗹𝘁: • Notification launches: weeks → hours • Self-serve campaigns with personalized game recommendations • A/B testing across email, push, and in-app — all unified • Product teams operate independently 🎥 Watch Jonas (VP of Product, CrazyGames) full story link in comments below. 33 4 Comments Like Comment Share SuprSend 19,129 followers 1mo Report this post We're #hiring a new Founders’ Office – Product Marketing in Bengaluru, Karnataka. Apply today or share this post with your network. Product Marketing Manager SuprSend, Bengaluru, Karnataka, India 9 1 Comment Like Comment Share SuprSend 19,129 followers 1mo Edited Report this post 𝗜𝗻𝘁𝗿𝗼𝗱𝘂𝗰𝗶𝗻𝗴 𝗧𝗿𝗮𝗻𝘀𝗹𝗮𝘁𝗶𝗼𝗻𝘀 𝗶𝗻 𝗡𝗼𝘁𝗶𝗳𝗶𝗰𝗮𝘁𝗶𝗼𝗻𝘀 Maintaining separate notification templates for every language doesn't scale. Change one template and you update all language versions manually. Translations solve this. Write one template that works across all languages. SuprSend automatically serves the right language based on user locale, with intelligent fallbacks. What's included: • Upload existing JSON translation files & manage through CLI/API • Smart translation keys with automatic language selection • Dynamic variables and pluralization handling • Namespaced keys to organize by feature • Change history with rollback support Documentation in the comments 👇 13 4 Comments Like Comment Share SuprSend 19,129 followers 1mo Report this post We're #hiring a new Product Manager in Bengaluru, Karnataka. Apply today or share this post with your network. Product Manager SuprSend, Bengaluru, Karnataka, India 4 Like Comment Share Join now to see what you are missing Find people you know at SuprSend Browse recommended jobs for you View all updates, news, and articles Join now Similar pages SuperSend Software Development Las Vegas, Nevada Crew Technology, Information and Internet Keploy 🐰 Technology, Information and Internet San Franciso, California KubeSense Software Development Austin, Texas Gushwork Software Development Brooklyn, New York Robylon AI Software Development San Francisco, California Cube Technology, Information and Internet Palo Alto, California Klaar Software Development San Francisco, California Bik.ai Technology, Information and Internet Zime Data Infrastructure and Analytics San Jose, CA Show more similar pages Show fewer similar pages Browse jobs Engineer jobs 555,845 open jobs Product Marketer jobs 9,108 open jobs Marketing Manager jobs 106,879 open jobs Scientist jobs 48,969 open jobs Machine Learning Engineer jobs 148,937 open jobs Developer jobs 258,935 open jobs Marketer jobs 37,677 open jobs Intelligence Specialist jobs 7,156 open jobs Intern jobs 71,196 open jobs Python Developer jobs 46,642 open jobs Senior Product Marketing Manager jobs 11,129 open jobs Analyst jobs 694,057 open jobs Manager jobs 1,880,925 open jobs Associate Product Manager jobs 76,300 open jobs General Engineer jobs 54,597 open jobs Software Engineer jobs 300,699 open jobs Associate jobs 1,091,945 open jobs Account Manager jobs 121,519 open jobs Marketing Specialist jobs 49,178 open jobs Digital Marketing Manager jobs 17,135 open jobs Show more jobs like this Show fewer jobs like this Funding SuprSend 1 total round Last Round Seed Oct 14, 2022 External Crunchbase Link for last round of funding US$ 1.0M Investors BoldCap + 4 Other investors See more info on crunchbase More searches More searches Engineer jobs Developer jobs Marketing Manager jobs Machine Learning Engineer jobs Intelligence Specialist jobs Scientist jobs Associate Product Manager jobs Analyst jobs Software Engineer jobs Intern jobs Product Management Intern jobs Talent Specialist jobs Global Marketing Manager jobs Consultant jobs Marketing Lead jobs Marketing Specialist jobs Product Marketer jobs Writer jobs Frontend Developer jobs Program Management Intern jobs Product Manager jobs Associate Project Manager jobs Network Developer jobs Account Manager jobs Digital Marketing Manager jobs Manager jobs Product Engineer jobs Senior Developer jobs Application Engineer jobs Customer Service Technician jobs Advocate jobs Linux Developer jobs Security Administrator jobs Web Developer jobs Senior Software Engineer jobs Full Stack Engineer jobs Data Scientist jobs Curriculum Developer jobs Sales Trainer jobs Science Specialist jobs Web Development Specialist jobs Security Engineer jobs Software Engineer Intern jobs Staff Software Engineer jobs Technology Engineer jobs Lead Software Engineer jobs Research Software Engineer jobs Business Development Associate jobs Technician jobs Content Specialist jobs iOS Developer jobs Senior Product Manager jobs User Interface Designer jobs PHP Developer jobs Product Designer jobs Director jobs Bookkeeper jobs User Experience Designer jobs Operations Engineer jobs Founder jobs LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language Agree & Join LinkedIn By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Sign in to see who you already know at SuprSend Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . | 2026-01-13T08:48:25 |
https://www.linkedin.com/legal/copyright-policy?trk=d_checkpoint_rp_requestPasswordReset_ft_copyright_policy | Copyright Policy Skip to main content User Agreement Summary of User Agreement Privacy Policy Professional Community Policies Cookie Policy Copyright Policy Regional Info EU Notice California Privacy Disclosure U.S. State Privacy Laws User Agreement Summary of User Agreement Privacy Policy Professional Community Policies Cookie Policy Copyright Policy Regional Info EU Notice California Privacy Disclosure U.S. State Privacy Laws Copyright Policy Effective March 26, 2014 Complaints regarding content posted on the LinkedIn website LinkedIn respects the intellectual property rights of others and desires to offer a platform which contains no content that violates those rights. Our User Agreement requires that information posted by Members be accurate, lawful and not in violation of the rights of third parties. To promote these objectives, LinkedIn provides a process for submission of complaints concerning content posted by our Members. Our policy and procedures are described and/or referenced in the sections that follow. Please note that whether or not we disable access to or remove content, LinkedIn may make a good faith attempt to forward the written notification, including the complainant’s contact information, to the Member who posted the content and/or take other reasonable steps to notify the Member that LinkedIn has received notice of an alleged violation of intellectual property rights or other content violation. It is also our policy, in appropriate circumstances and in our discretion, to disable and/or terminate the accounts of Members, or groups as the case may be, who infringe or repeatedly infringe the rights of others or otherwise post unlawful content. Please note that any notice or counter-notice you submit must be truthful and must be submitted under penalty of perjury. A false notice or counter-notice may give rise to personal liability. You may therefore want to seek the advice of legal counsel before submitting a notice or a counter-notice. Claims regarding copyright infringement Notice of Copyright Infringement: Pursuant to the Digital Millennium Copyright Act (17 U.S.C. § 512), LinkedIn has implemented procedures for receiving written notification of claimed infringements. LinkedIn has also designated an agent to receive notices of claimed copyright infringement. If you believe in good faith that your copyright has been infringed, you may complete and submit a Notice of Copyright Infringement form , or otherwise provide a written communication which contains: An electronic or physical signature of the person authorized to act on behalf of the owner of the copyright interest; A description of the copyrighted work that you claim has been infringed; A description specifying the location on our website of the material that you claim is infringing; Your email address and your mailing address and/or telephone number; A statement by you that you have a good faith belief that the disputed use is not authorized by the copyright owner, its agent, or the law; and A statement by you, made under penalty of perjury, that the information in your notice is accurate and that you are the copyright owner or authorized to act on the copyright owner’s behalf. Please submit your notice to LinkedIn Corporation’s Copyright Agent as follows: Fill out our online submission form to contact the LinkedIn Copyright Agent Or contact us by mail at: LinkedIn Corporation ATTN: Copyright Agent Legal Department 1000 West Maude Avenue Sunnyvale, CA 94085 USA Counter-Notice: If you believe that a notice of copyright infringement has been improperly submitted against you, you may submit a Counter-Notice, pursuant to Sections 512(g)(2) and (3) of the Digital Millennium Copyright Act. You may complete the Counter-Notice Regarding Claim of Copyright Infringement form , or otherwise provide a written communication which contains: Your physical or electronic signature; Identification of the material removed or to which access has been disabled; A statement under penalty of perjury that you have a good faith belief that removal or disablement of the material was a mistake or that the material was misidentified; Your full name, your email address, your mailing address, and a statement that you consent to the jurisdiction of the Federal District court (i) in the judicial district where your address is located if the address is in the United States, or (ii) located in the Northern District of California (Santa Clara County), if your address is located outside the United States, and that you will accept service of process from the Complainant submitting the notice or his/her authorized agent. Please submit your Counter-Notice to LinkedIn’s Copyright Agent via our online submission form or mail to the address specified above. Claims regarding content other than copyright infringement For issues other than copyright infringement please visit our Help Center where you’ll find information on how to flag and report other types of content violations. Learn more: Reporting Inappropriate Content, Messages, or Safety Concerns LinkedIn's Trademark Policy LinkedIn's False Profile Policy Notice regarding Associated Press content on LinkedIn: Associated Press text, photo, graphic, audio and/or video material shall not be published, broadcast, rewritten for broadcast or publication or redistributed directly or indirectly in any medium. Neither these AP materials nor any portion thereof may be stored in a computer except for personal and non-commercial use. Users may not download or reproduce a substantial portion of the AP material found on this web site. AP will not be held liable for any delays, inaccuracies, errors or omissions therefrom or in the transmission or delivery of all or any part thereof or for any damages arising from any of the foregoing. LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language | 2026-01-13T08:48:25 |
http://www.ycombinator.com | Y Combinator About What Happens at YC? Apply YC Interview Guide FAQ People YC Blog Companies Startup Directory Founder Directory Launch YC Startup Jobs All Jobs ◦ Engineering ◦ Operations ◦ Marketing ◦ Sales Internships Startup Job Guide YC Startup Jobs Blog Find a Co-Founder Library SAFE Resources Startup School Newsletter Requests for Startups For Investors Verify Founders Hacker News Bookface Open main menu Apply for X2026 batch. Apply Y Combinator Make something people want. Apply to YC 5,000 funded startups $800B combined valuation Top YC companies + We help founders make something people want and the results speak for themselves. We help founders at their earliest stages regardless of their age. We improve the success rate of our startups. We give startups a huge fundraising advantage. Our companies have a track record of becoming billion dollar companies. Our formula for success . YC is run by startup founders who have built exactly what they wanted when starting and growing a startup. The most experienced partners Each founder is assigned a dedicated YC partner who has mentored hundreds of YC companies. They have more data on what it takes to build a successful startup than any other early stage startup advisor. These partners read applications, interview companies, and mentor startups throughout the batch. You can access them in person, over email, and on Slack. Investor network YC companies have raised $85 billion dollars from the best investors in the world. Our founders have access to the YC Investor Database which has profiles and reviews for more than 50,000 startup investors. Private social network only for founders YC founders get to benefit from the collective wisdom of over 9000 YC alumni. They can access these alums through Bookface, our private social network. We have a forum for asking questions to the community, a founder directory for finding specific people who can provide advice and intros, and a company directory for finding potential customers. Exclusive deals YC founders have access to over 1000 deals from leading software companies. Every YC company gets free credits or significant discounts on hosting, banking, cap table management, back office, and much more. Companies report these deals to be worth in excess of $500,000. The best written advice YC founders get to benefit from our collective experience funding 5000 companies across almost 20 years. We have extensive documentation for common questions about fundraising, go to market, sales, product market fit, mental health, hiring, and much more. Networks to build your team Through Work at a Startup and HN , we help our founders hire the small number of early engineers and other team members critical to finding product market fit. At any given time there are 150,000+ candidates searching for jobs at early stage YC companies. We put founders' interests first. We don’t take a board seat. We don’t demand 20% of your company. We don’t take weeks/months to decide to invest. We don’t charge fees. We don’t require decks, business plans, or MBAs. We don't tell you what to do. We only offer advice. Hear more from the community. " Y Combinator is the best program for creating top-end entrepreneurs that has ever existed. " Marc Andreessen , General Partner, Andreessen Horowitz " Y Combinator is the best startup accelerator in the world. YC helps their companies a lot, and the YC community is a huge asset for the companies that go through the program. " Ron Conway , Founder, SV Angel " At YC, we were challenged to do things that don't scale – to start with the perfect experience for one person, then work backwards and scale it to 100 people who love us. This was the best piece of advice we've ever received. " Brian Chesky , Founder, Airbnb (YC W09) " I doubt that Stripe would have worked without YC. It's that simple. Acquiring early customers, figuring out who to hire, closing deals with banks, raising money – YC's partners were closely involved and crucially helpful. " Patrick Collison , Founder, Stripe (YC S09) Want to learn more? YC Library Videos, podcasts, and essays for startup founders Newsletter Keep up with the latest news, launches, jobs, and events from the YC community Launch YC Discover new YC companies and products Work at a Startup Find your next role at a YC startup Blog Essays, events, and announcements from YC Co-Founder Matching Meet a potential co-founder to start a startup with Footer Y Combinator Programs YC Program Startup School Work at a Startup Co-Founder Matching Company YC Blog Contact Press People Careers Privacy Policy Notice at Collection Security Terms of Use Resources Startup Directory Startup Library Investors SAFE Hacker News Launch YC YC Deals Make something people want. Apply Twitter Twitter Facebook Facebook Instagram Instagram LinkedIn LinkedIn Youtube YouTube © 2026 Y Combinator | 2026-01-13T08:48:25 |
https://www.linkedin.com/posts/suprsend_%F0%9D%97%96%F0%9D%97%AE%F0%9D%98%81%F0%9D%97%B2%F0%9D%97%B4%F0%9D%97%BC%F0%9D%97%BF%F0%9D%98%86-%F0%9D%97%A7%F0%9D%97%BF%F0%9D%97%AE%F0%9D%97%BB%F0%9D%98%80%F0%9D%97%B9%F0%9D%97%AE%F0%9D%98%81%F0%9D%97%B6%F0%9D%97%BC%F0%9D%97%BB%F0%9D%98%80-activity-7404527843570991104-bYon | Seamless Translations for Multilingual Preference Centers | SuprSend posted on the topic | LinkedIn Agree & Join LinkedIn By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Skip to main content LinkedIn Top Content People Learning Jobs Games Sign in Join now for free Seamless Translations for Multilingual Preference Centers This title was summarized by AI from the post below. SuprSend 19,129 followers 1mo Edited Report this post 𝗖𝗮𝘁𝗲𝗴𝗼𝗿𝘆 𝗧𝗿𝗮𝗻𝘀𝗹𝗮𝘁𝗶𝗼𝗻𝘀 𝗳𝗼𝗿 𝗣𝗿𝗲𝗳𝗲𝗿𝗲𝗻𝗰𝗲 𝗖𝗲𝗻𝘁𝗲𝗿𝘀 🌍 In pursuit of seamless translations: preference categories now display in your user's locale. 𝗪𝗵𝗮𝘁 𝘁𝗵𝗶𝘀 𝗺𝗲𝗮𝗻𝘀: • One preference center works globally (no separate versions for each region) • Users make informed choices when they see categories in their preferred language • Add translations through Dashboard, API, or CLI • Smart fallback logic ensures something always displays (es-mx → es → en) If you're shipping notifications to a multilingual audience, this removes friction for both your users and your team. Docs in comments below 👇 13 1 Comment Like Comment Share Copy LinkedIn Facebook X SuprSend 1mo Report this comment Check the docs: https://docs.suprsend.com/docs/user-preferences#translating-preference-categories-in-user ’s-locale Like Reply 1 Reaction To view or add a comment, sign in More Relevant Posts Shoesmith Life Cycle LLC 46 followers 3w Report this post Gemini Enhances Conversations with New Live Speech Translation Features https://lnkd.in/erRm5MMq #supportsmallbusinesses #smallbusinessowner #smallbusiness #shoesmithlc Gemini Enhances Conversations with New Live Speech Translation Features smallbiztrends.com Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Modilingua 42 followers 1w Report this post You can have clean code. You can have a perfect launch strategy. But if your localization workflow relies on manual copy-pasting and direct dictionary swaps, you're creating friction for every new user. Products can stall in new markets simply because the operational side of translation was ignored. Check out my roundup of 14 of the best technical and strategic guides to fix this. I cover the entire ecosystem: ▪️ Automating workflows in Google Sheets ▪️ Running regression tests with Selenium ▪️ Fixing broken date formats and syntax ▪️ Managing auto-translate on social platforms Stop getting lost in translation. Start building a system that scales. Read the full guide here: https://lnkd.in/dQX-HJqn 1 Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in SuprSend 19,129 followers 2w Report this post [𝗟𝗜𝗩𝗘] 𝗛𝗼𝘀𝘁𝗲𝗱 𝗣𝗿𝗲𝗳𝗲𝗿𝗲𝗻𝗰𝗲 𝗣𝗮𝗴𝗲: 𝗥𝗲𝗮𝗱𝘆-𝘁𝗼-𝘂𝘀𝗲 𝘂𝘀𝗲𝗿 𝘀𝗲𝘁𝘁𝗶𝗻𝗴𝘀 🌍 SuprSend now gives you a ready-made Preference Page where users can manage how they receive notifications. Just link to it from your emails or SMS — no need to build or maintain your own preference system. It’s designed to help you stay compliant while giving users better control over their communication. We’ve now added full localization support so these pages work seamlessly for global audiences. What’s new: • Pages adapt automatically to the user’s locale • Category names, descriptions, and sections are rendered dynamically • Static page text is localized • Smart fallback when a regional language isn’t available If you’re sending notifications across regions, this makes preference management clearer for users and easier to scale for teams. Preview link in the comments. 5 Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Raisa Carazo - ✅ Chartered Linguist 1mo Report this post 💡 Avoiding Back-and-Forth Emails: Save Time, Boost Profitability If you’re managing client projects, you know how time-consuming endless email chains can be. Every email isn’t just communication 👉🏻it’s time, and time is money. Here’s a simple strategy to minimise the back-and-forth: 👉🏻 Before hitting “send” read your email 2-3 times 👉🏻 Ask yourself: What questions might the client have after reading this? 👉🏻 If you can anticipate their doubts, address them upfront. Provide clarity, context, and all necessary details. Being one step ahead doesn’t just make you look professional; it protects your schedule, improves project efficiency, and directly impacts profitability. Next time you draft an email, ask yourself: is everything clear, or am I inviting more questions? ______________________________ ⚠️ In finance, medicine, or technical fields, words carry risk, regulation, and reputation. 🚫 Generic won’t cut it 🚫 AI can’t read the room Finding real technical translators you can trust? That’s the hard part. 👉🏻 𝐓𝐡𝐚𝐭’𝐬 𝐰𝐡𝐞𝐫𝐞 𝐰𝐞 𝐜𝐨𝐦𝐞 𝐢𝐧. ✅ High-precision translation by subject-matter experts who have done it IRL. 🔗 JYC Translations - Your Technical Translation Team 🌍 3w jyctranslations com #TechnicalTranslations #FinancialTranslation #Localization #ProjectManagement #ProfessionalTips 8 Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Hiroko Imai Google Business Profile Diamond Product Expert | PE Ambassador 2w Report this post It seems they've added a help page about reviews. The key point here is: "Important: Reviews and other user contributions to Google Maps must reflect a genuine experience." This clearly shows Google's serious commitment to this policy. Create a link or QR code to request reviews(*) https://lnkd.in/g_mbF2sK *Currently, help pages in languages other than English seem to be behind in translation, so English versions are being displayed. Translations for each language will be added eventually. #GoogleBusinessProfile 9 4 Comments Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Ana Catarina Lopes 4w Report this post Speed gets you seen. Accuracy is what makes people trust you. Ana Sofia Correia published a new Med & Mark article on a topic she keeps coming back to: We’re all producing content faster… but that doesn’t mean it’s clearer. She breaks down the points where things usually get messy (source development, review, and localization) and how teams can keep accuracy and consistency without slowing everything down. I hope you’ll find it useful. Read the full article: Speed can get you noticed. Accuracy is what earns trust. 👇 🔗 https://lnkd.in/eNzVYXiJ 11 1 Comment Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in M.A. Utsav 1mo Report this post Google is upgrading Translate and related features with Gemini so translations sound more natural, work live in your headphones, and support more language-learning tools. 1 Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Jonathan Alejandro Diaz Mollocondo 3w Report this post If your product speaks only one language, your revenue is capped. I’ve seen teams delay localization because: - We’ll do it later - It’s just translations But adding a language flag early: - Prevents data rewrites - Avoids breaking API contracts - Keeps schemas future-proof This isn’t a tech detail. It’s a growth strategy hidden in your backend. Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Techy 101 5 followers 1mo Report this post 🤖 Tech made simple with Techy101: Google Translate is now powered by Gemini, includes live translations on headphones Today Google is finally revamping Google Translate, infusing it with Gemini capabilities in order to improve translations, especially on phrases with nuanced Read more at Techy101.com ⚡ https://lnkd.in/gmpEyH5Y Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Danidu Muhandiram 4w Report this post Recently, I built a simple bulk keyword translation tool to support my own workflow. I’m sharing it in case it’s useful for others with similar needs. When working with large keyword lists on a daily basis, it’s often necessary to check the meaning and intent of keywords in a target language to maintain content quality. Doing this manually becomes inefficient when handling hundreds or thousands of keywords. The tool allows you to: • Paste keyword lists in bulk • Hover over or select individual keywords to view their translations • Remove unwanted keywords instantly • Copy the final cleaned keyword list easily (input/output) Currently, the application uses a lightweight translation service suitable for general validation. There are plans to move to a higher accuracy translation provider (such as DeepL or a premium API) to further improve translation quality and reliability for professional keyword analysis. Demo: https://lnkd.in/g4f8Gqjr For tech stack related details: https://lnkd.in/gEmRE7mm 24 1 Comment Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in 19,129 followers View Profile Connect Explore content categories Career Productivity Finance Soft Skills & Emotional Intelligence Project Management Education Technology Leadership Ecommerce User Experience Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language Sign in to view more content Create your free account or sign in to continue your search Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . | 2026-01-13T08:48:25 |
https://www.linkedin.com/company/suprsend?trk=organization_guest_main-feed-card_feed-actor-name | SuprSend | LinkedIn Skip to main content LinkedIn Top Content People Learning Jobs Games Sign in Join for free SuprSend Software Development San Francisco, CA 19,129 followers Communication Infrastructure for dev & product teams See jobs Follow Discover all 17 employees Report this company About us SuprSend is a central communication stack for easily creating, managing and delivering notifications to your end users on multiple channels. Our single notification API has all the features set, which enables you to send notifications in a reliable and scalable manner and take care of end user experience, thereby eliminating the need to develop any notification service in-house for transactional/engagement notifications. Website https://www.suprsend.com/ External link for SuprSend Industry Software Development Company size 11-50 employees Headquarters San Francisco, CA Type Privately Held Founded 2021 Specialties notifications, android push, ios push, email, sms, whatsapp, slack, Microsoft teams, Telegram, App Inbox, A/B Experiments, web push, RCS, preferences management, batching & digests, notification infrastructure, twilio, template builder, inapp inbox, and react sdk Products SuprSend SuprSend Push Notification Software SuprSend is a notification infrastructure as a service platform for easily creating, managing, and delivering notifications to your end users. SuprSend has all the features set which enable you to send notifications in a reliable and scalable manner, as well as take care of end-user experience, thereby eliminating the need to build any notification service in-house. Benefits of using SuprSend as your notification stack are that: * You do not have to do any vendor integrations for channels in your code. You can easily add/remove/prioritize vendors and channels from your SuprSend account, * You can design powerful templates for all channels together and manage them from a single place, * You can leverage powerful features to experiment fast with notifications and take care of end-user experience without writing a single line of code. Locations Primary San Francisco, CA 94104, US Get directions Bengaluru, KA 560102, IN Get directions Employees at SuprSend Deepak Deolalikar Samuel Sunderaraj Gaurav Verma Sathya Nellore Sampat See all employees Updates SuprSend reposted this SuprSend 19,129 followers 4d Report this post 𝗧𝘆𝗽𝗲-𝘀𝗮𝗳𝗲 𝘄𝗼𝗿𝗸𝗳𝗹𝗼𝘄 𝘁𝗿𝗶𝗴𝗴𝗲𝗿𝘀 𝗶𝗻 𝗦𝘂𝗽𝗿𝗦𝗲𝗻𝗱 🧩 Triggering workflows with loosely typed payloads often leads to bugs that only show up at runtime. To reduce that risk, SuprSend now supports schema-driven type generation for workflow triggers. You define the payload structure once as a JSON schema in SuprSend. From there, the CLI generates strongly-typed interfaces that you can use directly in your application code. What this improves: • Catch invalid payloads during development instead of production • Get IDE autocomplete and immediate feedback while coding • Keep workflow payloads consistent as schemas evolve • Avoid manually maintaining type definitions Type generation is available for 𝗧𝘆𝗽𝗲𝗦𝗰𝗿𝗶𝗽𝘁, 𝗣𝘆𝘁𝗵𝗼𝗻, 𝗚𝗼, 𝗝𝗮𝘃𝗮, 𝗞𝗼𝘁𝗹𝗶𝗻, 𝗦𝘄𝗶𝗳𝘁, 𝗮𝗻𝗱 𝗗𝗮𝗿𝘁. Docs in the comments. 7 1 Comment Like Comment Share SuprSend 19,129 followers 4d Report this post 𝗧𝘆𝗽𝗲-𝘀𝗮𝗳𝗲 𝘄𝗼𝗿𝗸𝗳𝗹𝗼𝘄 𝘁𝗿𝗶𝗴𝗴𝗲𝗿𝘀 𝗶𝗻 𝗦𝘂𝗽𝗿𝗦𝗲𝗻𝗱 🧩 Triggering workflows with loosely typed payloads often leads to bugs that only show up at runtime. To reduce that risk, SuprSend now supports schema-driven type generation for workflow triggers. You define the payload structure once as a JSON schema in SuprSend. From there, the CLI generates strongly-typed interfaces that you can use directly in your application code. What this improves: • Catch invalid payloads during development instead of production • Get IDE autocomplete and immediate feedback while coding • Keep workflow payloads consistent as schemas evolve • Avoid manually maintaining type definitions Type generation is available for 𝗧𝘆𝗽𝗲𝗦𝗰𝗿𝗶𝗽𝘁, 𝗣𝘆𝘁𝗵𝗼𝗻, 𝗚𝗼, 𝗝𝗮𝘃𝗮, 𝗞𝗼𝘁𝗹𝗶𝗻, 𝗦𝘄𝗶𝗳𝘁, 𝗮𝗻𝗱 𝗗𝗮𝗿𝘁. Docs in the comments. 7 1 Comment Like Comment Share SuprSend 19,129 followers 2w Report this post [𝗟𝗜𝗩𝗘] 𝗛𝗼𝘀𝘁𝗲𝗱 𝗣𝗿𝗲𝗳𝗲𝗿𝗲𝗻𝗰𝗲 𝗣𝗮𝗴𝗲: 𝗥𝗲𝗮𝗱𝘆-𝘁𝗼-𝘂𝘀𝗲 𝘂𝘀𝗲𝗿 𝘀𝗲𝘁𝘁𝗶𝗻𝗴𝘀 🌍 SuprSend now gives you a ready-made Preference Page where users can manage how they receive notifications. Just link to it from your emails or SMS — no need to build or maintain your own preference system. It’s designed to help you stay compliant while giving users better control over their communication. We’ve now added full localization support so these pages work seamlessly for global audiences. What’s new: • Pages adapt automatically to the user’s locale • Category names, descriptions, and sections are rendered dynamically • Static page text is localized • Smart fallback when a regional language isn’t available If you’re sending notifications across regions, this makes preference management clearer for users and easier to scale for teams. Preview link in the comments. 5 Like Comment Share SuprSend 19,129 followers 3w Edited Report this post 𝗘𝘅𝗽𝗼𝗿𝘁 𝗡𝗼𝘁𝗶𝗳𝗶𝗰𝗮𝘁𝗶𝗼𝗻𝘀 𝗗𝗮𝘁𝗮 𝘁𝗼 𝗔𝗺𝗮𝘇𝗼𝗻 𝗦𝟯 🚀 Now you can fully own and control your notifications data within your S3 bucket — create custom dashboards, debug delivery issues, or maintain audit trails for compliance. 𝗪𝗵𝗮𝘁'𝘀 𝗶𝗻𝗰𝗹𝘂𝗱𝗲𝗱: • Syncs every 5 minutes in encrypted Parquet files • Messages, Workflow Executions, and Requests • Automatic backfills and hourly partitions • Works natively with Athena, Snowflake, BigQuery, Redshift Confidently build dashboards, surface notification logs to customers, or track entire customer lifecycle end-to-end. Docs in comments 👇 9 1 Comment Like Comment Share SuprSend 19,129 followers 1mo Report this post We're #hiring a new UI / UX Designer in Bengaluru, Karnataka. Apply today or share this post with your network. UI / UX Designer SuprSend, Bengaluru, Karnataka, India 7 Like Comment Share SuprSend 19,129 followers 1mo Edited Report this post 𝗖𝗮𝘁𝗲𝗴𝗼𝗿𝘆 𝗧𝗿𝗮𝗻𝘀𝗹𝗮𝘁𝗶𝗼𝗻𝘀 𝗳𝗼𝗿 𝗣𝗿𝗲𝗳𝗲𝗿𝗲𝗻𝗰𝗲 𝗖𝗲𝗻𝘁𝗲𝗿𝘀 🌍 In pursuit of seamless translations: preference categories now display in your user's locale. 𝗪𝗵𝗮𝘁 𝘁𝗵𝗶𝘀 𝗺𝗲𝗮𝗻𝘀: • One preference center works globally (no separate versions for each region) • Users make informed choices when they see categories in their preferred language • Add translations through Dashboard, API, or CLI • Smart fallback logic ensures something always displays (es-mx → es → en) If you're shipping notifications to a multilingual audience, this removes friction for both your users and your team. Docs in comments below 👇 13 1 Comment Like Comment Share SuprSend 19,129 followers 1mo Report this post 𝗛𝗼𝘄 𝗖𝗿𝗮𝘇𝘆𝗚𝗮𝗺𝗲𝘀 𝗖𝘂𝘁 𝗡𝗼𝘁𝗶𝗳𝗶𝗰𝗮𝘁𝗶𝗼𝗻 𝗗𝗲𝗽𝗹𝗼𝘆𝗺𝗲𝗻𝘁 𝗳𝗿𝗼𝗺 𝗪𝗲𝗲𝗸𝘀 𝘁𝗼 𝗛𝗼𝘂𝗿𝘀 CrazyGames serves 45M+ monthly players across 3,000+ browser games. But their in-house notification system held them back. 🎮 𝗧𝗵𝗲 𝗽𝗿𝗼𝗯𝗹𝗲𝗺: Building notifications required heavy engineering involvement. Even small template changes meant creating dev tickets and took 2 weeks to deploy. Product teams couldn't personalize or experiment fast without developer time. 𝗪𝗵𝗮𝘁 𝗰𝗵𝗮𝗻𝗴𝗲𝗱: CrazyGames adopted SuprSend to abstract notification development out of code. Templates, logic, and workflows shifted entirely to Product & Design. They also connected their database to SuprSend, allowing teams to create targeted cohorts by writing SQL — no data exports, no syncing delays, no engineering bottlenecks. 𝗧𝗵𝗲 𝗿𝗲𝘀𝘂𝗹𝘁: • Notification launches: weeks → hours • Self-serve campaigns with personalized game recommendations • A/B testing across email, push, and in-app — all unified • Product teams operate independently 🎥 Watch Jonas (VP of Product, CrazyGames) full story link in comments below. 33 4 Comments Like Comment Share SuprSend 19,129 followers 1mo Report this post We're #hiring a new Founders’ Office – Product Marketing in Bengaluru, Karnataka. Apply today or share this post with your network. Product Marketing Manager SuprSend, Bengaluru, Karnataka, India 9 1 Comment Like Comment Share SuprSend 19,129 followers 1mo Edited Report this post 𝗜𝗻𝘁𝗿𝗼𝗱𝘂𝗰𝗶𝗻𝗴 𝗧𝗿𝗮𝗻𝘀𝗹𝗮𝘁𝗶𝗼𝗻𝘀 𝗶𝗻 𝗡𝗼𝘁𝗶𝗳𝗶𝗰𝗮𝘁𝗶𝗼𝗻𝘀 Maintaining separate notification templates for every language doesn't scale. Change one template and you update all language versions manually. Translations solve this. Write one template that works across all languages. SuprSend automatically serves the right language based on user locale, with intelligent fallbacks. What's included: • Upload existing JSON translation files & manage through CLI/API • Smart translation keys with automatic language selection • Dynamic variables and pluralization handling • Namespaced keys to organize by feature • Change history with rollback support Documentation in the comments 👇 13 4 Comments Like Comment Share SuprSend 19,129 followers 1mo Report this post We're #hiring a new Product Manager in Bengaluru, Karnataka. Apply today or share this post with your network. Product Manager SuprSend, Bengaluru, Karnataka, India 4 Like Comment Share Join now to see what you are missing Find people you know at SuprSend Browse recommended jobs for you View all updates, news, and articles Join now Similar pages SuperSend Software Development Las Vegas, Nevada Crew Technology, Information and Internet Keploy 🐰 Technology, Information and Internet San Franciso, California KubeSense Software Development Austin, Texas Gushwork Software Development Brooklyn, New York Robylon AI Software Development San Francisco, California Cube Technology, Information and Internet Palo Alto, California Klaar Software Development San Francisco, California Bik.ai Technology, Information and Internet Zime Data Infrastructure and Analytics San Jose, CA Show more similar pages Show fewer similar pages Browse jobs Engineer jobs 555,845 open jobs Product Marketer jobs 9,108 open jobs Marketing Manager jobs 106,879 open jobs Scientist jobs 48,969 open jobs Machine Learning Engineer jobs 148,937 open jobs Developer jobs 258,935 open jobs Marketer jobs 37,677 open jobs Intelligence Specialist jobs 7,156 open jobs Intern jobs 71,196 open jobs Python Developer jobs 46,642 open jobs Senior Product Marketing Manager jobs 11,129 open jobs Analyst jobs 694,057 open jobs Manager jobs 1,880,925 open jobs Associate Product Manager jobs 76,300 open jobs General Engineer jobs 54,597 open jobs Software Engineer jobs 300,699 open jobs Associate jobs 1,091,945 open jobs Account Manager jobs 121,519 open jobs Marketing Specialist jobs 49,178 open jobs Digital Marketing Manager jobs 17,135 open jobs Show more jobs like this Show fewer jobs like this Funding SuprSend 1 total round Last Round Seed Oct 14, 2022 External Crunchbase Link for last round of funding US$ 1.0M Investors BoldCap + 4 Other investors See more info on crunchbase More searches More searches Engineer jobs Developer jobs Marketing Manager jobs Machine Learning Engineer jobs Intelligence Specialist jobs Scientist jobs Associate Product Manager jobs Analyst jobs Software Engineer jobs Intern jobs Product Management Intern jobs Talent Specialist jobs Global Marketing Manager jobs Consultant jobs Marketing Lead jobs Marketing Specialist jobs Product Marketer jobs Writer jobs Frontend Developer jobs Program Management Intern jobs Product Manager jobs Associate Project Manager jobs Network Developer jobs Account Manager jobs Digital Marketing Manager jobs Manager jobs Product Engineer jobs Senior Developer jobs Application Engineer jobs Customer Service Technician jobs Advocate jobs Linux Developer jobs Security Administrator jobs Web Developer jobs Senior Software Engineer jobs Full Stack Engineer jobs Data Scientist jobs Curriculum Developer jobs Sales Trainer jobs Science Specialist jobs Web Development Specialist jobs Security Engineer jobs Software Engineer Intern jobs Staff Software Engineer jobs Technology Engineer jobs Lead Software Engineer jobs Research Software Engineer jobs Business Development Associate jobs Technician jobs Content Specialist jobs iOS Developer jobs Senior Product Manager jobs User Interface Designer jobs PHP Developer jobs Product Designer jobs Director jobs Bookkeeper jobs User Experience Designer jobs Operations Engineer jobs Founder jobs LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language Agree & Join LinkedIn By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Sign in to see who you already know at SuprSend Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . | 2026-01-13T08:48:25 |
https://www.youtube.com/channel/UCr8O8l5cCX85Oem1d18EezQ/videos | Daniel Bourke - YouTube 정보 보도자료 저작권 문의하기 크리에이터 광고 개발자 약관 개인정보처리방침 정책 및 안전 YouTube 작동의 원리 새로운 기능 테스트하기 © 2026 Google LLC, Sundar Pichai, 1600 Amphitheatre Parkway, Mountain View CA 94043, USA, 0807-882-594 (무료), yt-support-solutions-kr@google.com, 호스팅: Google LLC, 사업자정보 , 불법촬영물 신고 크리에이터들이 유튜브 상에 게시, 태그 또는 추천한 상품들은 판매자들의 약관에 따라 판매됩니다. 유튜브는 이러한 제품들을 판매하지 않으며, 그에 대한 책임을 지지 않습니다. | 2026-01-13T08:48:25 |
https://www.linkedin.com/company/suprsend | SuprSend | LinkedIn Skip to main content LinkedIn Top Content People Learning Jobs Games Sign in Join now SuprSend Software Development San Francisco, CA 19,129 followers Communication Infrastructure for dev & product teams See jobs Follow Discover all 17 employees Report this company About us SuprSend is a central communication stack for easily creating, managing and delivering notifications to your end users on multiple channels. Our single notification API has all the features set, which enables you to send notifications in a reliable and scalable manner and take care of end user experience, thereby eliminating the need to develop any notification service in-house for transactional/engagement notifications. Website https://www.suprsend.com/ External link for SuprSend Industry Software Development Company size 11-50 employees Headquarters San Francisco, CA Type Privately Held Founded 2021 Specialties notifications, android push, ios push, email, sms, whatsapp, slack, Microsoft teams, Telegram, App Inbox, A/B Experiments, web push, RCS, preferences management, batching & digests, notification infrastructure, twilio, template builder, inapp inbox, and react sdk Products SuprSend SuprSend Push Notification Software SuprSend is a notification infrastructure as a service platform for easily creating, managing, and delivering notifications to your end users. SuprSend has all the features set which enable you to send notifications in a reliable and scalable manner, as well as take care of end-user experience, thereby eliminating the need to build any notification service in-house. Benefits of using SuprSend as your notification stack are that: * You do not have to do any vendor integrations for channels in your code. You can easily add/remove/prioritize vendors and channels from your SuprSend account, * You can design powerful templates for all channels together and manage them from a single place, * You can leverage powerful features to experiment fast with notifications and take care of end-user experience without writing a single line of code. Locations Primary San Francisco, CA 94104, US Get directions Bengaluru, KA 560102, IN Get directions Employees at SuprSend Deepak Deolalikar Samuel Sunderaraj Gaurav Verma Sathya Nellore Sampat See all employees Updates SuprSend reposted this SuprSend 19,129 followers 4d Report this post 𝗧𝘆𝗽𝗲-𝘀𝗮𝗳𝗲 𝘄𝗼𝗿𝗸𝗳𝗹𝗼𝘄 𝘁𝗿𝗶𝗴𝗴𝗲𝗿𝘀 𝗶𝗻 𝗦𝘂𝗽𝗿𝗦𝗲𝗻𝗱 🧩 Triggering workflows with loosely typed payloads often leads to bugs that only show up at runtime. To reduce that risk, SuprSend now supports schema-driven type generation for workflow triggers. You define the payload structure once as a JSON schema in SuprSend. From there, the CLI generates strongly-typed interfaces that you can use directly in your application code. What this improves: • Catch invalid payloads during development instead of production • Get IDE autocomplete and immediate feedback while coding • Keep workflow payloads consistent as schemas evolve • Avoid manually maintaining type definitions Type generation is available for 𝗧𝘆𝗽𝗲𝗦𝗰𝗿𝗶𝗽𝘁, 𝗣𝘆𝘁𝗵𝗼𝗻, 𝗚𝗼, 𝗝𝗮𝘃𝗮, 𝗞𝗼𝘁𝗹𝗶𝗻, 𝗦𝘄𝗶𝗳𝘁, 𝗮𝗻𝗱 𝗗𝗮𝗿𝘁. Docs in the comments. 7 1 Comment Like Comment Share SuprSend 19,129 followers 4d Report this post 𝗧𝘆𝗽𝗲-𝘀𝗮𝗳𝗲 𝘄𝗼𝗿𝗸𝗳𝗹𝗼𝘄 𝘁𝗿𝗶𝗴𝗴𝗲𝗿𝘀 𝗶𝗻 𝗦𝘂𝗽𝗿𝗦𝗲𝗻𝗱 🧩 Triggering workflows with loosely typed payloads often leads to bugs that only show up at runtime. To reduce that risk, SuprSend now supports schema-driven type generation for workflow triggers. You define the payload structure once as a JSON schema in SuprSend. From there, the CLI generates strongly-typed interfaces that you can use directly in your application code. What this improves: • Catch invalid payloads during development instead of production • Get IDE autocomplete and immediate feedback while coding • Keep workflow payloads consistent as schemas evolve • Avoid manually maintaining type definitions Type generation is available for 𝗧𝘆𝗽𝗲𝗦𝗰𝗿𝗶𝗽𝘁, 𝗣𝘆𝘁𝗵𝗼𝗻, 𝗚𝗼, 𝗝𝗮𝘃𝗮, 𝗞𝗼𝘁𝗹𝗶𝗻, 𝗦𝘄𝗶𝗳𝘁, 𝗮𝗻𝗱 𝗗𝗮𝗿𝘁. Docs in the comments. 7 1 Comment Like Comment Share SuprSend 19,129 followers 2w Report this post [𝗟𝗜𝗩𝗘] 𝗛𝗼𝘀𝘁𝗲𝗱 𝗣𝗿𝗲𝗳𝗲𝗿𝗲𝗻𝗰𝗲 𝗣𝗮𝗴𝗲: 𝗥𝗲𝗮𝗱𝘆-𝘁𝗼-𝘂𝘀𝗲 𝘂𝘀𝗲𝗿 𝘀𝗲𝘁𝘁𝗶𝗻𝗴𝘀 🌍 SuprSend now gives you a ready-made Preference Page where users can manage how they receive notifications. Just link to it from your emails or SMS — no need to build or maintain your own preference system. It’s designed to help you stay compliant while giving users better control over their communication. We’ve now added full localization support so these pages work seamlessly for global audiences. What’s new: • Pages adapt automatically to the user’s locale • Category names, descriptions, and sections are rendered dynamically • Static page text is localized • Smart fallback when a regional language isn’t available If you’re sending notifications across regions, this makes preference management clearer for users and easier to scale for teams. Preview link in the comments. 5 Like Comment Share SuprSend 19,129 followers 3w Edited Report this post 𝗘𝘅𝗽𝗼𝗿𝘁 𝗡𝗼𝘁𝗶𝗳𝗶𝗰𝗮𝘁𝗶𝗼𝗻𝘀 𝗗𝗮𝘁𝗮 𝘁𝗼 𝗔𝗺𝗮𝘇𝗼𝗻 𝗦𝟯 🚀 Now you can fully own and control your notifications data within your S3 bucket — create custom dashboards, debug delivery issues, or maintain audit trails for compliance. 𝗪𝗵𝗮𝘁'𝘀 𝗶𝗻𝗰𝗹𝘂𝗱𝗲𝗱: • Syncs every 5 minutes in encrypted Parquet files • Messages, Workflow Executions, and Requests • Automatic backfills and hourly partitions • Works natively with Athena, Snowflake, BigQuery, Redshift Confidently build dashboards, surface notification logs to customers, or track entire customer lifecycle end-to-end. Docs in comments 👇 9 1 Comment Like Comment Share SuprSend 19,129 followers 1mo Report this post We're #hiring a new UI / UX Designer in Bengaluru, Karnataka. Apply today or share this post with your network. UI / UX Designer SuprSend, Bengaluru, Karnataka, India 7 Like Comment Share SuprSend 19,129 followers 1mo Edited Report this post 𝗖𝗮𝘁𝗲𝗴𝗼𝗿𝘆 𝗧𝗿𝗮𝗻𝘀𝗹𝗮𝘁𝗶𝗼𝗻𝘀 𝗳𝗼𝗿 𝗣𝗿𝗲𝗳𝗲𝗿𝗲𝗻𝗰𝗲 𝗖𝗲𝗻𝘁𝗲𝗿𝘀 🌍 In pursuit of seamless translations: preference categories now display in your user's locale. 𝗪𝗵𝗮𝘁 𝘁𝗵𝗶𝘀 𝗺𝗲𝗮𝗻𝘀: • One preference center works globally (no separate versions for each region) • Users make informed choices when they see categories in their preferred language • Add translations through Dashboard, API, or CLI • Smart fallback logic ensures something always displays (es-mx → es → en) If you're shipping notifications to a multilingual audience, this removes friction for both your users and your team. Docs in comments below 👇 13 1 Comment Like Comment Share SuprSend 19,129 followers 1mo Report this post 𝗛𝗼𝘄 𝗖𝗿𝗮𝘇𝘆𝗚𝗮𝗺𝗲𝘀 𝗖𝘂𝘁 𝗡𝗼𝘁𝗶𝗳𝗶𝗰𝗮𝘁𝗶𝗼𝗻 𝗗𝗲𝗽𝗹𝗼𝘆𝗺𝗲𝗻𝘁 𝗳𝗿𝗼𝗺 𝗪𝗲𝗲𝗸𝘀 𝘁𝗼 𝗛𝗼𝘂𝗿𝘀 CrazyGames serves 45M+ monthly players across 3,000+ browser games. But their in-house notification system held them back. 🎮 𝗧𝗵𝗲 𝗽𝗿𝗼𝗯𝗹𝗲𝗺: Building notifications required heavy engineering involvement. Even small template changes meant creating dev tickets and took 2 weeks to deploy. Product teams couldn't personalize or experiment fast without developer time. 𝗪𝗵𝗮𝘁 𝗰𝗵𝗮𝗻𝗴𝗲𝗱: CrazyGames adopted SuprSend to abstract notification development out of code. Templates, logic, and workflows shifted entirely to Product & Design. They also connected their database to SuprSend, allowing teams to create targeted cohorts by writing SQL — no data exports, no syncing delays, no engineering bottlenecks. 𝗧𝗵𝗲 𝗿𝗲𝘀𝘂𝗹𝘁: • Notification launches: weeks → hours • Self-serve campaigns with personalized game recommendations • A/B testing across email, push, and in-app — all unified • Product teams operate independently 🎥 Watch Jonas (VP of Product, CrazyGames) full story link in comments below. 33 4 Comments Like Comment Share SuprSend 19,129 followers 1mo Report this post We're #hiring a new Founders’ Office – Product Marketing in Bengaluru, Karnataka. Apply today or share this post with your network. Product Marketing Manager SuprSend, Bengaluru, Karnataka, India 9 1 Comment Like Comment Share SuprSend 19,129 followers 1mo Edited Report this post 𝗜𝗻𝘁𝗿𝗼𝗱𝘂𝗰𝗶𝗻𝗴 𝗧𝗿𝗮𝗻𝘀𝗹𝗮𝘁𝗶𝗼𝗻𝘀 𝗶𝗻 𝗡𝗼𝘁𝗶𝗳𝗶𝗰𝗮𝘁𝗶𝗼𝗻𝘀 Maintaining separate notification templates for every language doesn't scale. Change one template and you update all language versions manually. Translations solve this. Write one template that works across all languages. SuprSend automatically serves the right language based on user locale, with intelligent fallbacks. What's included: • Upload existing JSON translation files & manage through CLI/API • Smart translation keys with automatic language selection • Dynamic variables and pluralization handling • Namespaced keys to organize by feature • Change history with rollback support Documentation in the comments 👇 13 4 Comments Like Comment Share SuprSend 19,129 followers 1mo Report this post We're #hiring a new Product Manager in Bengaluru, Karnataka. Apply today or share this post with your network. Product Manager SuprSend, Bengaluru, Karnataka, India 4 Like Comment Share Join now to see what you are missing Find people you know at SuprSend Browse recommended jobs for you View all updates, news, and articles Join now Similar pages SuperSend Software Development Las Vegas, Nevada Crew Technology, Information and Internet Keploy 🐰 Technology, Information and Internet San Franciso, California KubeSense Software Development Austin, Texas Gushwork Software Development Brooklyn, New York Robylon AI Software Development San Francisco, California Cube Technology, Information and Internet Palo Alto, California Klaar Software Development San Francisco, California Bik.ai Technology, Information and Internet Zime Data Infrastructure and Analytics San Jose, CA Show more similar pages Show fewer similar pages Browse jobs Engineer jobs 555,845 open jobs Product Marketer jobs 9,108 open jobs Marketing Manager jobs 106,879 open jobs Scientist jobs 48,969 open jobs Machine Learning Engineer jobs 148,937 open jobs Developer jobs 258,935 open jobs Marketer jobs 37,677 open jobs Intelligence Specialist jobs 7,156 open jobs Intern jobs 71,196 open jobs Python Developer jobs 46,642 open jobs Senior Product Marketing Manager jobs 11,129 open jobs Analyst jobs 694,057 open jobs Manager jobs 1,880,925 open jobs Associate Product Manager jobs 76,300 open jobs General Engineer jobs 54,597 open jobs Software Engineer jobs 300,699 open jobs Associate jobs 1,091,945 open jobs Account Manager jobs 121,519 open jobs Marketing Specialist jobs 49,178 open jobs Digital Marketing Manager jobs 17,135 open jobs Show more jobs like this Show fewer jobs like this Funding SuprSend 1 total round Last Round Seed Oct 14, 2022 External Crunchbase Link for last round of funding US$ 1.0M Investors BoldCap + 4 Other investors See more info on crunchbase More searches More searches Engineer jobs Developer jobs Marketing Manager jobs Machine Learning Engineer jobs Intelligence Specialist jobs Scientist jobs Associate Product Manager jobs Analyst jobs Software Engineer jobs Intern jobs Product Management Intern jobs Talent Specialist jobs Global Marketing Manager jobs Consultant jobs Marketing Lead jobs Marketing Specialist jobs Product Marketer jobs Writer jobs Frontend Developer jobs Program Management Intern jobs Product Manager jobs Associate Project Manager jobs Network Developer jobs Account Manager jobs Digital Marketing Manager jobs Manager jobs Product Engineer jobs Senior Developer jobs Application Engineer jobs Customer Service Technician jobs Advocate jobs Linux Developer jobs Security Administrator jobs Web Developer jobs Senior Software Engineer jobs Full Stack Engineer jobs Data Scientist jobs Curriculum Developer jobs Sales Trainer jobs Science Specialist jobs Web Development Specialist jobs Security Engineer jobs Software Engineer Intern jobs Staff Software Engineer jobs Technology Engineer jobs Lead Software Engineer jobs Research Software Engineer jobs Business Development Associate jobs Technician jobs Content Specialist jobs iOS Developer jobs Senior Product Manager jobs User Interface Designer jobs PHP Developer jobs Product Designer jobs Director jobs Bookkeeper jobs User Experience Designer jobs Operations Engineer jobs Founder jobs LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language Agree & Join LinkedIn By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Sign in to see who you already know at SuprSend Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . | 2026-01-13T08:48:25 |
https://socket.io/docs/v4/server-api/ | Server API | Socket.IO Skip to main content Latest blog post (July 25, 2024): npm package provenance . Socket.IO Docs Guide Tutorial Examples Emit cheatsheet Server API Client API Ecosystem Help Troubleshooting Stack Overflow GitHub Discussions Slack News Blog Twitter Tools CDN Admin UI About FAQ Changelog Roadmap Become a sponsor 4.x 4.x 3.x 2.x Changelog English English Español Français Português (Brasil) 中文（中国） Search Socket.IO API Options API Version: 4.x On this page Server API Server Related documentation pages: installation initialization details of the server instance Constructor new Server(httpServer [, options] ) httpServer <http.Server> | <https.Server> options <Object> import { createServer } from "http" ; import { Server } from "socket.io" ; const httpServer = createServer ( ) ; const io = new Server ( httpServer , { // options } ) ; io . on ( "connection" , ( socket ) => { // ... } ) ; httpServer . listen ( 3000 ) ; The complete list of available options can be found here . new Server(port [, options] ) port <number> options <Object> import { Server } from "socket.io" ; const io = new Server ( 3000 , { // options } ) ; io . on ( "connection" , ( socket ) => { // ... } ) ; The complete list of available options can be found here . new Server(options) options <Object> import { Server } from "socket.io" ; const io = new Server ( { // options } ) ; io . on ( "connection" , ( socket ) => { // ... } ) ; io . listen ( 3000 ) ; The complete list of available options can be found here . Events Event: 'connect' Synonym of Event: "connection" . Event: 'connection' socket (Socket) socket connection with client Fired upon a connection from client. io . on ( "connection" , ( socket ) => { // ... } ) ; Event: 'new_namespace' namespace Namespace Fired when a new namespace is created: io . on ( "new_namespace" , ( namespace ) => { // ... } ) ; This can be useful for example: to attach a shared middleware to each namespace io . on ( "new_namespace" , ( namespace ) => { namespace . use ( myMiddleware ) ; } ) ; to track the dynamically created namespaces io . of ( / \/nsp-\w+ / ) ; io . on ( "new_namespace" , ( namespace ) => { console . log ( namespace . name ) ; } ) ; Attributes server.engine A reference to the underlying Engine.IO server. See here . server.sockets <Namespace> An alias for the main namespace ( / ). io . sockets . emit ( "hi" , "everyone" ) ; // is equivalent to io . of ( "/" ) . emit ( "hi" , "everyone" ) ; Methods server.adapter( [value] ) value <Adapter> Returns <Server> | <Adapter> Sets the adapter value . Defaults to an instance of the Adapter that ships with socket.io which is memory based. See socket.io-adapter . If no arguments are supplied this method returns the current value. import { Server } from "socket.io" ; import { createAdapter } from "@socket.io/redis-adapter" ; import { createClient } from "redis" ; const io = new Server ( ) ; const pubClient = createClient ( { host : "localhost" , port : 6379 } ) ; const subClient = pubClient . duplicate ( ) ; io . adapter ( createAdapter ( pubClient , subClient ) ) ; // redis@3 io . listen ( 3000 ) ; // redis@4 Promise . all ( [ pubClient . connect ( ) , subClient . connect ( ) ] ) . then ( ( ) => { io . listen ( 3000 ) ; } ) ; server.attach(httpServer [, options] ) httpServer <http.Server> | <https.Server> options <Object> Attaches the Server to an httpServer with the supplied options . import { createServer } from "http" ; import { Server } from "socket.io" ; const httpServer = createServer ( ) ; const io = new Server ( ) ; io . attach ( httpServer ) ; io . on ( "connection" , ( socket ) => { // ... } ) ; httpServer . listen ( 3000 ) ; server.attach(port [, options] ) port <number> options <Object> Attaches the Server on the given port with the supplied options . import { Server } from "socket.io" ; const io = new Server ( ) ; io . attach ( 3000 ) ; io . on ( "connection" , ( socket ) => { // ... } ) ; server.attachApp(app [, options] ) app <uws.App> options <Object> Attaches the Socket.IO server to an µWebSockets.js app: import { App } from "uWebSockets.js" ; import { Server } from "socket.io" ; const app = App ( ) ; const io = new Server ( ) ; io . attachApp ( app ) ; io . on ( "connection" , ( socket ) => { // ... } ) ; app . listen ( 3000 , ( token ) => { if ( ! token ) { console . warn ( "port already in use" ) ; } } ) ; server.bind(engine) engine <engine.Server> Returns <Server> Advanced use only. Binds the server to a specific engine.io Server (or compatible API) instance. import { createServer } from "node:http" ; import { Server as Engine } from "engine.io" ; import { Server } from "socket.io" ; const httpServer = createServer ( ( req , res ) => { res . writeHead ( 404 ) . end ( ) ; } ) ; const engine = new Engine ( ) ; engine . attach ( httpServer , { path : "/socket.io/" } ) ; const io = new Server ( ) ; io . bind ( engine ) ; httpServer . listen ( 3000 ) ; server.close( [callback] ) callback <Function> Closes the Socket.IO server and disconnect all clients. The callback argument is optional and will be called when all connections are closed. info This also closes the underlying HTTP server. import { createServer } from "http" ; import { Server } from "socket.io" ; const PORT = 3030 ; const io = new Server ( PORT ) ; io . close ( ) ; const httpServer = createServer ( ) ; httpServer . listen ( PORT ) ; // PORT is free to use io . attach ( httpServer ) ; note Only closing the underlying HTTP server is not sufficient, as it will only prevent the server from accepting new connections but clients connected with WebSocket will not be disconnected right away. Reference: https://nodejs.org/api/http.html#serverclosecallback server.disconnectSockets( [close] ) Added in v4.0.0 Alias for io.of("/").disconnectSockets(close) . // make all Socket instances disconnect io . disconnectSockets ( ) ; // make all Socket instances in the "room1" room disconnect (and close the low-level connection) io . in ( "room1" ) . disconnectSockets ( true ) ; tip This method also works within a cluster of multiple Socket.IO servers, with a compatible adapter like the Postgres adapter . In that case, if you only want to affect the socket instances on the given node, you need to use the local flag: // make all Socket instances that are currently connected on the given node disconnect io . local . disconnectSockets ( ) ; See here . server.emit(eventName [, ...args] ) History Version Changes v4.5.0 io.emit() now supports acknowledgements. v1.0.0 Initial implementation. eventName <string> | <symbol> args any[] Returns true Emits an event to all connected clients in the main namespace. io . emit ( "hello" ) ; Any number of parameters can be included, and all serializable data structures are supported: io . emit ( "hello" , 1 , "2" , { "3" : 4 } , Buffer . from ( [ 5 ] ) ) ; And on the receiving side: socket . on ( "hello" , ( arg1 , arg2 , arg3 , arg4 ) => { console . log ( arg1 ) ; // 1 console . log ( arg2 ) ; // "2" console . log ( arg3 ) ; // { "3": 4 } console . log ( arg4 ) ; // ArrayBuffer or Buffer, depending on the platform } ) ; info The arguments will automatically be serialized, so calling JSON.stringify() is not needed. You can use to() and except() to send the packet to specific clients: // the “hello” event will be broadcast to all connected clients that are either // in the "room1" room or in the "room2" room, excluding those in the "room3" room io . to ( "room1" ) . to ( "room2" ) . except ( "room3" ) . emit ( "hello" ) ; Starting with version 4.5.0 , it is now possible to use acknowledgements when broadcasting: io . timeout ( 10000 ) . emit ( "some-event" , ( err , responses ) => { if ( err ) { // some clients did not acknowledge the event in the given delay } else { console . log ( responses ) ; // one response per client } } ) ; caution Calling timeout() is mandatory in that case. server.emitWithAck(eventName [, ...args] ) Added in v4.6.0 eventName <string> | <symbol> args any[] Returns Promise<any[]> Promised-based version of broadcasting and expecting an acknowledgement from all targeted clients: try { const responses = await io . timeout ( 10000 ) . emitWithAck ( "some-event" ) ; console . log ( responses ) ; // one response per client } catch ( e ) { // some clients did not acknowledge the event in the given delay } The example above is equivalent to: io . timeout ( 10000 ) . emit ( "some-event" , ( err , responses ) => { if ( err ) { // some clients did not acknowledge the event in the given delay } else { console . log ( responses ) ; // one response per client } } ) ; And on the receiving side: socket . on ( "some-event" , ( callback ) => { callback ( "got it" ) ; // only one argument is expected } ) ; server.except(rooms) Added in v4.0.0 rooms <string> | <string[]> Returns BroadcastOperator Sets a modifier for a subsequent event emission that the event will only be broadcast to clients that have not joined the given rooms . // the "foo" event will be broadcast to all connected clients, except the ones that are in the "room-101" room io . except ( "room-101" ) . emit ( "foo" , "bar" ) ; // with an array of rooms io . except ( [ "room-101" , "room-102" ] ) . emit ( "foo" , "bar" ) ; // with multiple chained calls io . except ( "room-101" ) . except ( "room-102" ) . emit ( "foo" , "bar" ) ; server.fetchSockets() Added in v4.0.0 Alias for io.of("/").fetchSocket() . // return all Socket instances of the main namespace const sockets = await io . fetchSockets ( ) ; // return all Socket instances in the "room1" room of the main namespace const sockets = await io . in ( "room1" ) . fetchSockets ( ) ; Sample usage: io . on ( "connection" , ( socket ) => { const userId = computeUserId ( socket ) ; socket . join ( userId ) ; socket . on ( "disconnect" , async ( ) => { const sockets = await io . in ( userId ) . fetchSockets ( ) ; if ( sockets . length === 0 ) { // no more active connections for the given user } } ) ; } ) ; tip This method also works within a cluster of multiple Socket.IO servers, with a compatible adapter like the Postgres adapter . In that case, if you only want to return the socket instances on the given node, you need to use the local flag: // return all Socket instances that are currently connected on the given node const sockets = await io . local . fetchSockets ( ) ; See here . server.in(room) Added in v1.0.0 Synonym of server.to(room) , but might feel clearer in some cases: // disconnect all clients in the "room-101" room io . in ( "room-101" ) . disconnectSockets ( ) ; server.listen(httpServer [, options] ) Synonym of server.attach(httpServer[, options]) . server.listen(port [, options] ) Synonym of server.attach(port[, options]) . server.of(nsp) nsp <string> | <RegExp> | <Function> Returns <Namespace> Initializes and retrieves the given Namespace by its pathname identifier nsp . If the namespace was already initialized it returns it immediately. const adminNamespace = io . of ( "/admin" ) ; A regex or a function can also be provided, in order to create namespace in a dynamic way: const dynamicNsp = io . of ( / ^\/dynamic-\d+$ / ) . on ( "connection" , ( socket ) => { const newNamespace = socket . nsp ; // newNamespace.name === "/dynamic-101" // broadcast to all clients in the given sub-namespace newNamespace . emit ( "hello" ) ; } ) ; // client-side const socket = io ( "/dynamic-101" ) ; // broadcast to all clients in each sub-namespace dynamicNsp . emit ( "hello" ) ; // use a middleware for each sub-namespace dynamicNsp . use ( ( socket , next ) => { /* ... */ } ) ; With a function: io . of ( ( name , query , next ) => { // the checkToken method must return a boolean, indicating whether the client is able to connect or not. next ( null , checkToken ( query . token ) ) ; } ) . on ( "connection" , ( socket ) => { /* ... */ } ) ; server.on(eventName, listener) Inherited from the EventEmitter class . eventName <string> | <symbol> listener <Function> Returns <Server> Adds the listener function to the end of the listeners array for the event named eventName . Available events: connection new_namespace any custom event from the serverSideEmit method io . on ( "connection" , ( socket ) => { // ... } ) ; server.onconnection(socket) socket <engine.Socket> Returns <Server> Advanced use only. Creates a new socket.io client from the incoming engine.io (or compatible API) Socket . import { Server } from "socket.io" ; import { Server as Engine } from "engine.io" ; const engine = new Engine ( ) ; const io = new Server ( ) ; engine . on ( "connection" , ( socket ) => { io . onconnection ( socket ) ; } ) ; engine . listen ( 3000 ) ; server.path( [value] ) value <string> Returns <Server> | <string> Sets the path value under which engine.io and the static files will be served. Defaults to /socket.io/ . If no arguments are supplied this method returns the current value. import { Server } from "socket.io" ; const io = new Server ( ) ; io . path ( "/myownpath/" ) ; danger The path value must match the one on the client side: import { io } from "socket.io-client" ; const socket = io ( { path : "/myownpath/" } ) ; server.serveClient( [value] ) value <boolean> Returns <Server> | <boolean> If value is true the attached server will serve the client files. Defaults to true . This method has no effect after listen is called. If no arguments are supplied this method returns the current value. import { Server } from "socket.io" ; const io = new Server ( ) ; io . serveClient ( false ) ; io . listen ( 3000 ) ; server.serverSideEmit(eventName [, ...args][, ack] ) Added in v4.1.0 Alias for: io.of("/").serverSideEmit(/* ... */); eventName <string> args <any[]> ack <Function> Returns true Sends a message to the other Socket.IO servers of the cluster . Syntax: io . serverSideEmit ( "hello" , "world" ) ; And on the receiving side: io . on ( "hello" , ( arg1 ) => { console . log ( arg1 ) ; // prints "world" } ) ; Acknowledgements are supported too: // server A io . serverSideEmit ( "ping" , ( err , responses ) => { console . log ( responses [ 0 ] ) ; // prints "pong" } ) ; // server B io . on ( "ping" , ( cb ) => { cb ( "pong" ) ; } ) ; Notes: the connection , connect and new_namespace strings are reserved and cannot be used in your application. you can send any number of arguments, but binary structures are currently not supported (the array of arguments will be JSON.stringify -ed) Example: io . serverSideEmit ( "hello" , "world" , 1 , "2" , { 3 : "4" } ) ; the acknowledgement callback might be called with an error, if the other Socket.IO servers do not respond after a given delay io . serverSideEmit ( "ping" , ( err , responses ) => { if ( err ) { // at least one Socket.IO server has not responded // the 'responses' array contains all the responses already received though } else { // success! the 'responses' array contains one object per other Socket.IO server in the cluster } } ) ; server.serverSideEmitWithAck(eventName [, ...args] ) Added in v4.6.0 Alias for: io.of("/").serverSideEmitWithAck(/* ... */); eventName <string> args <any[]> ack <Function> Returns Promise<any[]> Promised-based version of broadcasting and expecting an acknowledgement from the other Socket.IO servers of the cluster . try { const responses = await io . serverSideEmitWithAck ( "some-event" ) ; console . log ( responses ) ; // one response per server (except itself) } catch ( e ) { // some servers did not acknowledge the event in the given delay } The example above is equivalent to: io . serverSideEmit ( "some-event" , ( err , responses ) => { if ( err ) { // some servers did not acknowledge the event in the given delay } else { console . log ( responses ) ; // one response per server (except itself) } } ) ; And on the receiving side: io . on ( "some-event" , ( callback ) => { callback ( "got it" ) ; // only one argument is expected } ) ; server.socketsJoin(rooms) Added in v4.0.0 Alias for io.of("/").socketsJoin(rooms) . // make all Socket instances join the "room1" room io . socketsJoin ( "room1" ) ; // make all Socket instances in the "room1" room join the "room2" and "room3" rooms io . in ( "room1" ) . socketsJoin ( [ "room2" , "room3" ] ) ; // this also works with a single socket ID io . in ( theSocketId ) . socketsJoin ( "room1" ) ; tip This method also works within a cluster of multiple Socket.IO servers, with a compatible adapter like the Postgres adapter . In that case, if you only want to affect the socket instances on the given node, you need to use the local flag: // make all Socket instances that are currently connected on the given node join the "room1" room io . local . socketsJoin ( "room1" ) ; See here . server.socketsLeave(rooms) Added in v4.0.0 Alias for io.of("/").socketsLeave(rooms) . // make all Socket instances leave the "room1" room io . socketsLeave ( "room1" ) ; // make all Socket instances in the "room1" room leave the "room2" and "room3" rooms io . in ( "room1" ) . socketsLeave ( [ "room2" , "room3" ] ) ; // this also works with a single socket ID io . in ( theSocketId ) . socketsLeave ( "room1" ) ; tip This method also works within a cluster of multiple Socket.IO servers, with a compatible adapter like the Postgres adapter . In that case, if you only want to affect the socket instances on the given node, you need to use the local flag: // make all Socket instances that are currently connected on the given node leave the "room1" room io . local . socketsLeave ( "room1" ) ; See here . server.timeout(value) Added in v4.5.0 value <number> Returns BroadcastOperator Sets a modifier for a subsequent event emission that the callback will be called with an error when the given number of milliseconds have elapsed without an acknowledgement from all targeted clients: io . timeout ( 10000 ) . emit ( "some-event" , ( err , responses ) => { if ( err ) { // some clients did not acknowledge the event in the given delay } else { console . log ( responses ) ; // one response per client } } ) ; server.to(room) History Version Changes v4.0.0 Allow to pass an array of rooms. v1.0.0 Initial implementation. room <string> | <string[]> Returns BroadcastOperator for chaining Sets a modifier for a subsequent event emission that the event will only be broadcast to clients that have joined the given room . To emit to multiple rooms, you can call to several times. // the “foo” event will be broadcast to all connected clients in the “room-101” room io . to ( "room-101" ) . emit ( "foo" , "bar" ) ; // with an array of rooms (a client will be notified at most once) io . to ( [ "room-101" , "room-102" ] ) . emit ( "foo" , "bar" ) ; // with multiple chained calls io . to ( "room-101" ) . to ( "room-102" ) . emit ( "foo" , "bar" ) ; server.use(fn) Added in v1.0.0 Alias for io.of("/").use(fn) . fn <Function> Registers a middleware for the main namespace, which is a function that gets executed for every incoming Socket , and receives as parameters the socket and a function to optionally defer execution to the next registered middleware. Errors passed to middleware callbacks are sent as special connect_error packets to clients. Server io . use ( ( socket , next ) => { const err = new Error ( "not authorized" ) ; err . data = { content : "Please retry later" } ; // additional details next ( err ) ; } ) ; Client socket . on ( "connect_error" , err => { console . log ( err instanceof Error ) ; // true console . log ( err . message ) ; // not authorized console . log ( err . data ) ; // { content: "Please retry later" } } ) ; More information can be found here . info If you are looking for Express middlewares, please check this section . Namespace Represents a pool of sockets connected under a given scope identified by a pathname (eg: /chat ). More information can be found here . Attributes namespace.adapter <Adapter> The "Adapter" used for the namespace. Note: the adapter of the main namespace can be accessed with io.of("/").adapter . More information about it here . const adapter = io . of ( "/my-namespace" ) . adapter ; namespace.name <string> The namespace identifier property. namespace.sockets Map<SocketId, Socket> A map of Socket instances that are connected to this namespace. // number of sockets in this namespace (on this node) const socketCount = io . of ( "/admin" ) . sockets . size ; Events Event: 'connect' Synonym of Event: "connection" . Event: 'connection' socket <Socket> Fired upon a connection from client. // main namespace io . on ( "connection" , ( socket ) => { // ... } ) ; // custom namespace io . of ( "/admin" ) . on ( "connection" , ( socket ) => { // ... } ) ; Methods namespace.allSockets() Returns Promise<Set<SocketId>> caution This method will be removed in the next major release, please use serverSideEmit() or fetchSockets() instead. Gets a list of socket IDs connected to this namespace (across all nodes if applicable). // all sockets in the main namespace const ids = await io . allSockets ( ) ; // all sockets in the main namespace and in the "user:1234" room const ids = await io . in ( "user:1234" ) . allSockets ( ) ; // all sockets in the "chat" namespace const ids = await io . of ( "/chat" ) . allSockets ( ) ; // all sockets in the "chat" namespace and in the "general" room const ids = await io . of ( "/chat" ) . in ( "general" ) . allSockets ( ) ; namespace.disconnectSockets( [close] ) Added in v4.0.0 close <boolean> whether to close the underlying connection Returns void Makes the matching Socket instances disconnect. // make all Socket instances disconnect io . disconnectSockets ( ) ; // make all Socket instances in the "room1" room disconnect (and discard the low-level connection) io . in ( "room1" ) . disconnectSockets ( true ) ; // make all Socket instances in the "room1" room of the "admin" namespace disconnect io . of ( "/admin" ) . in ( "room1" ) . disconnectSockets ( ) ; // this also works with a single socket ID io . of ( "/admin" ) . in ( theSocketId ) . disconnectSockets ( ) ; namespace.emit(eventName [, ...args] ) History Version Changes v4.5.0 io.emit() now supports acknowledgements. v1.0.0 Initial implementation. eventName <string> | <symbol> args any[] Returns true Emits an event to all connected clients in the given namespace. io . of ( "/chat" ) . emit ( "hello" ) ; Any number of parameters can be included, and all serializable data structures are supported: io . of ( "/chat" ) . emit ( "hello" , 1 , "2" , { "3" : 4 } , Buffer . from ( [ 5 ] ) ) ; And on the receiving side: socket . on ( "hello" , ( arg1 , arg2 , arg3 , arg4 ) => { console . log ( arg1 ) ; // 1 console . log ( arg2 ) ; // "2" console . log ( arg3 ) ; // { "3": 4 } console . log ( arg4 ) ; // ArrayBuffer or Buffer, depending on the platform } ) ; info The arguments will automatically be serialized, so calling JSON.stringify() is not needed. You can use to() and except() to send the packet to specific clients: // the “hello” event will be broadcast to all connected clients that are either // in the "room1" room or in the "room2" room, excluding those in the "room3" room io . of ( "/chat" ) . to ( "room1" ) . to ( "room2" ) . except ( "room3" ) . emit ( "hello" ) ; Starting with version 4.5.0 , it is now possible to use acknowledgements when broadcasting: io . of ( "/chat" ) . timeout ( 10000 ) . emit ( "some-event" , ( err , responses ) => { if ( err ) { // some clients did not acknowledge the event in the given delay } else { console . log ( responses ) ; // one response per client } } ) ; caution Calling timeout() is mandatory in that case. namespace.emitWithAck(eventName [, ...args] ) Added in v4.6.0 eventName <string> | <symbol> args any[] Returns Promise<any[]> Promised-based version of broadcasting and expecting an acknowledgement from all targeted clients in the given namespace: try { const responses = await io . of ( "/chat" ) . timeout ( 10000 ) . emitWithAck ( "some-event" ) ; console . log ( responses ) ; // one response per client } catch ( e ) { // some clients did not acknowledge the event in the given delay } The example above is equivalent to: io . of ( "/chat" ) . timeout ( 10000 ) . emit ( "some-event" , ( err , responses ) => { if ( err ) { // some clients did not acknowledge the event in the given delay } else { console . log ( responses ) ; // one response per client } } ) ; And on the receiving side: socket . on ( "some-event" , ( callback ) => { callback ( "got it" ) ; // only one argument is expected } ) ; namespace.except(rooms) Added in v4.0.0 rooms <string> | <string[]> Returns BroadcastOperator Sets a modifier for a subsequent event emission that the event will only be broadcast to clients that have not joined the given rooms . const myNamespace = io . of ( "/my-namespace" ) ; // the "foo" event will be broadcast to all connected clients, except the ones that are in the "room-101" room myNamespace . except ( "room-101" ) . emit ( "foo" , "bar" ) ; // with an array of rooms myNamespace . except ( [ "room-101" , "room-102" ] ) . emit ( "foo" , "bar" ) ; // with multiple chained calls myNamespace . except ( "room-101" ) . except ( "room-102" ) . emit ( "foo" , "bar" ) ; namespace.fetchSockets() Added in v4.0.0 Returns Socket[] | RemoteSocket[] Returns the matching Socket instances: // return all Socket instances in the main namespace const sockets = await io . fetchSockets ( ) ; // return all Socket instances in the "room1" room of the main namespace const sockets = await io . in ( "room1" ) . fetchSockets ( ) ; // return all Socket instances in the "room1" room of the "admin" namespace const sockets = await io . of ( "/admin" ) . in ( "room1" ) . fetchSockets ( ) ; // this also works with a single socket ID const sockets = await io . in ( theSocketId ) . fetchSockets ( ) ; The sockets variable in the example above is an array of objects exposing a subset of the usual Socket class: for ( const socket of sockets ) { console . log ( socket . id ) ; console . log ( socket . handshake ) ; console . log ( socket . rooms ) ; console . log ( socket . data ) ; socket . emit ( /* ... */ ) ; socket . join ( /* ... */ ) ; socket . leave ( /* ... */ ) ; socket . disconnect ( /* ... */ ) ; } The data attribute is an arbitrary object that can be used to share information between Socket.IO servers: // server A io . on ( "connection" , ( socket ) => { socket . data . username = "alice" ; } ) ; // server B const sockets = await io . fetchSockets ( ) ; console . log ( sockets [ 0 ] . data . username ) ; // "alice" Important note : this method (and socketsJoin , socketsLeave and disconnectSockets too) is compatible with the Redis adapter (starting with socket.io-redis@6.1.0 ), which means that they will work across Socket.IO servers. namespace.in(room) Added in v1.0.0 Synonym of namespace.to(room) , but might feel clearer in some cases: const myNamespace = io . of ( "/my-namespace" ) ; // disconnect all clients in the "room-101" room myNamespace . in ( "room-101" ) . disconnectSockets ( ) ; namespace.serverSideEmit(eventName [, ...args][, ack] ) Added in v4.1.0 eventName <string> args <any[]> ack <Function> Returns true Sends a message to the other Socket.IO servers of the cluster . Syntax: io . of ( "/chat" ) . serverSideEmit ( "hello" , "world" ) ; And on the receiving side: io . of ( "/chat" ) . on ( "hello" , ( arg1 ) => { console . log ( arg1 ) ; // prints "world" } ) ; Acknowledgements are supported too: // server A io . of ( "/chat" ) . serverSideEmit ( "ping" , ( err , responses ) => { console . log ( responses [ 0 ] ) ; // prints "pong" } ) ; // server B io . of ( "/chat" ) . on ( "ping" , ( cb ) => { cb ( "pong" ) ; } ) ; Notes: the connection , connect and new_namespace strings are reserved and cannot be used in your application. you can send any number of arguments, but binary structures are currently not supported (the array of arguments will be JSON.stringify -ed) Example: io . of ( "/chat" ) . serverSideEmit ( "hello" , "world" , 1 , "2" , { 3 : "4" } ) ; the acknowledgement callback might be called with an error, if the other Socket.IO servers do not respond after a given delay io . of ( "/chat" ) . serverSideEmit ( "ping" , ( err , responses ) => { if ( err ) { // at least one Socket.IO server has not responded // the 'responses' array contains all the responses already received though } else { // success! the 'responses' array contains one object per other Socket.IO server in the cluster } } ) ; namespace.serverSideEmitWithAck(eventName [, ...args] ) Added in v4.6.0 eventName <string> args <any[]> ack <Function> Returns Promise<any[]> Promised-based version of broadcasting and expecting an acknowledgement from the other Socket.IO servers of the cluster . try { const responses = await io . of ( "/chat" ) . serverSideEmitWithAck ( "some-event" ) ; console . log ( responses ) ; // one response per server (except itself) } catch ( e ) { // some servers did not acknowledge the event in the given delay } The example above is equivalent to: io . of ( "/chat" ) . serverSideEmit ( "some-event" , ( err , responses ) => { if ( err ) { // some servers did not acknowledge the event in the given delay } else { console . log ( responses ) ; // one response per server (except itself) } } ) ; And on the receiving side: io . of ( "/chat" ) . on ( "some-event" , ( callback ) => { callback ( "got it" ) ; // only one argument is expected } ) ; namespace.socketsJoin(rooms) Added in v4.0.0 rooms <string> | <string[]> Returns void Makes the matching Socket instances join the specified rooms: // make all Socket instances join the "room1" room io . socketsJoin ( "room1" ) ; // make all Socket instances in the "room1" room join the "room2" and "room3" rooms io . in ( "room1" ) . socketsJoin ( [ "room2" , "room3" ] ) ; // make all Socket instances in the "room1" room of the "admin" namespace join the "room2" room io . of ( "/admin" ) . in ( "room1" ) . socketsJoin ( "room2" ) ; // this also works with a single socket ID io . in ( theSocketId ) . socketsJoin ( "room1" ) ; More information can be found here . namespace.socketsLeave(rooms) Added in v4.0.0 rooms <string> | <string[]> Returns void Makes the matching Socket instances leave the specified rooms: // make all Socket instances leave the "room1" room io . socketsLeave ( "room1" ) ; // make all Socket instances in the "room1" room leave the "room2" and "room3" rooms io . in ( "room1" ) . socketsLeave ( [ "room2" , "room3" ] ) ; // make all Socket instances in the "room1" room of the "admin" namespace leave the "room2" room io . of ( "/admin" ) . in ( "room1" ) . socketsLeave ( "room2" ) ; // this also works with a single socket ID io . in ( theSocketId ) . socketsLeave ( "room1" ) ; namespace.timeout(value) Added in v4.5.0 value <number> Returns BroadcastOperator Sets a modifier for a subsequent event emission that the callback will be called with an error when the given number of milliseconds have elapsed without an acknowledgement from the client: io . of ( "/chat" ) . timeout ( 10000 ) . emit ( "some-event" , ( err , responses ) => { if ( err ) { // some clients did not acknowledge the event in the given delay } else { console . log ( responses ) ; // one response per client } } ) ; namespace.to(room) History Version Changes v4.0.0 Allow to pass an array of rooms. v1.0.0 Initial implementation. room <string> | <string[]> Returns BroadcastOperator for chaining Sets a modifier for a subsequent event emission that the event will only be broadcast to clients that have joined the given room . To emit to multiple rooms, you can call to several times. const myNamespace = io . of ( "/my-namespace" ) ; // the “foo” event will be broadcast to all connected clients in the “room-101” room myNamespace . to ( "room-101" ) . emit ( "foo" , "bar" ) ; // with an array of rooms (a client will be notified at most once) myNamespace . to ( [ "room-101" , "room-102" ] ) . emit ( "foo" , "bar" ) ; // with multiple chained calls myNamespace . to ( "room-101" ) . to ( "room-102" ) . emit ( "foo" , "bar" ) ; namespace.use(fn) Added in v1.0.0 fn <Function> Registers a middleware for the given namespace, which is a function that gets executed for every incoming Socket , and receives as parameters the socket and a function to optionally defer execution to the next registered middleware. Errors passed to middleware callbacks are sent as special connect_error packets to clients. Server io . of ( "/chat" ) . use ( ( socket , next ) => { const err = new Error ( "not authorized" ) ; err . data = { content : "Please retry later" } ; // additional details next ( err ) ; } ) ; Client socket . on ( "connect_error" , err => { console . log ( err instanceof Error ) ; // true console . log ( err . message ) ; // not authorized console . log ( err . data ) ; // { content: "Please retry later" } } ) ; More information can be found here . info If you are looking for Express middlewares, please check this section . Flags Flag: 'local' Sets a modifier for a subsequent event emission that the event data will only be broadcast to the current node (when scaling to multiple nodes ). io . local . emit ( "an event" , { some : "data" } ) ; Flag: 'volatile' Sets a modifier for a subsequent event emission that the event data may be lost if the clients are not ready to receive messages (because of network slowness or other issues, or because they’re connected through long polling and is in the middle of a request-response cycle). io . volatile . emit ( "an event" , { some : "data" } ) ; // the clients may or may not receive it Socket A Socket is the fundamental class for interacting with browser clients. A Socket belongs to a certain Namespace (by default / ) and uses an underlying Client to communicate. It should be noted the Socket doesn't relate directly to the actual underlying TCP/IP socket and it is only the name of the class. Within each Namespace , you can also define arbitrary channels (called room ) that the Socket can join and leave. That provides a convenient way to broadcast to a group of Socket s (see Socket#to below). The Socket class inherits from EventEmitter . The Socket class overrides the emit method, and does not modify any other EventEmitter method. All methods documented here which also appear as EventEmitter methods (apart from emit ) are implemented by EventEmitter , and documentation for EventEmitter applies. More information can be found here . Events Event: 'disconnect' reason <string> the reason of the disconnection (either client or server-side) Fired upon disconnection. io . on ( "connection" , ( socket ) => { socket . on ( "disconnect" , ( reason ) => { // ... } ) ; } ) ; Possible reasons: Reason Description server namespace disconnect The socket was forcefully disconnected with socket.disconnect() . client namespace disconnect The client has manually disconnected the socket using socket.disconnect() . server shutting down The server is, well, shutting down. ping timeout The client did not send a PONG packet in the pingTimeout delay. transport close The connection was closed (example: the user has lost connection, or the network was changed from WiFi to 4G). transport error The connection has encountered an error. parse error The server has received an invalid packet from the client. forced close The server has received an invalid packet from the client. forced server close The client did not join a namespace in time (see the connectTimeout option) and was forcefully closed. Event: 'disconnecting' Added in v1.5.0 reason <string> the reason of the disconnection (either client or server-side) Fired when the client is going to be disconnected (but hasn't left its rooms yet). io . on ( "connection" , ( socket ) => { socket . on ( "disconnecting" , ( reason ) => { console . log ( socket . rooms ) ; // Set { ... } } ) ; } ) ; With an asynchronous handler, you will need to create a copy of the rooms attribute: io . on ( "connection" , ( socket ) => { socket . on ( "disconnecting" , async ( reason ) => { const rooms = new Set ( socket . rooms ) ; await someLongRunningOperation ( ) ; // socket.rooms will be empty there console . log ( rooms ) ; } ) ; } ) ; caution Those events, along with connect , connect_error , newListener and removeListener , are special events that shouldn't be used in your application: // BAD, will throw an error socket . emit ( "disconnect" ) ; Attributes socket.client <Client> A reference to the underlying Client object. socket.conn <engine.Socket> A reference to the underlying Client transport connection (engine.io Socket object). This allows access to the IO transport layer, which still (mostly) abstracts the actual TCP/IP socket. io . on ( "connection" , ( socket ) => { console . log ( "initial transport" , socket . conn . transport . name ) ; // prints "polling" socket . conn . once ( "upgrade" , ( ) => { // called when the transport is upgraded (i.e. from HTTP long-polling to WebSocket) console . log ( "upgraded transport" , socket . conn . transport . name ) ; // prints "websocket" } ) ; socket . conn . on ( "packet" , ( { type , data } ) => { // called for each packet received } ) ; socket . conn . on ( "packetCreate" , ( { type , data } ) => { // called for each packet sent } ) ; socket . conn . on ( "drain" , ( ) => { // called when the write buffer is drained } ) ; socket . conn . on ( "heartbeat" , ( ) => { // called after each round trip of the heartbeat mechanism console . log ( "heartbeat" ) ; } ) ; socket . conn . on ( "close" , ( reason ) => { // called when the underlying connection is closed } ) ; } ) ; socket.data Added in v4.0.0 An arbitrary object that can be used in conjunction with the fetchSockets() utility method: io . on ( "connection" , ( socket ) => { socket . data . username = "alice" ; } ) ; const sockets = await io . fetchSockets ( ) ; console . log ( sockets [ 0 ] . data . username ) ; // "alice" tip This also works within a Socket.IO cluster, with a compatible adapter like the Postgres adapter . socket.handshake <Object> The handshake details: Field Type Description headers IncomingHttpHeaders The headers sent as part of the handshake. time <string> The date of creation (as string). address <string> The ip address of the client. xdomain <boolean> Whether the connection is cross-domain. secure <boolean> Whether the connection is made over SSL. issued <number> The date of creation (as unix timestamp). url <string> The request URL string. query Record<string, string or string[]> The query parameters of the first request. auth Record<string, any> The authentication payload. See also here . Usage: io . use ( ( socket , next ) => { let handshake = socket . handshake ; // ... } ) ; io . on ( "connection" , ( socket ) => { let handshake = socket . handshake ; // ... } ) ; Example: const handshake = { headers : { "user-agent" : "node-XMLHttpRequest" , accept : "*/*" , host : "localhost:3000" , connection : "close" } , time : "Wed Jan 01 2020 01:00:00 GMT+0100 (Central European Standard Time)" , address : "::ffff:127.0.0.1" , xdomain : false , secure : false , issued : 1577836800000 , url : "/socket.io/?EIO=4&transport=polling&t=OPAfXv5&b64=1" , query : { EIO : "4" , transport : "polling" , t : "OPAfXv5" , b64 : "1" } , auth : { } } Note: the headers attribute refers to the headers of the first HTTP request of the session, and won't be updated by the subsequent HTTP requests. io . on ( "connection" , ( socket ) => { console . log ( socket . handshake . headers === socket . request . headers ) ; // prints "true" } ) ; socket.id <string> A unique identifier for the session, that comes from the underlying Client . caution The id attribute is an ephemeral ID that is not meant to be used in your application (or only for debugging purposes) because: this ID is regenerated after each reconnection (for example when the WebSocket connection is severed, or when the user refreshes the page) two different browser tabs will have two different IDs there is no message queue stored for a given ID on the server (i.e. if the client is disconnected, the messages sent from the server to this ID are lost) Please use a regular session ID instead (either sent in a cookie, or stored in the localStorage and sent in the auth payload). See also: Part II of our private message guide How to deal with cookies socket.recovered Added in v4.6.0 <boolean> Whether the connection state was successfully recovered during the last reconnection. io . on ( "connection" , ( socket ) => { if ( socket . recovered ) { // recovery was successful: socket.id, socket.rooms and socket.data were restored } else { // new or unrecoverable session } } ) ; More information about this feature here . socket.request <http.IncomingMessage> A getter proxy that returns the reference to the request that originated the underlying engine.io Client . Useful for accessing request headers such as Cookie or User-Agent . import { parse } from "cookie" ; io . on ( "connection" , ( socket ) => { const cookies = parse ( socket . request . headers . cookie || "" ) ; } ) ; Note: socket.request refers to the first HTTP request of the session, and won't be updated by the subsequent HTTP requests. io . on ( "connection" , ( socket ) => { console . log ( socket . request . headers === socket . handshake . headers ) ; // prints "true" } ) ; If you don't need this reference, you can discard it in order to reduce the memory footprint: io . on ( "connection" , ( socket ) => { delete socket . conn . request ; } ) ; socket.rooms Set<string> A Set of strings identifying the rooms this client is in. io . on ( "connection" , ( socket ) => { console . log ( socket . rooms ) ; // Set { <socket.id> } socket . join ( "room1" ) ; console . log ( socket . rooms ) ; // Set { <socket.id>, "room1" } } ) ; Methods socket.compress(value) value <boolean> whether to following packet will be compressed Returns Socket for chaining Sets a modifier for a subsequent event emission that the event data will only be compressed if the value is true . Defaults to true when you don't call the method. io . on ( "connection" , ( socket ) => { socket . compress ( false ) . emit ( "uncompressed" , "that's rough" ) ; } ) ; socket.disconnect( [close] ) close <boolean> whether to close the underlying connection Returns Socket Disconnects this socket. If value of close is true , closes the underlying connection. Otherwise, it just disconnects the namespace. io . on ( "connection" , ( socket ) => { setTimeout ( ( ) => socket . disconnect ( true ) , 5000 ) ; } ) ; socket.emit(eventName [, ...args][, ack] ) (overrides EventEmitter.emit ) eventName <string> | <symbol> args <any[]> ack <Function> Returns true Emits an event to the socket identified by the string name. Any other parameters can be included. All serializable data structures are supported, including Buffer . io . on ( "connection" , ( ) => { socket . emit ( "hello" , "world" ) ; socket . emit ( "with-binary" , 1 , "2" , { 3 : "4" , 5 : Buffer . from ( [ 6 ] ) } ) ; } ) ; The ack argument is optional and will be called with the client's answer. Server io . on ( "connection" , ( socket ) => { socket . emit ( "hello" , "world" , ( response ) => { console . log ( response ) ; // "got it" } ) ; } ) ; Client socket . on ( "hello" , ( arg , callback ) => { console . log ( arg ) ; // "world" callback ( "got it" ) ; } ) ; socket.emitWithAck(eventName [, ...args] ) Added in v4.6.0 eventName <string> | <symbol> args any[] Returns Promise<any> Promised-based version of emitting and expecting an acknowledgement from the given client: io . on ( "connection" , async ( socket ) => { // without timeout const response = await socket . emitWithAck ( "hello" , "world" ) ; // with a specific timeout try { const response = await socket . timeout ( 10000 ) . emitWithAck ( "hello" , "world" ) ; } catch ( err ) { // the client did not acknowledge the event in the given delay } } ) ; The example above is equivalent to: io . on ( "connection" , ( socket ) => { // without timeout socket . emit ( "hello" , "world" , ( val ) => { // ... } ) ; // with a specific timeout socket . timeout ( 10000 ) . emit ( "hello" , "world" , ( err , val ) => { // ... } ) ; } ) ; And on the receiving side: socket . on ( "hello" , ( arg1 , callback ) => { callback ( "got it" ) ; // only one argument is expected } ) ; socket.eventNames() Inherited from EventEmitter (along with other methods not mentioned here). See the Node.js documentation for the events module. socket.except(rooms) Added in v4.0.0 rooms <string> | <string[]> Returns BroadcastOperator Sets a modifier for a subsequent event emission that the event will only be broadcast to clients that have not joined the given rooms (the socket itself being excluded). // to al | 2026-01-13T08:48:25 |
https://www.linkedin.com/company/suprsend?trk=organization_guest_main-feed-card_feed-reaction-header | SuprSend | LinkedIn Skip to main content LinkedIn Top Content People Learning Jobs Games Sign in Join now SuprSend Software Development San Francisco, CA 19,129 followers Communication Infrastructure for dev & product teams See jobs Follow Discover all 17 employees Report this company About us SuprSend is a central communication stack for easily creating, managing and delivering notifications to your end users on multiple channels. Our single notification API has all the features set, which enables you to send notifications in a reliable and scalable manner and take care of end user experience, thereby eliminating the need to develop any notification service in-house for transactional/engagement notifications. Website https://www.suprsend.com/ External link for SuprSend Industry Software Development Company size 11-50 employees Headquarters San Francisco, CA Type Privately Held Founded 2021 Specialties notifications, android push, ios push, email, sms, whatsapp, slack, Microsoft teams, Telegram, App Inbox, A/B Experiments, web push, RCS, preferences management, batching & digests, notification infrastructure, twilio, template builder, inapp inbox, and react sdk Products SuprSend SuprSend Push Notification Software SuprSend is a notification infrastructure as a service platform for easily creating, managing, and delivering notifications to your end users. SuprSend has all the features set which enable you to send notifications in a reliable and scalable manner, as well as take care of end-user experience, thereby eliminating the need to build any notification service in-house. Benefits of using SuprSend as your notification stack are that: * You do not have to do any vendor integrations for channels in your code. You can easily add/remove/prioritize vendors and channels from your SuprSend account, * You can design powerful templates for all channels together and manage them from a single place, * You can leverage powerful features to experiment fast with notifications and take care of end-user experience without writing a single line of code. Locations Primary San Francisco, CA 94104, US Get directions Bengaluru, KA 560102, IN Get directions Employees at SuprSend Deepak Deolalikar Samuel Sunderaraj Gaurav Verma Sathya Nellore Sampat See all employees Updates SuprSend reposted this SuprSend 19,129 followers 4d Report this post 𝗧𝘆𝗽𝗲-𝘀𝗮𝗳𝗲 𝘄𝗼𝗿𝗸𝗳𝗹𝗼𝘄 𝘁𝗿𝗶𝗴𝗴𝗲𝗿𝘀 𝗶𝗻 𝗦𝘂𝗽𝗿𝗦𝗲𝗻𝗱 🧩 Triggering workflows with loosely typed payloads often leads to bugs that only show up at runtime. To reduce that risk, SuprSend now supports schema-driven type generation for workflow triggers. You define the payload structure once as a JSON schema in SuprSend. From there, the CLI generates strongly-typed interfaces that you can use directly in your application code. What this improves: • Catch invalid payloads during development instead of production • Get IDE autocomplete and immediate feedback while coding • Keep workflow payloads consistent as schemas evolve • Avoid manually maintaining type definitions Type generation is available for 𝗧𝘆𝗽𝗲𝗦𝗰𝗿𝗶𝗽𝘁, 𝗣𝘆𝘁𝗵𝗼𝗻, 𝗚𝗼, 𝗝𝗮𝘃𝗮, 𝗞𝗼𝘁𝗹𝗶𝗻, 𝗦𝘄𝗶𝗳𝘁, 𝗮𝗻𝗱 𝗗𝗮𝗿𝘁. Docs in the comments. 7 1 Comment Like Comment Share SuprSend 19,129 followers 4d Report this post 𝗧𝘆𝗽𝗲-𝘀𝗮𝗳𝗲 𝘄𝗼𝗿𝗸𝗳𝗹𝗼𝘄 𝘁𝗿𝗶𝗴𝗴𝗲𝗿𝘀 𝗶𝗻 𝗦𝘂𝗽𝗿𝗦𝗲𝗻𝗱 🧩 Triggering workflows with loosely typed payloads often leads to bugs that only show up at runtime. To reduce that risk, SuprSend now supports schema-driven type generation for workflow triggers. You define the payload structure once as a JSON schema in SuprSend. From there, the CLI generates strongly-typed interfaces that you can use directly in your application code. What this improves: • Catch invalid payloads during development instead of production • Get IDE autocomplete and immediate feedback while coding • Keep workflow payloads consistent as schemas evolve • Avoid manually maintaining type definitions Type generation is available for 𝗧𝘆𝗽𝗲𝗦𝗰𝗿𝗶𝗽𝘁, 𝗣𝘆𝘁𝗵𝗼𝗻, 𝗚𝗼, 𝗝𝗮𝘃𝗮, 𝗞𝗼𝘁𝗹𝗶𝗻, 𝗦𝘄𝗶𝗳𝘁, 𝗮𝗻𝗱 𝗗𝗮𝗿𝘁. Docs in the comments. 7 1 Comment Like Comment Share SuprSend 19,129 followers 2w Report this post [𝗟𝗜𝗩𝗘] 𝗛𝗼𝘀𝘁𝗲𝗱 𝗣𝗿𝗲𝗳𝗲𝗿𝗲𝗻𝗰𝗲 𝗣𝗮𝗴𝗲: 𝗥𝗲𝗮𝗱𝘆-𝘁𝗼-𝘂𝘀𝗲 𝘂𝘀𝗲𝗿 𝘀𝗲𝘁𝘁𝗶𝗻𝗴𝘀 🌍 SuprSend now gives you a ready-made Preference Page where users can manage how they receive notifications. Just link to it from your emails or SMS — no need to build or maintain your own preference system. It’s designed to help you stay compliant while giving users better control over their communication. We’ve now added full localization support so these pages work seamlessly for global audiences. What’s new: • Pages adapt automatically to the user’s locale • Category names, descriptions, and sections are rendered dynamically • Static page text is localized • Smart fallback when a regional language isn’t available If you’re sending notifications across regions, this makes preference management clearer for users and easier to scale for teams. Preview link in the comments. 5 Like Comment Share SuprSend 19,129 followers 3w Edited Report this post 𝗘𝘅𝗽𝗼𝗿𝘁 𝗡𝗼𝘁𝗶𝗳𝗶𝗰𝗮𝘁𝗶𝗼𝗻𝘀 𝗗𝗮𝘁𝗮 𝘁𝗼 𝗔𝗺𝗮𝘇𝗼𝗻 𝗦𝟯 🚀 Now you can fully own and control your notifications data within your S3 bucket — create custom dashboards, debug delivery issues, or maintain audit trails for compliance. 𝗪𝗵𝗮𝘁'𝘀 𝗶𝗻𝗰𝗹𝘂𝗱𝗲𝗱: • Syncs every 5 minutes in encrypted Parquet files • Messages, Workflow Executions, and Requests • Automatic backfills and hourly partitions • Works natively with Athena, Snowflake, BigQuery, Redshift Confidently build dashboards, surface notification logs to customers, or track entire customer lifecycle end-to-end. Docs in comments 👇 9 1 Comment Like Comment Share SuprSend 19,129 followers 1mo Report this post We're #hiring a new UI / UX Designer in Bengaluru, Karnataka. Apply today or share this post with your network. UI / UX Designer SuprSend, Bengaluru, Karnataka, India 7 Like Comment Share SuprSend 19,129 followers 1mo Edited Report this post 𝗖𝗮𝘁𝗲𝗴𝗼𝗿𝘆 𝗧𝗿𝗮𝗻𝘀𝗹𝗮𝘁𝗶𝗼𝗻𝘀 𝗳𝗼𝗿 𝗣𝗿𝗲𝗳𝗲𝗿𝗲𝗻𝗰𝗲 𝗖𝗲𝗻𝘁𝗲𝗿𝘀 🌍 In pursuit of seamless translations: preference categories now display in your user's locale. 𝗪𝗵𝗮𝘁 𝘁𝗵𝗶𝘀 𝗺𝗲𝗮𝗻𝘀: • One preference center works globally (no separate versions for each region) • Users make informed choices when they see categories in their preferred language • Add translations through Dashboard, API, or CLI • Smart fallback logic ensures something always displays (es-mx → es → en) If you're shipping notifications to a multilingual audience, this removes friction for both your users and your team. Docs in comments below 👇 13 1 Comment Like Comment Share SuprSend 19,129 followers 1mo Report this post 𝗛𝗼𝘄 𝗖𝗿𝗮𝘇𝘆𝗚𝗮𝗺𝗲𝘀 𝗖𝘂𝘁 𝗡𝗼𝘁𝗶𝗳𝗶𝗰𝗮𝘁𝗶𝗼𝗻 𝗗𝗲𝗽𝗹𝗼𝘆𝗺𝗲𝗻𝘁 𝗳𝗿𝗼𝗺 𝗪𝗲𝗲𝗸𝘀 𝘁𝗼 𝗛𝗼𝘂𝗿𝘀 CrazyGames serves 45M+ monthly players across 3,000+ browser games. But their in-house notification system held them back. 🎮 𝗧𝗵𝗲 𝗽𝗿𝗼𝗯𝗹𝗲𝗺: Building notifications required heavy engineering involvement. Even small template changes meant creating dev tickets and took 2 weeks to deploy. Product teams couldn't personalize or experiment fast without developer time. 𝗪𝗵𝗮𝘁 𝗰𝗵𝗮𝗻𝗴𝗲𝗱: CrazyGames adopted SuprSend to abstract notification development out of code. Templates, logic, and workflows shifted entirely to Product & Design. They also connected their database to SuprSend, allowing teams to create targeted cohorts by writing SQL — no data exports, no syncing delays, no engineering bottlenecks. 𝗧𝗵𝗲 𝗿𝗲𝘀𝘂𝗹𝘁: • Notification launches: weeks → hours • Self-serve campaigns with personalized game recommendations • A/B testing across email, push, and in-app — all unified • Product teams operate independently 🎥 Watch Jonas (VP of Product, CrazyGames) full story link in comments below. 33 4 Comments Like Comment Share SuprSend 19,129 followers 1mo Report this post We're #hiring a new Founders’ Office – Product Marketing in Bengaluru, Karnataka. Apply today or share this post with your network. Product Marketing Manager SuprSend, Bengaluru, Karnataka, India 9 1 Comment Like Comment Share SuprSend 19,129 followers 1mo Edited Report this post 𝗜𝗻𝘁𝗿𝗼𝗱𝘂𝗰𝗶𝗻𝗴 𝗧𝗿𝗮𝗻𝘀𝗹𝗮𝘁𝗶𝗼𝗻𝘀 𝗶𝗻 𝗡𝗼𝘁𝗶𝗳𝗶𝗰𝗮𝘁𝗶𝗼𝗻𝘀 Maintaining separate notification templates for every language doesn't scale. Change one template and you update all language versions manually. Translations solve this. Write one template that works across all languages. SuprSend automatically serves the right language based on user locale, with intelligent fallbacks. What's included: • Upload existing JSON translation files & manage through CLI/API • Smart translation keys with automatic language selection • Dynamic variables and pluralization handling • Namespaced keys to organize by feature • Change history with rollback support Documentation in the comments 👇 13 4 Comments Like Comment Share SuprSend 19,129 followers 1mo Report this post We're #hiring a new Product Manager in Bengaluru, Karnataka. Apply today or share this post with your network. Product Manager SuprSend, Bengaluru, Karnataka, India 4 Like Comment Share Join now to see what you are missing Find people you know at SuprSend Browse recommended jobs for you View all updates, news, and articles Join now Similar pages SuperSend Software Development Las Vegas, Nevada Crew Technology, Information and Internet Keploy 🐰 Technology, Information and Internet San Franciso, California KubeSense Software Development Austin, Texas Gushwork Software Development Brooklyn, New York Robylon AI Software Development San Francisco, California Cube Technology, Information and Internet Palo Alto, California Klaar Software Development San Francisco, California Bik.ai Technology, Information and Internet Zime Data Infrastructure and Analytics San Jose, CA Show more similar pages Show fewer similar pages Browse jobs Engineer jobs 555,845 open jobs Product Marketer jobs 9,108 open jobs Marketing Manager jobs 106,879 open jobs Scientist jobs 48,969 open jobs Machine Learning Engineer jobs 148,937 open jobs Developer jobs 258,935 open jobs Marketer jobs 37,677 open jobs Intelligence Specialist jobs 7,156 open jobs Intern jobs 71,196 open jobs Python Developer jobs 46,642 open jobs Senior Product Marketing Manager jobs 11,129 open jobs Analyst jobs 694,057 open jobs Manager jobs 1,880,925 open jobs Associate Product Manager jobs 76,300 open jobs General Engineer jobs 54,597 open jobs Software Engineer jobs 300,699 open jobs Associate jobs 1,091,945 open jobs Account Manager jobs 121,519 open jobs Marketing Specialist jobs 49,178 open jobs Digital Marketing Manager jobs 17,135 open jobs Show more jobs like this Show fewer jobs like this Funding SuprSend 1 total round Last Round Seed Oct 14, 2022 External Crunchbase Link for last round of funding US$ 1.0M Investors BoldCap + 4 Other investors See more info on crunchbase More searches More searches Engineer jobs Developer jobs Marketing Manager jobs Machine Learning Engineer jobs Intelligence Specialist jobs Scientist jobs Associate Product Manager jobs Analyst jobs Software Engineer jobs Intern jobs Product Management Intern jobs Talent Specialist jobs Global Marketing Manager jobs Consultant jobs Marketing Lead jobs Marketing Specialist jobs Product Marketer jobs Writer jobs Frontend Developer jobs Program Management Intern jobs Product Manager jobs Associate Project Manager jobs Network Developer jobs Account Manager jobs Digital Marketing Manager jobs Manager jobs Product Engineer jobs Senior Developer jobs Application Engineer jobs Customer Service Technician jobs Advocate jobs Linux Developer jobs Security Administrator jobs Web Developer jobs Senior Software Engineer jobs Full Stack Engineer jobs Data Scientist jobs Curriculum Developer jobs Sales Trainer jobs Science Specialist jobs Web Development Specialist jobs Security Engineer jobs Software Engineer Intern jobs Staff Software Engineer jobs Technology Engineer jobs Lead Software Engineer jobs Research Software Engineer jobs Business Development Associate jobs Technician jobs Content Specialist jobs iOS Developer jobs Senior Product Manager jobs User Interface Designer jobs PHP Developer jobs Product Designer jobs Director jobs Bookkeeper jobs User Experience Designer jobs Operations Engineer jobs Founder jobs LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language Agree & Join LinkedIn By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Sign in to see who you already know at SuprSend Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . | 2026-01-13T08:48:25 |
https://stackoverflow.com/questions/tagged/socket.io | Newest 'socket.io' Questions - Stack Overflow Skip to main content Stack Overflow About Products For Teams Stack Internal Implement a knowledge platform layer to power your enterprise and AI tools. Stack Data Licensing Get access to top-class technical expertise with trusted & attributed content. Stack Ads Connect your brand to the world’s most trusted technologist communities. Releases Keep up-to-date on features we add to Stack Overflow and Stack Internal. About the company Visit the blog s-popover#show" data-s-popover-placement="bottom-start" /> Loading… current community Stack Overflow help chat Meta Stack Overflow your communities Sign up or log in to customize your list. more stack exchange communities company blog Log in Sign up Home Questions AI Assist Tags Challenges Chat Articles Users Companies Collectives Communities for your favorite technologies. Explore all Collectives Stack Internal Stack Overflow for Teams is now called Stack Internal . Bring the best of human thought and AI automation together at your work. Try for free Learn more Stack Internal Bring the best of human thought and AI automation together at your work. Learn more Collectives™ on Stack Overflow Find centralized, trusted content and collaborate around the technologies you use most. Learn more about Collectives Stack Internal Knowledge at work Bring the best of human thought and AI automation together at your work. Explore Stack Internal 20,563 questions se-uql#toggleEditor"> Newest Active Bountied Unanswered More Bountied 0 Unanswered Frequent Score Trending Week Month Unanswered (my tags) Filter Filter by No answers No upvoted or accepted answers No Staging Ground Has bounty Days old Sorted by Newest Recent activity Highest score Most frequent Bounty ending soon Trending Most activity Tagged with My watched tags The following tags: Apply filter Cancel 0 votes 1 answer 37 views Python socket.io frequent websocket disconnections I’m facing persistent WebSocket disconnections in production on Azure App Service (Linux container) during long-running operations (60–120 seconds). The same setup works fine locally in Docker. ... python websocket socket.io disconnection Pramod 1 asked Jan 5 at 10:25 1 vote 2 answers 80 views Why isn't this emitting the message? @app.route('/3x3/online/<username>', methods = ['POST']) def online3x3(username): if username == session['username']: socketio.emit('create', (session['username'], 1), namespace = '/... python flask socket.io emit Robin Bourne 11 asked Jan 1 at 15:15 1 vote 0 answers 65 views Socket.IO Livestream Not Cleaning Up After App Crash (Zombie Stream Issue) I’m building a Node.js + Socket.IO livestreaming backend where a user can have only one active livestream at a time. When a mobile app is force-closed or crashes, the client does not send a ... node.js websocket socket.io live-streaming Bisrat Dereje 11 asked Dec 30, 2025 at 19:21 Best practices 0 votes 0 replies 24 views How does one prevent stale ack caused by exceptions? I have a nest server that has a few @SubscribeMessage functions that fetch data and return it to the client. If the client's request if bad, the functions might throw an error. However, the client's ... socket.io nest Jan Thürmann 53 asked Dec 28, 2025 at 15:13 1 vote 1 answer 58 views Socket.io Custom Headers So apparently for authentication you need to pass extraHeaders in socket.io, meaning you can't use http-only cookies. Since I have this code over here, trying to connect to the most barebones socket.... websocket socket.io Ruslan Plastun 2,292 asked Dec 25, 2025 at 13:10 -3 votes 0 answers 142 views node.js socket reconnection failed I'm new in Socket.io; connection successful, "emit" fires and "on" listens successfully from both sides. but when i reload my frontend, then the connection lost; i found repeatedly ... javascript node.js next.js socket.io MD Meadul Islam 3 asked Dec 15, 2025 at 6:17 0 votes 0 answers 77 views Socket connection issue in react-native and nodejs I’m currently working on a logistics app that manages goods transportation in my area. The tech stack includes React Native for the mobile app, Node.js / Express.js for the backend, MongoDB as the ... node.js react-native express redis socket.io Hiren Gamit 1 asked Dec 9, 2025 at 18:14 0 votes 0 answers 32 views Server is listening, but Socket.io client can't reach server I've spent countless hours trying to figure this out, the code worked perfectly fine on my machine, but stopped working on the server, it just kept throwing "example.com/socket.io/?EIO=4&... node.js sockets socket.io Matt Williams4 1 asked Dec 3, 2025 at 16:45 1 vote 2 answers 120 views Frequent update of records in database I’m building a real-time chat application using NestJS, Postgresql (Main DB), Redis and Socket.IO. My database schema (simplified) looks like this: -- Chats table chats ( id serial primary key, ... node.js postgresql redis socket.io real-time Vasile Bubuioc 13 asked Nov 24, 2025 at 10:13 Advice 0 votes 2 replies 68 views Code Review: Websockets integration using NestJS for trading application I’m currently building a trading platform that requires streaming real-time price updates to the UI. I’ve implemented a WebSocket gateway and added handling for common issues such as: Ghost/... node.js websocket socket.io nestjs webster 29 asked Nov 24, 2025 at 0:20 0 votes 0 answers 25 views Integrate socket.io namespaces with Node Cluster I am trying to integrate socket.io with Node's HTTP alongside Node's Cluster Module. Consider the reproducible example: index.js: let cluster = require('cluster') let fs = require('fs') let http = ... node.js parallel-processing socket.io cluster-computing Issac Howard 351 asked Oct 24, 2025 at 14:05 0 votes 0 answers 50 views Error with Turso connection database on Node project I'm following a Node.js tutorial where the database is created with Turso but I have a problem, the connection is created well but I can't realise any type of query. I'm using these libraries: import ... node.js socket.io turso Jordi García 5 asked Oct 22, 2025 at 13:00 0 votes 1 answer 61 views Socket io is not connecting from Angular to backend nodejs So I am trying to build a dynamic dashboard application ,so I use socket io 4.8.1 , and In frontend as well I installed the same version , now I used polling socket io it actually worked with polling ... node.js angular express socket.io Vignesh 61 asked Oct 16, 2025 at 10:07 0 votes 0 answers 43 views How to prevent auth token from being stolen on the Nextjs client side of socket.io? This is my nodejs server socket.io code: const io = new Server(server, { cors: { origin: "*", // Allows connections from any origin methods: ["GET", "POST"] // ... next.js socket.io cookie-httponly yeln 797 asked Oct 3, 2025 at 3:34 0 votes 0 answers 88 views Python Socket.IO with FastAPI in Kubernetes 499 and 426 error I am trying to setup a socketio server, but having issues with client connection either getting 499 or 426 error - I have tried port forwarding from the pod to my local and run curl command that also ... python kubernetes socket.io kubernetes-ingress nginx-ingress Arsh 45 asked Sep 19, 2025 at 16:43 0 votes 0 answers 60 views socket.io works in browser but failed in node.js I'm trying to replicate a function of a website in node.js. And this function is implemented by establishing a websocket connection via socket.io. So I just imported socket.io in my node.js code, but ... node.js websocket socket.io n1nja88888 66 asked Sep 11, 2025 at 13:49 0 votes 1 answer 84 views How to emit Socket.IO events from Bull queue worker running in separate process? I have a Express application with Socket.IO and Bull queues. My worker processes run in separate processes from the main Express server, and I need to emit Socket.IO events from within the worker jobs.... node.js express socket.io bull raspace 3 asked Aug 26, 2025 at 14:56 0 votes 1 answer 87 views Laravel Echo Server not receiving broadcast events even though WebSocket connection is successful I’m using Laravel 8 with Redis and laravel-echo-server to broadcast events to my frontend. The WebSocket connection is successful (status 200), but the broadcasted event from Laravel never shows up in ... laravel redis socket.io laravel-echo laravel-events bunga shafa 1 asked Aug 18, 2025 at 17:56 0 votes 1 answer 42 views Where does the cookie value come from in socketio server when using express-session? This is what the request headers look like in my handshake request GET wss://<REDACTED>/socket.io/?EIO=4&transport=websocket HTTP/1.1 Host: <REDACTED> Connection: Upgrade Pragma: no-... socket.io express-session rjpj1998 419 asked Jul 26, 2025 at 21:24 0 votes 0 answers 74 views Android System Monitoring: ADB polling vs. APK with Socket.IO - Which has lower performance overhead? I need to collect various system metrics from an Android device, including: Frame rate (FPS) Memory usage CPU frequency Battery level Battery voltage Battery temperature Battery current Power ... android socket.io apk adb Bellong 49 asked Jul 25, 2025 at 4:39 -1 votes 1 answer 74 views In Next.js, not using sockets but getting GET 404 There was another post like this, but the only answer it had was to just restart, which didn't work for me. I added sockets to my project for the first time, it wasn't working so i reverted to a ... reactjs sockets next.js websocket socket.io Yevheniia Simaka 31 asked Jul 18, 2025 at 15:02 0 votes 0 answers 48 views socket io java android app and socket io javascript server reliable connection possible? I need to make a reliable socket io solution for my android apps for chatting app or similar. When I was tinkering with the system I noticed the socketio java client is getting disconnected every few ... java android sockets socket.io Rifat 1,928 asked Jul 16, 2025 at 8:22 0 votes 0 answers 61 views Artillery Socket.IO: {{token}} in socketio.query interpolates as 'undefined' despite beforeConnect I'm trying to load test a Node.js Socket.IO server using Artillery. My server expects an authentication token as a query parameter during the handshake. I'm using Artillery's socketio.beforeConnect ... websocket socket.io jwt load-testing artillery Manish Kumar 1 asked Jul 11, 2025 at 20:02 1 vote 1 answer 29 views Periodic beeping in live audio stream using Flask-SocketIO and sounddevice — concurrency issue? Periodic beeping in live audio stream using Flask-SocketIO and sounddevice — concurrency or deployment issue? Question I'm building a live audio streaming feature with Flask-SocketIO and sounddevice. ... python flask audio socket.io Daniel 63 asked Jul 7, 2025 at 17:09 0 votes 0 answers 42 views pc.oniceconnectionstatechange = () => { state disconnected i am making the streamign app in react native so when host start the streamign and user user join the stream user able to see host stream but user start the stream host not able see user see that ... javascript node.js react-native socket.io Vikram bhosale 9 asked Jun 27, 2025 at 4:17 0 votes 0 answers 38 views Question about receiving events in Artillery without emitting I'm using the socketio engine in Artillery, and I want to connect to the server without emitting any events — just receive events after the connection is established. Is there a way to listen for ... socket.io artillery 장현수 1 asked Jun 25, 2025 at 6:06 0 votes 1 answer 66 views Socket.IO not working on AWS with NGINX, Node.js, and HTTPS (400 Bad Request on WebSocket) I'm running a Node.js application with HTTPS and Socket.IO on an AWS EC2 instance, behind NGINX. The REST APIs work fine, but the WebSocket connection to Socket.IO fails with a 400 Bad Request. const ... node.js amazon-web-services https socket.io Kulweet_kumar 34 asked Jun 20, 2025 at 10:27 0 votes 0 answers 25 views Socket.IO client only sends message on first request, subsequent emits are queued but not sent I'm using Socket.IO in a Next.js 15 app, and I establish the socket connection globally inside a layout or provider component. My issue is that when I click a button to send a message using socket.... reactjs next.js socket.io Igor Croitoru 11 asked Jun 6, 2025 at 20:37 0 votes 1 answer 58 views Flutter web + flask_socketio: flutter app can't connect to flask socketio I am trying to run a Flutter web frontend and a python flask + flask_socketio api/socketio backend in a docker compose file. The frontend image uses nginx as a reverse proxy, and its configuration ... flutter nginx docker-compose socket.io flask-socketio tommat208 409 asked Jun 6, 2025 at 16:00 1 vote 1 answer 86 views Bloc throws an exception "emit was called after an event handler completed normally." I am using bloc and socket.io in my flutter application to react to login states from the server. Future<void> _setLoginListener(SetLoginListener event, Emitter<LoginState> emit)async{ ... flutter socket.io bloc user29365632 23 asked Jun 3, 2025 at 16:33 0 votes 0 answers 51 views socket.io-client works only via Run Code in VSCode, not with node CLI Environment: OS: Windows 10 Node.js: v20.12.2 socket.io: v4.8.1 socket.io-client: v4.8.1 Run environment: VSCode (Run Code extension) & terminal (Git Bash, PowerShell) Issue: I have a Node.js + ... node.js sockets socket.io seungyeop yoo 1 asked May 31, 2025 at 10:34 2 votes 2 answers 73 views Making a ChatApp Two - Way So, basically, I have created a basic chat app using html, css, and javascript. I am also using SocketIO, so that I can make the chat app real-time. The problem is, I am not able to figure out how I ... javascript html socket.io hacks_and_nimbus 33 asked May 30, 2025 at 14:51 0 votes 1 answer 59 views Why is this event is not getting cleaned up or getting attached twice? There's an event listener as update-active-users and it's getting listened twice i asked ChatGpt she says that might be listener is getting registered twice . useEffect(() => { const ... reactjs node.js websocket socket.io chatbot Raman Pratap Singh 1 asked May 13, 2025 at 15:12 0 votes 0 answers 38 views Ios Swift authentication with auth object I'm using sockets in android to have a connection between backend(node js) app and my android app. I'm successfully able connect to socket by passing auth header like mSocket = IO.socket(uri, IO.... swift react-native socket.io Mohammad Fahad 81 asked May 9, 2025 at 15:53 0 votes 1 answer 27 views How do you use certificates and certificate chain with Flask SocketIO? I need to use SocketIO from flask_socketio with certificate, secret key, and certification chain. How do I do that? Here is my code so far: from gevent import monkey monkey.patch_all() import ssl ... python flask socket.io certificate wedesoft 2,997 asked May 9, 2025 at 15:14 1 vote 1 answer 46 views socket notification for multiple user for different logical area approach comparison My app has five tab - Tab1 Tab2 Tab3 Tab4 Tab5 each tab its own logical operation. using WebSocket notification with api if user made any change in Tab1 Tab 2 3 4,5 must get notification. similar ... websocket socket.io push-notification signalr signalr.client Maulik Dave 235 asked May 8, 2025 at 1:55 0 votes 0 answers 31 views Websockets not working on AWS elastic beanstalk (Socket.IO) I'm deploying a Node.js app on AWS Elastic Beanstalk using Nginx as the reverse proxy, with socket.io on the backend and socket.io-client on the frontend. Everything runs on a single instance. Locally ... websocket socket.io amazon-elastic-beanstalk Diego H. O'Hagan 117 asked May 1, 2025 at 5:34 0 votes 0 answers 64 views Socket.IO not connecting in Chrome browser (HTTPS, custom port 6530) Socket issue: My Laravel backend is hosted on https://example001.com/, while my React app is hosted on https://example002.com/ React uses the 4.8.1 version of the socket.io client, and Laravel uses ... reactjs laravel websocket socket.io socket.io-client Tirth Gajjar 1 asked Apr 30, 2025 at 13:43 0 votes 2 answers 72 views TypeError: Cannot read properties of undefined (reading 'id') when using createAdapter() from @socket.io/cluster-adapter I'm trying to set up Socket.IO with cluster support using PM2, following this docs. Here's my code: import { createAdapter } from "@socket.io/redis-adapter"; import { createAdapter as ... javascript typescript express socket.io michioxd 63 asked Apr 28, 2025 at 16:44 0 votes 0 answers 29 views python server / JS client: socketio regular disconnects In trying to reproduce errors from a larger project I have created a server using python's aiohttp and the following python-socketio (v5.12.0) namespace: class MyNamespace(AsyncNamespace): ... javascript websocket socket.io aiohttp python-socketio Gentleman_Narwhal 101 asked Apr 27, 2025 at 8:37 0 votes 0 answers 59 views Connection failed: socket.io how are you? Guys, I'm trying to use socket.io to create a chat, locally everything works, when I put "Cpanel" into production I can't connect. Displays message below: websocket.js:43 ... node.js sockets websocket socket.io node-modules Leonardo Arruda 1 asked Apr 23, 2025 at 18:10 2 votes 1 answer 43 views SocketIO in React app does not capture emitted event I am trying to build a Leaderboard that updates real-time based on redis stream events. So I have this code in my frontend component that ultimately should be getting the latest updates real-time from ... python websocket socket.io flask-socketio Vaggouras 89 asked Apr 21, 2025 at 17:39 1 vote 1 answer 117 views Flutter socket_io_client not updating query token on reconnect – server keeps receiving old 'public' token I'm building a mobile app in Flutter that connects to a Node.js WebSocket server using socket_io_client. The WebSocket is used for both: public unauthenticated users (to receive global broadcasts) ... node.js flutter dart websocket socket.io Nico 51 asked Apr 20, 2025 at 10:13 0 votes 2 answers 126 views Golang Fiber + Socket.IO: WebSocket Disconnects and Connects in Never Ending Loop I'm working with a Golang Fiber web server using socketio to manage WebSocket connections. I'm trying to mark a guest as Online = false in the database when the socket disconnects. However, I'm facing ... go sockets websocket socket.io Vidy45agarvk 11 asked Apr 16, 2025 at 19:02 0 votes 1 answer 57 views Socket.IO server in v2.x with a v3.x client, but they are not compatible I am working on flutter app where i need to show live stock price from symphonyfintech and I am using socket_io_client: ^3.1.1. Now i am trying to get connect with socket i am getting error that says: ... flutter dart socket.io flutter-dependencies user29912264 asked Apr 16, 2025 at 7:47 0 votes 0 answers 30 views iOS Socket.IO client connects but events don't reach server (auth via headers, works on Android/Postman) Description: I'm implementing a Socket.IO connection in an iOS app using socket.io-client-swift. The backend uses authentication via headers (user-id and sessionkey). The issue I'm facing is: The ... ios swift websocket socket.io Testing Something 1 asked Apr 15, 2025 at 14:24 0 votes 0 answers 43 views How to use socketio and ipc together in python I am trying to building an server that communicates with the client using socketio protocol, Now the server starts multiple application as a sub processes, the server communicates with this ... python socket.io ipc distributed-system Souvik De 70 asked Apr 12, 2025 at 5:00 0 votes 0 answers 42 views AWS NodeJS Websocket server "sleeping" - no error I've got a NodeJS websocket running on an EC2 instance. I'm keeping it alive with PM2. I'm working on it via SSH using vis studio code. The system is running well and I have about 500 clients (desktop ... node.js amazon-ec2 socket.io pm2 Glenn Angel 1 asked Apr 4, 2025 at 1:29 0 votes 1 answer 51 views How to add different namespace clients to the same room? I created two socket.io namespaces because there is an agent and customer in chat application and their handleConnection, handleDisconnect functions and etc. are different. That is why I separated ... typescript websocket socket.io nestjs Asif Hajiyev 1 asked Apr 3, 2025 at 13:10 1 vote 1 answer 57 views Why does my Socket.IO connection prevent my Angular component from reloading? I have an Angular component that connects to a Socket.IO server. However, when I include the WebSocket connection code, my component fails to reload properly. If I comment out the Socket.IO code, ... angular websocket socket.io server-side-rendering angular-ssr Hamzah Alkhateeb 109 asked Mar 27, 2025 at 4:27 1 2 3 4 5 … 412 Next The Overflow Blog Now everyone can chat on Stack Overflow Vibe code anything in a Hanselminute Featured on Meta A proposal for bringing back Community Promotion & Open Source Ads Community Asks Sprint Announcement – January 2026: Custom site-specific badges! Policy: Generative AI (e.g., ChatGPT) is banned Modernizing curation: A proposal for The Workshop and The Archive All users on Stack Overflow can now participate in chat Hot Network Questions Sentence that contains both a statement and its opposite How to decide if I need a DPIA for a new project? How to translate habebat in this sentence? Does the 22° angle in the right triangle seem to correspond to the maximum of this area ratio? What's up with the constant barrage of Public Safety Alerts in Korea, and is there any way to opt out? Does this fallacy already exist? Western with a violent father and a conflict between two ranches Handling feature correlation in datasets How can I change my eye color when renewing my US passport? what aircraft does 14CFR Part 61.101 (f) assume? Which torture methods were used on Sam Lowry? (James 2:18b) Was James speaking facetiously to make a spiritual and practical pastoral point? tikz: using the pos key to place nodes along a plot When did German nouns become capitalized? Does the success of physics justify a belief in Physicalism? Designing offline-first sync for a multi-user desktop app that must keep working through network outages What is the species of this seed? The rigor of the definition of higher derivative How to Create an Abstract Network Animation with Moving Light Pulses in Blender? Implicit methods than can be invoked without mentioning the method name Why is the word "receive" only two syllables when it has so many vowels? Apparent flaw in classical explanation of radiation pressure Selecting non-white/non-black color for any given background color In considering asset allocation, should one take into account the buy-low/sell-high principle? more hot questions Newest socket.io questions feed Subscribe to RSS Newest socket.io questions feed To subscribe to this RSS feed, copy and paste this URL into your RSS reader. Stack Overflow Questions Help Chat Business Stack Internal Stack Data Licensing Stack Ads Company About Press Work Here Legal Privacy Policy Terms of Service Contact Us cookie-settings#toggle" class="s-btn s-btn__link py4 js-gps-track -link" data-gps-track="footer.click({ location: 5, link: 38 })" data-consent-popup-loader="footer"> Cookie Settings Cookie Policy Stack Exchange Network Technology Culture & recreation Life & arts Science Professional Business API Data Blog Facebook Twitter LinkedIn Instagram Site design / logo © 2026 Stack Exchange Inc; user contributions licensed under CC BY-SA . rev 2026.1.12.38533 | 2026-01-13T08:48:25 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.