Flow Labs

flowlabs

TORTOLA, BVI, July 25th, 2024/Chainwire/--The Tanssi appchain infrastructure protocol has announced a significant collaboration with Grupo Flow, one of Brazil’s largest media ecosystems, boasting over 23 million subscribers across multiple platforms. As Grupo Flow transitions into the blockchain space with the creation of Flow Chain, this collaboration signifies a milestone. Tanssi will facilitate this move, not only bringing Grupo Flow's vast community into the blockchain realm but also connecting them with Polkadot’s vibrant and interoperable ecosystem. This strategic integration ensures a robust, scalable infrastructure that will enhance user engagement, expand Grupo Flow's audience reach, and open new monetization opportunities for content creators within the Flow Chain platform, leveraging both existing community strengths and new blockchain capabilities. "The possibilities and connections with our audience through our own chain are very exciting. We are thrilled to have a trusted partner to guide us on this journey. Now it's time to head to the lab, study the path and roadmap, and look forward to seeing the first features in our ecosystem,” said Andre Gaigher, CCO at Group Flow. Grupo Flow Transitions to Blockchain, Setting a New Standard for the Digital Media Industry Grupo Flow is a leading digital media ecosystem in Brazil, known for its vast reach and influence in the creator economy. With diverse ventures including creative hubs, software development, and audiovisual production, Grupo Flow has solidified its position as a key player in the Brazilian media landscape. Their platforms, such as the highly popular Flow Podcast, attract millions of followers and listeners, collectively achieving over 73 million views per month and amassing more than 23 million followers. As Grupo Flow transitions into the Polkadot blockchain space with Tanssi, they aim to enhance digital engagement, handle large-scale interactions, and seamlessly integrate advanced technology, all while maintaining their commitment to delivering an excellent user experience. This collaboration will help them strengthen their audience and tap into a new community of blockchain users, further enhancing their digital media ecosystem. Tanssi & Grupo Flow: Unlocking Blockchain Potential for Digital Media Transformation Tanssi’s advanced blockchain infrastructure is crucial in facilitating Grupo Flow’s seamless transition to the blockchain space. Grupo Flow will launch its own application blockchain, Flow Chain, offering a dedicated and customizable environment tailored to their needs. This collaboration will enhance digital engagement through tokenized interactions and decentralized governance, allowing users to participate in content decisions, access exclusive events, and earn rewards. Tanssi’s scalable infrastructure will handle high volumes of transactions, ensuring efficient processing and maintaining a seamless user experience for Grupo Flow’s large and active community. By integrating with Polkadot’s interoperable ecosystem, Flow Chain will access a network of interconnected blockchains and leverage technologies like Moonbeam Routed Liquidity to expand into ecosystems such as Ethereum and Avalanche. This ensures robust security, consistent performance, and extensive growth opportunities. Tanssi's infrastructure reduces transaction costs and opens up new revenue streams through staking rewards and tokenized assets. This strategic collaboration not only supports Grupo Flow’s transition to blockchain but also sets a new benchmark in the digital media industry by enhancing scalability, security, and user engagement. Looking Forward: Grupo Flow's Next Steps With Tanssi Grupo Flow is set to revolutionize the digital media landscape with the launch of Flow Houses, inspired by Soho Houses, known for their exclusive memberships and luxurious amenities. This platform will offer unique, tokenized access to high-end venues and events through blockchain technology, showcasing Grupo Flow's commitment to pioneering new experiences in the media sector. The upcoming launch of Grupo Flow on Tanssi Mainnet later this year marks one of the largest blockchain integrations by an online media group in Brazil, leveraging the scalability and efficiency of Tanssi's infrastructure and benefiting from Polkadot's interoperable ecosystem. For those interested in expanding their project to the blockchain space, Tanssi offers a straightforward, code-free application chain deployment platform. Explore and launch your project today at apps.tanssi.network. About Tanssi Network Tanssi’s appchain infrastructure protocol is designed to simplify and accelerate the deployment of appchains. By connecting a chain to Tanssi, it is instantly transformed into a modular appchain. This transition grants access to a developer-friendly and permissionless environment, fully stocked with all essential infrastructural components to run a chain right out of the box. Key features include a shared and decentralized network of block producers, ensuring robust security and data retrievability, alongside seamless integrations with vital tools like bridges, wallets, block explorers, RPC endpoints, indexers, oracles, and more. As a result, appchains can be deployed in just minutes—a significant improvement over the typical months-long process. Learn more at tanssi.network. About Grupo Flow Grupo Flow operates as a comprehensive media ecosystem, focusing on the creator economy with ventures in technology, content, media, production, and advertising. Central to the group is Estudios Flow, a creative hub housing over 30 creators dedicated to fostering dialogue, plurality, and transparency. Producing over 70 hours of content weekly across various formats and niches, Estudios Flow aims to build community ties nationwide. The ecosystem also includes Flow S.A., Flow Games, Flow News, Flow Sport Club, Venus, Ciência Sem Fim, Amplifica, the digital agency Golden Pill, software house WolfVision, and Flow Labs, specializing in audiovisual productions. The initiative traces back to the influential Flow, launched by Igor Coelho, a trailblazer in Brazil’s videocast arena. Learn more at linkedin.com/company/flow-grupo. Contact CMO Katherine Quilca Barcelli Moondance Labs kathy@moondancelabs.com This story was distributed as a release by Chainwire under HackerNoon’s Business Blogging Program. Learn more about the program here. TORTOLA, BVI, July 25th, 2024/Chainwire/--The Tanssi appchain infrastructure protocol has announced a significant collaboration with Grupo Flow, one of Brazil’s largest media ecosystems, boasting over 23 million subscribers across multiple platforms. As Grupo Flow transitions into the blockchain space with the creation of Flow Chain, this collaboration signifies a milestone. Tanssi will facilitate this move, not only bringing Grupo Flow's vast community into the blockchain realm but also connecting them with Polkadot’s vibrant and interoperable ecosystem. This strategic integration ensures a robust, scalable infrastructure that will enhance user engagement, expand Grupo Flow's audience reach, and open new monetization opportunities for content creators within the Flow Chain platform, leveraging both existing community strengths and new blockchain capabilities. "The possibilities and connections with our audience through our own chain are very exciting. We are thrilled to have a trusted partner to guide us on this journey. Now it's time to head to the lab, study the path and roadmap, and look forward to seeing the first features in our ecosystem,” said Andre Gaigher, CCO at Group Flow. "The possibilities and connections with our audience through our own chain are very exciting. We are thrilled to have a trusted partner to guide us on this journey. Now it's time to head to the lab, study the path and roadmap, and look forward to seeing the first features in our ecosystem,” said Andre Gaigher, CCO at Group Flow. Grupo Flow Transitions to Blockchain, Setting a New Standard for the Digital Media Industry Grupo Flow is a leading digital media ecosystem in Brazil, known for its vast reach and influence in the creator economy. With diverse ventures including creative hubs, software development, and audiovisual production, Grupo Flow has solidified its position as a key player in the Brazilian media landscape. Their platforms, such as the highly popular Flow Podcast, attract millions of followers and listeners, collectively achieving over 73 million views per month and amassing more than 23 million followers. As Grupo Flow transitions into the Polkadot blockchain space with Tanssi, they aim to enhance digital engagement, handle large-scale interactions, and seamlessly integrate advanced technology, all while maintaining their commitment to delivering an excellent user experience. This collaboration will help them strengthen their audience and tap into a new community of blockchain users, further enhancing their digital media ecosystem. Tanssi & Grupo Flow: Unlocking Blockchain Potential for Digital Media Transformation Tanssi’s advanced blockchain infrastructure is crucial in facilitating Grupo Flow’s seamless transition to the blockchain space. Grupo Flow will launch its own application blockchain, Flow Chain, offering a dedicated and customizable environment tailored to their needs. This collaboration will enhance digital engagement through tokenized interactions and decentralized governance, allowing users to participate in content decisions, access exclusive events, and earn rewards. Tanssi’s scalable infrastructure will handle high volumes of transactions, ensuring efficient processing and maintaining a seamless user experience for Grupo Flow’s large and active community. By integrating with Polkadot’s interoperable ecosystem, Flow Chain will access a network of interconnected blockchains and leverage technologies like Moonbeam Routed Liquidity to expand into ecosystems such as Ethereum and Avalanche. This ensures robust security, consistent performance, and extensive growth opportunities. Tanssi's infrastructure reduces transaction costs and opens up new revenue streams through staking rewards and tokenized assets. This strategic collaboration not only supports Grupo Flow’s transition to blockchain but also sets a new benchmark in the digital media industry by enhancing scalability, security, and user engagement. Looking Forward: Grupo Flow's Next Steps With Tanssi Grupo Flow is set to revolutionize the digital media landscape with the launch of Flow Houses, inspired by Soho Houses, known for their exclusive memberships and luxurious amenities. This platform will offer unique, tokenized access to high-end venues and events through blockchain technology, showcasing Grupo Flow's commitment to pioneering new experiences in the media sector. The upcoming launch of Grupo Flow on Tanssi Mainnet later this year marks one of the largest blockchain integrations by an online media group in Brazil, leveraging the scalability and efficiency of Tanssi's infrastructure and benefiting from Polkadot's interoperable ecosystem. For those interested in expanding their project to the blockchain space, Tanssi offers a straightforward, code-free application chain deployment platform. Explore and launch your project today at apps.tanssi.network . apps.tanssi.network apps.tanssi.network About Tanssi Network Tanssi’s appchain infrastructure protocol is designed to simplify and accelerate the deployment of appchains. By connecting a chain to Tanssi, it is instantly transformed into a modular appchain. This transition grants access to a developer-friendly and permissionless environment, fully stocked with all essential infrastructural components to run a chain right out of the box. Key features include a shared and decentralized network of block producers, ensuring robust security and data retrievability, alongside seamless integrations with vital tools like bridges, wallets, block explorers, RPC endpoints, indexers, oracles, and more. As a result, appchains can be deployed in just minutes—a significant improvement over the typical months-long process. Learn more at tanssi.network . tanssi.network tanssi.network About Grupo Flow Grupo Flow operates as a comprehensive media ecosystem, focusing on the creator economy with ventures in technology, content, media, production, and advertising. Central to the group is Estudios Flow, a creative hub housing over 30 creators dedicated to fostering dialogue, plurality, and transparency. Producing over 70 hours of content weekly across various formats and niches, Estudios Flow aims to build community ties nationwide. The ecosystem also includes Flow S.A., Flow Games, Flow News, Flow Sport Club, Venus, Ciência Sem Fim, Amplifica, the digital agency Golden Pill, software house WolfVision, and Flow Labs, specializing in audiovisual productions. The initiative traces back to the influential Flow, launched by Igor Coelho, a trailblazer in Brazil’s videocast arena. Learn more at linkedin.com/company/flow-grupo . linkedin.com/company/flow-grupo linkedin.com/company/flow-grupo Contact CMO Katherine Quilca Barcelli Moondance Labs kathy@moondancelabs.com This story was distributed as a release by Chainwire under HackerNoon’s Business Blogging Program. Learn more about the program here. This story was distributed as a release by Chainwire under HackerNoon’s Business Blogging Program. Learn more about the program here . here here

Tanssi Supports Grupo Flow In Major Blockchain Expansion On Polkadot

পোলকাডটসে প্রধান ব্লকচেইন সম্প্রসারণে নাচ গ্রুপো প্রবাহকে সমর্থন করে

Dance unterstützt Grupo Flow bei der großen Blockchain-Erweiterung auf Polkadots

Dance apoya al Grupo Flow en una importante expansión de blockchain en Polkadots

Dance soutient Grupo Flow dans une extension majeure de la blockchain sur Polkadots

डांस पोलकाडॉट्स पर प्रमुख ब्लॉकचेन विस्तार में ग्रुपो फ्लो का समर्थन करता है

ダンスがポルカドットの大規模なブロックチェーン拡張で Grupo フローをサポート

Dance는 Polkadots의 주요 블록체인 확장에서 Grupo Flow를 지원합니다.

Dance apoia grupo Flow na grande expansão do Blockchain em Polkadots

Dance поддерживает поток Grupo в крупном расширении блокчейна на Polkadots

Dance, Polkadots'taki Büyük Blockchain Genişlemesinde Grupo Flow'u Destekliyor

Dance hỗ trợ dòng chảy Grupo trong việc mở rộng chuỗi khối lớn trên Polkadots

Dance 在 Polkadots 的主要区块链扩展中支持 Grupo Flow

Ever thought about getting into gaming but lack the technical skills. Here's how you can create your first game in 30 minutes! 1. Create a account and select my games, new game then empty project Flowlab.io 2. Click on the canvas, select create. Under type, type grass and then select edit sprite. 3. Select browse, select category, pixel-blocks, the grass block and then ok. 4. Click and drag your grass block in place. Then click on the block and select clone. Duplicate the block to create a ground surface and then select done cloning. 5. Select the canvas again, select create and change the type label to person and edit sprite. (in the physics settings, make sure the object is movable) 6. Click on browse, select category then pixel-chars. Select a character and choose ok. 7. Drag your character into place. Click on it and select edit, then behaviours. To make your character move. Select keyboard in triggers, change the key to the right arrow key (make sure repeating is selected). Under logic & math select number, change the label to forward and the number to 6. Lastly, add velocity from properties. Connect down to get and out to x. Repeat this process but change the key to the left arrow, the label to backwards and the number to -6. 8. Now we're going to make our character jump. Select keyboard in triggers, change the key to the up arrow key. Under logic & math select number, change the label to jump and the number to 12. Lastly, add impulse from components. Connect down to get and out to y. 9. Add the flip block in properties. Then connect backward to flip and forward to back. 9. We're going to add an animation to our character. Click on the character and select edit sprite. Then select the animation column, pick animation, create new, then name it run. Select the plus icon and change the character image, repeat this two more times then press ok. Then add animation from the properties tab. Connect down from the left and right keyboard triggers to the start on the animation block and the up to the stop on the animation block. 10. Add a new object to ensure that your player doesn't fall off the map. 11. Add a new object called coins. Make sure it is not solid but enable collisions in the physics settings. (I've added some additional terrain). 12. Return to the behaviours setting for our player the add the collision block in triggers. Select coins as your type. Add the number block in logic & math and give it a label named score and a current value of 0. Then add the label tab in GUI and give it a value of 0. Connect the collision block's hit to the score block "+" and the score block to the label's value. Create another label block but this time type "score". Then click ok 13. Click and drag the labels to make the score and value clear. 14. Lastly, to make the coins disappear on the player collision. Select then coin and add a behaviour. Select the collision trigger and change the type to player. Add destroyer from components and link hit to destroy. 15. Congratulations, now you can test your platformer game. It should look something like the image below. Here's a link to our version: https://flowlab.io/game/play/1703330 In part 2 we will be adding more complex features such as music, enemies and health status. You can find an example here: https://flowlab.io/game/play/1702939

How to Make an Interactive Pixelated Game in 30 Minutes Without Coding 

We spend a large proportion of our lives debugging issues. Sometimes we just need an answer to a very simple question but getting that answer is a real struggle and can be time-consuming. On occassions I’ve seen a complicated 3rd party piece of technology thrown at the problem but often in these sorts of scenarios, linux already has you covered. Many of these command-line utilties either already come with a standard linux distribution or are one line away from an install from your specific distro’s preferred package manager. Here’s a list of command-line tools I think all developers should know how to use to answer simple questions. ps For answering the question: What’s running on my machine and what process ID does it have? There are many useful flags you can append to the command such as: ps -ef To list all processes in unix format OR: ps -aux To list all processes in BSD format. You can then grep this list to find the PID of the desired application, for example trying to find the PID of a running tomcat: ps -ef | grep tomcat Here’s some example output: andy@desktop:~$ ps -ef | grep tomcatandy   19822  1590 99 14:08 pts/1    00:00:06 /usr/lib/jvm/java-8-oracle/bin/java -Djava.util.logging.config.file=/home/andy/tomcat/apache-tomcat-7.0.56/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -XX:MaxPermSize=512m -Xmx2048m -Dcom.sun.management.jmxremote.port=9012 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Djava.endorsed.dirs=/home/andy/tomcat/apache-tomcat-7.0.56/endorsed -classpath /home/andy/tomcat/apache-tomcat-7.0.56/bin/bootstrap.jar:/home/andy/tomcat/apache-tomcat-7.0.56/bin/tomcat-juli.jar -Dcatalina.base=/home/andy/tomcat/apache-tomcat-7.0.56 -Dcatalina.home=/home/andy/tomcat/apache-tomcat-7.0.56 -Djava.io.tmpdir=/home/andy/tomcat/apache-tomcat-7.0.56/temp org.apache.catalina.startup.Bootstrap startandy   19848  7377  0 14:08 pts/1    00:00:00 grep --color=auto tomcat Here I can see a process running with a PID of 19822 Note: You will also see your grep in this output (the PID of _19848_ ). netstat For answering the question: What’s running on my machine and on what port? If I want to determine what’s listening on port 8000: sudo netstat tulpn | grep 8000 Here’s an explanation of what the different flags mean — more can be found with : netstat --help -t   # tcp ports-u   # udp ports-l   # only listening ports-p   # output PIDs-n   # resolve hardware names And if I have something running on this port, I get something along the lines of the following output: andy@desktop:~$ netstat -tulpn | grep 8000tcp        0      0 127.0.0.1:8000          0.0.0.0:*               LISTEN      16740/node Allowing me to or inspect the process that’s running as necessary. kill <pid> tcpdump For answering the question: What requests / packets are coming from and to my applications? If I’m interested in the requests and packets coming from and to port 8080, I can get a full dump of the traffic, requests and message body with this command: sudo tcpdump -A -s 0 -i lo port 8080 is the interface name. is the loopback interface and all traffic originating from your machine will go through this network interface. -i lo will debug and omit some strange characters. -A will print all packets since tcpdump doesn’t do this by default. -s 0 Here’s some example output showing a simple POST request to an application which performs a simple authenticated redirect with a username and password combo: 13:49:04.701180 IP6 (flowlabel 0x8a77f, hlim 64, next-header TCP (6) payload length: 817) ip6-localhost.52870 > ip6-localhost.http-alt: Flags [P.], cksum 0x0339 (incorrect -> 0x3fa7), seq 1861:2646, ack 2002, win 1373, options [nop,nop,TS val 4948070 ecr 4947571], length 785: HTTP, length: 785POST /login/?sessionId=941b5ac4-5524-4b43-b4b1-b9e371a7f212 HTTP/1.1Host: localhost:8080Connection: keep-aliveContent-Length: 49Accept: */*Origin: X-Requested-With: XMLHttpRequestUser-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.119 Safari/537.36Content-Type: application/x-www-form-urlencoded; charset=UTF-8Referer: Accept-Encoding: gzip, deflate, brAccept-Language: en,en-GB;q=0.9Cookie: sessionId=941b5ac4-5524-4b43-b4b1-b9e371a7f212; http://localhost:8080 http://localhost:8080/login/?redirect=/myApp username=username&password=password\[!http\] There are many other additional flags you can add to the command such as monitoring more than one port: sudo tcpdump -A -s 0 -i lo port 8080 or port 8000 Or capturing packets only from a single host: sudo tcpdump -A -s 0 -i lo port 8080 and src host 1.2.3.4 telnet For answering the question: Is there a network issue preventing me from connecting to my resource? telnet <host> <port> Here’s some example output — I have no active processes running and listening on port 8000 on my local machine so I can’t connect to them: andy@desktop:~$ telnet localhost 8000Trying 127.0.0.1...telnet: Unable to connect to remote host: Connection refused Say for example I’m trying to determine whether I can connect to a remote instance of postgres in my network, I already know the instance is up and there are no networking issues — I already know the hostname and know that postgres listens on : TCP 5432 andy@desktop:~$ telnet myRDSinstance.eu-west-1.rds.amazonaws.com 5432Trying 172.20.15.200...Connected to myRDSinstance.eu-west-1.rds.amazonaws.com.Escape character is '^]'. I will receive a message which shows I have made a TCP connection to my resource. Or if I fail to connect I will see something similar to the following message: andy@desktop:~$ telnet myRDSinstance.eu-west-1.rds.amazonaws.com 5432Trying 172.20.15.200...telnet: Unable to connect to remote host: Connection refused Giving me evidence to suggest network connectivity issues as the culprit for my particular issue.

Developer’s Toolkit: 4 linux command-line tools for debugging everyday issues that all developers…

NOTE: I’ve deprecated Flowless (and have abandoned using Flow) in favor of what I wrote based on that from scratch: Simple-Stack . So you should keep in mind that I am no longer using this, because Simple-Stack solves quirks that I didn’t like about Flow’s design. — — — — — — — — — — — — — — — — — — — — — — — — — This is a follow-up article to . Saying No To Fragments and Activities: Creating View-driven Applications with Flow While I claimed that that article will get to the point, it was more-so a comparison of how things are lately with (and ), . So one could argue that it did not get straight to the point, after all. Flow 1.0-alpha2 Flowless versus how things used to be with Flow 0.8 So let’s get to it, shall we? Flow: a backstack manager As , the primary task of Flow (and the instance itself) is to manage the . All it really cares about is the (essentially a ), and exposes operators that allow it. stated in a previous article Flow backstack History List<Object> manipulating Keys: representation of application state The primary difference using Flow compared to just Activities is that instead of having an , you have a History of “key” objects that are just general Parcelable objects with and that represent what view you’re supposed to be showing. implicit backstack created by a series of Intents that open a bunch of Activities hashCode() equals() (In fact, it doesn’t have to be a view, if you’re a heretic, you can even use Fragments with it. No, really; just use the newly added _FragmentManager.commitNow()_ , and don’t use _addToBackStack()_ , defer backstack manipulation to Flow instead. Theoretically, it should work, although I must admit I haven’t tried it yet.) A possible example key would be the following: But if you don’t like extracting values from annotations, then you can just use interfaces and method calls. It’s up to you! This allows simple initialization for what your application state should be. And it also allows you to easily set whatever view you want to test with instrumentation tests. You might be thinking, “wait, but this is a whole bunch of methods in the key, I thought this was going to make my life simpler?!” Actually, it does. Exactly because this kind of “behavior” that is encoded here in the key used to be thrown randomly into Fragments, that were manipulating the Toolbar title in the Activity directly. Here this is something you can globally do in your dispatcher implementation, and it’s set properly on back press too with minimal effort (in fact, it works out of the box). Custom Views, and listening to the lifecycle This is a -specific feature, partly piggybacking on top of the fragment in the original Flow. Flowless InternalLifecycleIntegration You generally need to know when your View is ready and its state is restored. You must also know when your View is killed, so that you can unsubscribe your subscriptions, or unregister from event buses. Previous Flow examples used to show and as the callbacks to be used, but that is actually unreliable. There are cases when is called, but is not. In that case, you do not receive any callback to , which means that you can lose your state! onAttachedToWindow onDetachedFromWindow onFinishInflate() onAttachedToWindow() onDetachedFromWindow() If you’re curious, this is most likely why the library exists. square/coordinators Instead, Flowless introduces the interface, which if you implement, then provides you the callbacks: and . FlowLifecycles.ViewLifecycleListener onViewRestored() onViewDestroyed() Additional lifecycle callbacks In other cases such as writing a , you might need to listen to permission results, or activity results. CameraView For and , you need to delegate these callbacks to the Dispatcher manually. onActivityResult onPermissionResult A possible base activity that hides this from you would be the following: Once the permission result delegation is added, the dispatcher forwards this event to the current active view. This way, you can handle any lifecycle event callback you need in your view. ServiceProvider: sharing services across the view hierarchy This is a new class in Flowless, its counterpart used to be .with its corresponding . The is pretty much just a that is stored inside Flow’s to preserve them across configuration change, very similar to Mortar which is essentially a . The initial key in this case of course is the itself, and not a “scope name” specified as a String. Flow.Services ServiceFactory ServiceProvider Map<Object, Map<String, Object>> InternalLifecycleIntegration Map<String, Map<String, Object>> Key The difference is that in the original Flow 1.0-alpha2, the were managed internally based on a reference count, based on interfaces such as or . This could cause problems even if you weren’t using it, which is what caused the crash that made me fork Flow and create Flowless in the first place. Flow.Services TreeKey MultiKey Instead, in Flowless, the expects you to set it up in the Dispatcher however you see fit. ServiceProvider Through , the allows you to obtain any service from your context, just like you can obtain Flow via . the magic of redefining [getSystemService()](https://github.com/Zhuinden/realm-book-example/commit/619546401dcade1fbc02001e8b12d71bfcec2952) ServiceProvider Flow.get(context) Sharing a Dagger2 component In the MVP example, this is how scoped components are provided down the view hierarchy. This allows us to obtain the Dagger2 component from any context — primarily within views of the custom view’s view hierarchy. Dispatcher: which determines what happens on state change The last and most important component of a Flow-based application is its Dispatcher implementation. This is what globally handles what should happen when you go from Key A to Key B. The most typical implementation would persist the state of the previous view, inflate the new view, restore state to the new view, remove the previous view, add the new view, and callback to signal completion. The following example also adds the Dagger2 component by and associate it with the given key, making the component accessible within the view hierarchy. DaggerService.TAG In the middle, you can see the Service being set up for the current key: the Dagger2 Component. This is basically where the “magic” happens. In this case, it’s 60 lines with comments, compared to the FragmentManager that is 2000 lines. I guess there’s a win there in simplicity. Conclusion Hopefully this helped understand how to use , and how to create a simple MVP-based (or maybe even MVVM-based with Data-Binding or RxJava!) application without using fragments or any kind of additional “arcane folklore” beyond an explicit backstack. Flowless The app is driven with just simple parcelable POJOs, and you write how to switch between the states only once. Simpler than either s or s. FragmentTransaction Intent The example cited multiple times during this article is available . Flow is primarily responsible for the way the layer works. here presentation

Simpler Android apps with Flowless 1.0-RC2 (or Flow 1.0-alpha2)

How to Create Scrollable Lists with Protocol-Oriented Design & UICollectionViewCompositionalLayout

প্রোটোকল-ওরিয়েন্টেড ডিজাইন এবং UICollectionViewCompositional Layout সহ কীভাবে স্ক্রোলযোগ্য তালিকা তৈরি করবেন

So erstellen Sie scrollbare Listen mit protokollorientiertem Design und UICollectionViewCompositionalLayout

Cómo crear listas desplazables con diseño orientado a protocolos y UICollectionViewCompositionalLayout

Comment créer des listes déroulantes avec une conception orientée protocole et UICollectionViewCompositionalLayout

प्रोटोकॉल-ओरिएंटेड डिज़ाइन और UICollectionViewCompositionalLayout के साथ स्क्रॉल करने योग्य सूचियाँ कैसे बनाएँ

プロトコル指向設計と UICollectionViewCompositionalLayout を使用してスクロール可能なリストを作成する方法

프로토콜 지향 디자인 및 UICollectionViewCompositionalLayout을 사용하여 스크롤 가능한 목록을 만드는 방법

Como criar listas roláveis com design orientado a protocolo e UICollectionViewCompositionalLayout

Как создавать прокручиваемые списки с помощью протокольно-ориентированного дизайна и UICollectionViewCompositionalLayout

Protokol Odaklı Tasarım ve UICollectionViewCompositionalLayout ile Kaydırılabilir Listeler Nasıl Oluşturulur

Cách tạo danh sách có thể cuộn với thiết kế hướng giao thức & UICollectionViewCompositionalLayout

如何使用面向协议的设计和 UICollectionViewCompositionalLayout 创建可滚动列表

Enabling Acoustic Audience Feedback in Large Virtual Events: Conclusions & References

Creating Scrollable Lists using Protocol-Oriented Programming and UICollectionViewFlowLayout

According to Gartner’s , low-code application development will account for more than 65% of software development activity by 2024. It seems that the need for highly customizable yet easily manageable solutions has been steadily increasing over the past years. estimates For all the benefits of low-code platforms, there are certain limitations that stem from the target area of their application options. For example, there are low-code solutions tailored for web development, mobile development, business processes management, etc. In other words, there is no universal low-code software that would fit any business and any development task. However, when choosing a platform for low-code development, one can consider several factors that are common for all areas. Today, we’ll look into the main features and requirements for low-code software and compare a few solutions available on the market. User-friendly interface Drag & Drop editors enabling simple creation of applications is at the core of the low-coding approach. Even business users with no technical background will be able to build workflows or entire apps with an intuitive and user-friendly GUI. When choosing a low-code platform, it’s crucial to make sure that your employees are comfortable while working with it. Even though they all have visual builders, they might differ significantly in terms of available options, customizations, and ease of use. Some vendors offer free trials so that you can test-drive their solution and see if it suits you. For example, platforms like or for automating processes and building workflows have a visual editor enabling you to easily model, create and edit interactive workflows of any complexity. Flowable OptimaJet Workflow Engine Customization options There’s often a need to adapt low-code software to your business processes and users, so it’s important to find out if the chosen solution is customizable enough. At the very least, you should be able to extend or modify its functionality with the help of add-ons or plugins. Some vendors can apply necessary modifications at the request or, in some cases, even provide the source code. For instance, OptimaJet Workflow Engine, a BPM low-code platform, offers customers its source code so that they can make necessary customizations to maximize productivity. Integrations It’s also worth checking whether the low-code platform you’re considering adopting integrates well with all the software and data types used in your company. In case there are a number of technologies used by different departments or business units (for example, if both .NET and Java are used), it’s important to make sure that the platform can be integrated with all of them. Some vendors offer in-built connectors to integrate with popular software tools; and most of them provide API interfaces as a more flexible integration opportunity. And while the former can be easily dealt with by an employee with no technical background, integrations via API will require some coding. Data access rights Working in low-code tools often requires granting users different access rights and permissions. This is especially crucial when used in large enterprise systems since access to specific data needs to be restricted. This is why, when choosing a low-code platform, data access rights are to be taken into account. Depending on your situation, you might need a more or less complicated permissions hierarchy and level of flexibility. For example, some of your employees might need access to different parts of the system but with different rights (to view, edit, or delete). In this case, the platform should be able to provide flexible permissions settings. Customer support Last but not least is the availability of technical support provided by vendors. When implementing comprehensive low-code solutions, the need for additional information or consultations often arises. Without professional and timely customer support, you might find it difficult and inconvenient to use the platform. What’s more, constant communication with customers enables vendors to better understand users’ requirements and add demanded features as they launch updates. So, if you have an opportunity to check the work of customer support in advance, this would be another point in the decision-making process. Low-code solutions comparison We have analyzed five popular low-code platforms aimed at business process automation: Although the basic functionality of these platforms is more or less the same, you might find one of them more convenient and better fitting your business needs than the others. We’ve chosen platforms with a free trial period so that you can test drive them and make an informed choice. In the end, it doesn’t matter if you choose or , , or — they can all provide you with the necessary tools for low-code development. Camunda Nintex OptimaJet Workflow Engine Nuxeo Flowable

5 Best Low-Code Development Platforms in 2022

IoT and smart buildings are all about data, but how is all this data used and what kind of data can you get? In this article, we share some examples of what kind of IoT data you can get in smart buildings and how it’s commonly used. Optimizing spaces with utilization data . Companies are always looking to create the best possible working spaces for their employees and to do that, they need to know how their spaces work. In addition, the question of space optimization and rental costs is always on every facility manager’s mind: In the 2017 , Jones Lang LaSalle reported that most corporate real estate executives estimate that 20% of available space is wasted, and this number can be even higher! Getting utilization data is highly important for modern facility management Occupancy Planning Annual Report with utilization data helps you reorganize your spaces by giving you insights on how to maximize your space usage, improve sustainability and reduce your company’s infrastructure costs. Optimizing your space usage With utilization data, can be determined based on facts, and thus action towards improving any under-used spaces can be taken. IoT data in smart buildings can show the popularity of different spaces in various ways: how many persons use the space on average per day, what are the peak hours or days, and so on. the popularity of different spaces With space utilization data, users can see free and occupied desks, meeting rooms, and other areas. This saves time and enables activity-based working in the office. The next step would be to find out if maybe the spaces are uninviting, have some necessary function missing or if there’s another reason people don’t want to use them. Having utilization data is also very interesting when moving into a new space. The data can be used to , how it flows, and what are the least used areas. This enables quick changes to be made so you can max out your space usage, further reducing your costs related to your real estate. test the new space on how it works Real-time usage & occupancy analytics Having real-time usage data from the building allows a way to of the building. This is done by monitoring the HVAC system and the electricity usage in the building. improve the environmental footprint When a room is not being used, there is no need to have the air conditioning keeping that room to a nice and chilly temperature. This energy can be saved or used to boost the air conditioning in other rooms, where it is actually needed. has a great use case in . Determining the most popular rooms with their peak hours and days enables, for example, automated heating and air conditioning optimization. This reduces the energy needed in the building. Real-time usage data facility management IoT utilization data can also help you prepare for unusual times: , companies with access to space utilization data have not just been able to set occupancy limitations to their spaces, but they also have been able to monitor this to ensure the safety of their employees. During COVID-19 Smart cleaning The same idea applies to When using occupancy information, there is a clear way to keep the most used spaces clean. Shifting from a schedule-based cleaning to a more need-based cleaning saves time and money and helps to ensure a higher standard of hygiene. smart cleaning. As with the utilization data, the real-time usage and occupancy data of a space can be used for . The occupancy data is very useful in spaces with a raised need for hygiene, such as in restrooms or hospitals. The time between in which the rooms have been used is very handy in helping to keep the building hygienic COVID-19 protocol enforcement Fill rate data and monitoring of the paper, towel, and soap dispensers, as well as trash bins, is most commonly used in smart cleaning solutions. With fill rate monitoring, the cleaning staff needs to do fewer unnecessary checks, saving time and steps while the users can always rely on having a well-stocked dispenser in their facilities. Monitoring the fill rates Here are some findings from textile service company Lindström on their : Flowability washroom solution Environmental data With IoT devices, you can from your smart building. Getting environmental data on your spaces helps you make sure your spaces offer healthy and safe conditions for the users, enables them to find areas best suited for them, and helps facility managers to keep track of heating and air conditioning needs. get a variety of environmental data Environmental data in buildings can be air quality, temperature, air pressure, or illuminance for example. Indoor tracking Using IoT devices data in smart buildings can also enable indoor tracking. In this context, indoor tracking can be either the or the . When considering the use case in location tracking for employees, it should always be a voluntary sharing tool. location of the workforce location of certain equipment Indoor tracking enables finding colleagues, allowing for better communication with them and cooperating better with team members and coworkers. It is especially neat when you need to find someone outside of your regular team, as you may not know where they usually sit. When using location tracking, the users can see , and maybe find some company to grab lunch with. who is around at the office for different tasks Location tracking in smart buildings is usually done with keycards, tags, or Bluetooth-enabled trackers people always carry with them. The data is then displayed on a digital twin of the office. As mentioned earlier, in addition to finding people, indoor tracking can be used with certain equipment. It might be that some of this and therefore needs to be tracked within the building, or that you want to monitor your inventory levels with the solution. Using indoor tracking for equipment can also help you understand equipment usage better and reduce the risk of loss and theft. equipment is critical to find Conclusion IoT data has a multitude of use cases in smart buildings. Whether you want to optimize your space usage or track critical equipment, . IoT data makes all this possible Read more about IoT devices and what they are capable of from our IoT devices guide.

IoT in Smart Buildings – A Behind-The-Scenes Picture on Data Utilization

Context I thought it was time to write a about how to design a proper, architecture that you may apply to any . This series of articles is the sum of all the knowledge that I’ve learned from working on different projects for different companies. For obvious reasons, I cannot disclose any information, but I can tell you that I’ve worked on projects for social network apps, cruise apps, airplane apps, e-commerce apps, radio streaming apps, and bank apps. Working on all these different projects has taught me the that you need to keep in mind when you are working on a large project. There are things related to the and there are things related to how the architecture that you choose to apply is going to impact your . series of articles scalable medium-large projects does and donts technology itself engineering team Before you start This article assumes that you are at a or . That means that you feel comfortable working with the most well-known technologies related to Android development, such as Dagger, Kotlin, RxJava, Google-related libraries (FCM, Remote Config, Crashlytics) and obviously, the Android SDK. semi-senior senior level I’m going to start talking about the , then show the that I have created for this article, and then in the next article I'll go on through each of the architecture. tech-stack setup example app layer Tech-stack setup Since some time ago I have permanently moved from to because MVVM has become the first Android architecture, through Android’s LiveData and ViewModels. Also, since this article aims towards a architecture this is going to be a architecture, with , a , and a . MVP MVVM officially supported large-scale multi-module feature modules core module base module The technologies that I’m going to use here are; for dependency injection, as my networking layer, to wrap the network layer into repositories. Dagger OkHttp/Retrofit RxJava Example App I have created as an example - no pun intended - of how this architecture works. This example app shows different real world scenarios, scenarios where we have to use cache, perform search, mix different endpoints, and so on. an example app Each shows different use cases and different scenarios. I often see that when you look for examples online you only see the most straightforward, simple and unrealistic scenarios¹. For example, just fetching something from the backend and display it on the UI. In my personal experience that’s not how real-world development works like. In the real world, you’re going to have to go back and forth with different resources within your company, and due to different constraints you may have to settle with some-what good API endpoints², or you may have to hit different endpoints to display the whole information to the user. feature module RxJava Example #1 The "RxJava Example #1" shows how we can conditionally zip two API calls together. In this example, we use two different endpoints to fetch the "recently viewed news" and the regular paginated news. If we do a Pull-to-Refresh or open the Activity from scratch, we are going to fetch both, the recently viewed news and the first page of the paginated news. If we continue to scroll down until we reach the next page, we are only going to call the API to fetch the second page. This example also handles error situations like doing a Pull-to-Refresh without internet connection . RxJava Example #2 The "RxJava Example #2" shows how we can zip responses from different endpoints through RxJava. In this example, we zip the responses from two different endpoints, one that provides the user's "business skills information" and another that provides the user's "personal information". We zip these requests together through RxJava and use wrapper objects to carry the responses around. Also, we handle different error situations for each endpoint and update the UI accordingly. This example supports Pull-to-Refresh behavior and handling no internet connection states. Cache Example The "Cache Example" shows how we can use a and a to display data to the user, update data dynamically, and without using any sort of EventBus technology, get these updates into the UI by relying on Room's Flowables. cache repository network repository In this example, we fetch a list of recipes from a mock endpoint host on ApiAry, store those recipes on cache, and allow the user to bookmark the recipes. When we bookmark a recipe we can see the change reflected on the recipe list as soon as we do it, all this thanks to Room's Flowables. This example also supports Pull-to-Refresh behavior and handles different error states, such as trying to fetch the list of recipes without internet connectivity. LiveData Example The "LiveData Example" shows how we can achieve a complex search by relying on LiveData. In this example, we can search image posts using the , through this API we are able to search using a String as the search term, and we have a few filtering options. We can select if we want to get the posts (Top) or if we want to get the posts (Viral). If we choose to filter by top posts, we can also specify a date windows, getting the top posts from the , , or . Imgur API query latest most trendy day week month This example supports handling the Pull-To-Refresh gesture and pagination. Also, we handle different error states such as trying to search for something without internet connection (it shows a Snackbar if we are seeing content or a full error state if we open the Activity from scratch). All this is done through LiveData. Notes [1] By unrealistic scenarios I mean when you go through an article and they show you how to fetch data, save it on cache, and display it on a RecyclerView. That’s all well and good; But what happens if you fetch a 500 (Internal error)? What happens if you fetch a 304 (Not Modified)? Do you waste time and store a duplicate response on the cache? What happens if there’s no internet connection? All these edge-case scenarios, that are actually very likely to happen in the real world, are totally omitted by most articles. [2] Some may argue that if this was to happen, you should push forward and settle for nothing else other than what you want. But that’s not how a company works. A company needs to deliver a product. Backend and frontend developers, they have deadlines, and trying to fix an endpoint so it is more mobile-friendly may take time, time that the backend resources don’t have.

A Production Level Architecture for Android Apps [Part 1]

Stories, News & Mentions about FLOWLABS

Flowlabs’s Stories on HackerNoon