<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[greypbikes - Medium]]></title>
        <description><![CDATA[Greyp Bikes is a tech company designing, engineering, and producing the world’s first fully connected e-bikes. - Medium]]></description>
        <link>https://medium.com/greypbikes?source=rss----f2d1bb7a0d0e---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>greypbikes - Medium</title>
            <link>https://medium.com/greypbikes?source=rss----f2d1bb7a0d0e---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 01:41:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/greypbikes" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[3D Bike Model Visualization (Angular + Hoops)]]></title>
            <link>https://medium.com/greypbikes/3d-bike-model-visualization-angular-hoops-d85b6289775b?source=rss----f2d1bb7a0d0e---4</link>
            <guid isPermaLink="false">https://medium.com/p/d85b6289775b</guid>
            <dc:creator><![CDATA[Helena]]></dc:creator>
            <pubDate>Tue, 17 Jan 2023 10:53:12 GMT</pubDate>
            <atom:updated>2023-01-17T10:53:12.759Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Let’s assume you’re building a web solution and you stumble upon a CAD web viewer requirement. It may sound overwhelming and one may get stuck and wonder about the right approach. Luckily, this article covers most of the questions and provides you with the needed actions. So, let’s dive right in!</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*z67uut1OCfddxcmnaNsydQ.gif" /><figcaption>Exploded view of a Greyp T5 model</figcaption></figure><p>These days, 3D modeling has an important role in both automotive and bicycle industry in terms of saving time and money in producing vehicle parts. The tool-of-choice highly depends on the actual company needs and can be picked from a large variety of CAD software on the market. Nevertheless, the ones that you most likely have heard of are AutoCAD, SolidWorks and Catia (among others). Of course, there are advantages and disadvantages using one over another, but this article is not going into that discussion. To continue, each of them has a special file extension what leads us to the point of a realization that we need somewhat of a converter to be able to display model in a browser. In this article, for that purpose, Hoops Communicator graphics engine will be used.</p><p>According to the official documentation, Hoops Communicator is an SDK for development of 3D engineering applications in a web browser. Using Hoops Communicator developers can quickly add 2D and 3D CAD viewing and interaction functionality in all browsers. It’s main component is the Hoops Web Viewer, a powerful and flexible Javascript library and it provides a lot of fun features like CAD preview, model tree, selections, filtering and layering, 2D drawings, configurations and much more.</p><h3>Get started with Hoops trial</h3><p><em>This tutorial may be different for other operating systems.</em></p><ol><li>You will need to register a new account in order to fetch your free trial solution <a href="https://www.techsoft3d.com/">Tech Soft 3D</a>.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R-tIF0aUZOJuGwdwswcJ6w.png" /><figcaption>Signup page Tech Soft</figcaption></figure><p>2. After successful registration navigate to the <a href="https://www.techsoft3d.com/products/hoops/web-platform">products page</a> and click on the Start a free trial button. You will see a popup window with your trial license key and available solution depending on the operating system. Save your license key and download your installer or package. After running your downloaded installer you will need to enter the saved license key and in the upcoming step select Hoops Web Platform solution. As explained, the Hoops Web Platform provides advanced 3D web visualization and CAD data access software development toolkits.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0Z1XoMJx_BHCjk5wfgEqLg.png" /><figcaption>Installer step</figcaption></figure><p>3. After successful installation you need to locate your Hoops Installer folder and navigate to the quick_start. Quick start folder contains already converted models, a script for the model conversion and a start server batch file. In order to convert your model (if extension supported) you need to run the mentioned server and then simply drag your model onto the convert batch file. If your server is properly running, you will get immediate preview of your model in a browser. The converted file will be located in the converted models folder under user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RA9hT9lcE6YLAlPBbQHmRQ.png" /><figcaption>Conversion done successfully</figcaption></figure><p>4. Now to the fun part. Following the next couple of steps you can render converted model in your Angular project. This example is not using streaming or viewing sessions features so we don’t need a running server. First, find <a href="https://github.com/techsoft3d/hoops-web-viewer">Hoops Web Viewer client scripts</a> and add them to your new or existing Angular project (the latest or a specific version).</p><pre>&lt;script type=&quot;text/javascript&quot; src=&quot;https://cdn.jsdelivr.net/gh/techsoft3d/hoops-web-viewer@latest/hoops_web_viewer.js&quot;&gt;&lt;/script&gt;<br>&lt;script type=&quot;text/javascript&quot; src=&quot;https://cdn.jsdelivr.net/gh/techsoft3d/hoops-web-viewer@2020.1.0/hoops_web_viewer.js&quot;&gt;&lt;/script&gt;</pre><p>After that, declare var Communicator in project typings.d.ts file.</p><pre>declare var Communicator: any;</pre><p>Next, you should place your previously converted file in the projects assets. You need to add the code attached below to the app component ngOnInit callback method.</p><pre>const hwv = new Communicator.WebViewer({<br>      containerId: &quot;visualization&quot;,<br>      endpointUri: &quot;assets/models/t5_xl_assembly-v03r03.asm.scs&quot;<br>    });</pre><p>Not to forget, you need to add your visualization container to the component template. You can style it the way you prefer.</p><pre>&lt;style&gt;<br>    #visualization{<br>        width: 640px;<br>        height: 480px;<br>        position: relative;<br>    }<br>&lt;/style&gt;<br>&lt;div id=&quot;visualization&quot;&gt;&lt;/div&gt;</pre><p>Now let’s connect the Hoops Web Viewer component with the empty visualization container we just created by adding the following lines right after the reference to the Hoops Web Viewer library. Also add sceneReady, this callback gets triggered as soon as the Web Viewer is active and can be interacted with. You should only do actions on the viewer after this callback has been triggered.</p><pre>hwv.start();<br>    hwv.setCallbacks({<br>      sceneReady: () =&gt; {<br>        console.log(&quot;HOOPS Web Viewer has been initialized.&quot;);<br>      }<br>    });</pre><p>There are more callbacks that are extremely useful, for instance modelStructureReady and camera.</p><pre>modelStructureReady: () =&gt; {<br>        console.log(&quot;Model structure ready.&quot;);<br>    },<br>    camera: () =&gt; {<br>        console.log(&quot;Camera view has changed&quot;);<br>    }</pre><p>Finally, you should run your project and test if everything is working properly. You should end up with your model fully rendered with basic functionality (rotate, zoom and selection).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*RWOSWkKDQc3KqE_PVqF42w.gif" /><figcaption>Custom model visualization</figcaption></figure><h3>To sum up…</h3><p>As seen from the example, it’s really easy to achieve basic preview of a CAD model using Hoops Web Viewer Platform. If you want to enrich your web application with high quality rendering and visual effects like ground shadows, reflections and ambient occlusion you should consider this solution. Furthermore, you should definitely explore other fascinating functionalities of the platform by reading <a href="https://docs.techsoft3d.com/communicator/latest/index.html">technical documentation</a>. Thankfully, technical documentation is really helpful and there are plenty of examples to keep you going. On the downside, Hoops is not open source or free, but trial gives you enough time to explore it and decide about purchase.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d85b6289775b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/greypbikes/3d-bike-model-visualization-angular-hoops-d85b6289775b">3D Bike Model Visualization (Angular + Hoops)</a> was originally published in <a href="https://medium.com/greypbikes">greypbikes</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Running Spring Boot App in Docker Using IntelliJ IDEA]]></title>
            <link>https://medium.com/greypbikes/running-spring-boot-app-in-docker-using-intellij-idea-db09980f803f?source=rss----f2d1bb7a0d0e---4</link>
            <guid isPermaLink="false">https://medium.com/p/db09980f803f</guid>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[spring-boot]]></category>
            <category><![CDATA[docker-compose]]></category>
            <category><![CDATA[java]]></category>
            <category><![CDATA[intellij]]></category>
            <dc:creator><![CDATA[Branimir Đurek]]></dc:creator>
            <pubDate>Fri, 25 Nov 2022 14:25:02 GMT</pubDate>
            <atom:updated>2022-12-02T19:23:21.482Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wwJKJDCYgGs2vDRjhs6bdA.jpeg" /><figcaption>© Katarina Kokanović, 2022</figcaption></figure><h3>Introduction</h3><p>Docker is a tool designed to make it easier to create, deploy and run applications in isolated environments, the so-called “containers”. Because of this, you don’t have to install every single piece of software directly on your machine. When it comes to the backend development, it is a perfect tool to run services like web server, database, search engine, etc.</p><p>In this guide, we’ll discuss how to setup, run and debug a Spring Boot application in Docker on your local machine by using IntelliJ IDEA.</p><h3>Prerequisites</h3><p>Before we begin with this guide, make sure you have the following software on your machine:</p><ul><li>IntelliJ IDEA → <a href="https://www.jetbrains.com/toolbox-app/">Install IntelliJ IDEA via JetBrains Toolbox</a></li><li>Docker →<a href="https://docs.docker.com/get-docker/"> Install Docker</a></li><li>Docker Compose →<a href="https://docs.docker.com/compose/install/"> Install Docker Compose</a></li></ul><h3>Setup your project</h3><p>Open your IntelliJ IDEA and follow these steps:</p><ol><li>Navigate to File &gt; New &gt; Project from Version Control...</li><li>Enter the following URL → <a href="https://github.com/bdjurek/spring-boot-app-in-docker-using-intellij">https://github.com/bdjurek/spring-boot-app-in-docker-using-intellij</a></li><li>Select a desired directory for the project</li><li>Press Clone button</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/891/1*C1o1NqaeWZ0TqMlvtdvYxA.png" /><figcaption>Create a new project from existing Git repository</figcaption></figure><h3>Project overview</h3><p>The idea is to run a Spring Boot application in Docker alongside MySQL and Redis service.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/691/1*KCkntJnoGHLD5TCYLBspSw.png" /><figcaption>Simple communication overview</figcaption></figure><p>Now, let’s break down thedocker-compose.yml configuration file.</p><p>First thing we need to do is to setup the app service using the following configuration:</p><pre>version: &#39;3&#39;<br>services:<br><br>  app:<br>    image: amazoncorretto:17-alpine<br>    ports:<br>      - &quot;8080:8080&quot;</pre><p>We need to define which docker image is going to be used for the app (in this case <a href="https://hub.docker.com/_/amazoncorretto">amazoncorretto</a>). Then, we need to bind the host machine 8080 port to the app container 8080 port so that we can easily access the app via the URL <a href="https://localhost:8080.">https://localhost:8080.</a></p><p><em>You will notice that IntelliJ IDEA ignores the port mapping defined on </em><em>app service and selects a random port every time you run the app. It can become annoying after a few reruns. Hopefully, this will be fixed in a future release. You can find more details regarding the issue </em><a href="https://youtrack.jetbrains.com/issue/IDEA-284458"><em>here</em></a><em>.</em></p><p>Finally, we need to setup mysql and redis service using the following configuration:</p><pre>  mysql:<br>    image: mysql:8.0<br>    ports:<br>      - &quot;3306:3306&quot;<br>    environment:<br>      MYSQL_DATABASE: demo_app<br>      MYSQL_ROOT_PASSWORD: demo_pass<br>    volumes:<br>      - mysql_data:/var/lib/mysql<br><br>  redis:<br>    image: redis:latest<br><br>volumes:<br> mysql_data:</pre><p>As you can see from the configuration above, we want to have direct access to the MySQL from the host machine. Also, we will mount docker volume on the path where MySQL stores the data so that we don’t lose it when the container is recreated.</p><p>Regarding the Redis, we only need to define which image we want to use. Later on, we can easily add port mapping so that we can access it directly from the host machine.</p><h3>Running the app</h3><p>Before we can run the app, we need to define Run/Debug configuration in IntelliJ IDEA (if you have pulled the project from the mentioned repository, you will already have the following configurations).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/888/1*R9q7FyDAiMlvftzaTP4WYA.png" /><figcaption>Choose a new Spring Boot configuration</figcaption></figure><p>Create a new target on which the app should run:</p><ol><li>For Run on property select: Manage targets... &gt; + &gt; Docker Compose</li><li>Choose the location of your docker-compose.yml file</li><li>Choose the app service from your docker-compose.yml file</li><li>Create and select newly created target</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/836/1*XDViP-BM6a4WiKNTH_J1pg.png" /><figcaption>Choose a run target</figcaption></figure><p>After you set the target, you can customize some properties shown in the image below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/888/1*nWwiBaGa9pBnrcxQmWJBcA.png" /><figcaption>Full configuration overview</figcaption></figure><p>Some properties worth mentioning:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/766/1*RX71PM2GS51jyI_rja35kw.png" /></figure><p>When you select Run application and press the Run icon, IntelliJ IDEA will build your app, run dependent services and run the app inside a docker container.</p><h3>Debugging the app</h3><p>Using the debugger is quite easy.</p><p>Just place your breakpoints in the code and press Debug icon on your Run application configuration.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F775039590%3Fh%3Deada530def%26app_id%3D122963&amp;dntp=1&amp;display_name=Vimeo&amp;url=https%3A%2F%2Fvimeo.com%2F775039590&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F1554940883-b845d01cc85f9ff8f5218f7f3b6bd77787db6b07e39fcc0279bf06c591db61d7-d_960&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1078" height="778" frameborder="0" scrolling="no"><a href="https://medium.com/media/d9cb2d673a4d9e797ce1dd175b29274e/href">https://medium.com/media/d9cb2d673a4d9e797ce1dd175b29274e/href</a></iframe><h3>Benefits</h3><p>This approach has a number of benefits, such as:</p><ul><li>One-click action to run/debug the app with all dependent services.</li><li>Changing JDK version is much easier, especially when you are working on multiple projects.</li><li>Possibility to reuse the existing docker-compose.yml configuration for Testcontainers library.</li><li>All project team members can share the same Run/Debug Configurations.</li></ul><h3>Conclusion</h3><p>In this guide we have covered how to setup, run and debug a Spring Boot application in Docker using IntelliJ IDEA and what are some benefits of this approach. We get a powerful and easy-to-use development setup when these tools combine together.</p><p>Stay tuned for more guidelines in order to get the most of your development setup.</p><p>The source code of this project is <a href="https://github.com/bdjurek/spring-boot-app-in-docker-using-intellij">available on GitHub</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=db09980f803f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/greypbikes/running-spring-boot-app-in-docker-using-intellij-idea-db09980f803f">Running Spring Boot App in Docker Using IntelliJ IDEA</a> was originally published in <a href="https://medium.com/greypbikes">greypbikes</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ANT+ in mobile software QA landscape]]></title>
            <link>https://medium.com/greypbikes/ant-in-mobile-software-qa-landscape-74bf1dc83d50?source=rss----f2d1bb7a0d0e---4</link>
            <guid isPermaLink="false">https://medium.com/p/74bf1dc83d50</guid>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[fitness-equipment]]></category>
            <category><![CDATA[connectivity]]></category>
            <category><![CDATA[testing-tools]]></category>
            <dc:creator><![CDATA[Damir Ban]]></dc:creator>
            <pubDate>Fri, 25 Nov 2022 08:54:16 GMT</pubDate>
            <atom:updated>2022-12-05T08:31:00.892Z</atom:updated>
            <content:encoded><![CDATA[<p>On the technology side of Greyp Bikes, it was always about combining different aspects of cycling and technology to give our customers a more connected and involving experience with their e-bike. But there is only so much that you can fit in a time &amp; budget-constrained hardware project before you need to release it to the market. What you can keep evolving and improving in shorter iterations once the product is out is the software. For the mobile app development team, this means that integrations with other hardware products, which cannot be resolved through the hardware already released on the e-bike, can also fall into our domain. Examples of these are speed and cadence sensors, cycling computers, power meters, different wearables, electronic shifters and such.</p><p>There is a fairly large number of devices on the bike components or fitness market that we would potentially like to integrate. For that reason, we investigate different solutions to simulate and mock the communication before actually investing in physical devices to polish the final integration. Historically, the communication protocol of choice in that space was ANT, backed and pushed by Garmin. This protocol later evolved into ANT+.</p><h3>ANT+ in general</h3><p>ANT (Advanced and Adaptive Network Technology) is a short-range wireless communication protocol with an emphasis on extremely efficient power usage on the radio level. The requirement was to prolong the battery lifespan in small sensors or remote devices that draw power from 3V button cell batteries.</p><p>ANT was invented by Dynastream Innovations, now part of Garmin. At the time when Dynastream Innovations introduced the first speed and distance monitor for runners in 2000, there were no wireless protocols for communicating sensor data to watch receivers nor were they capable of running on a watch battery. So, to get their first products to the market it was necessary to develop this new protocol.</p><p>It is now the underlying protocol of evolved ANT+, a communication interface standard for ultra-low power devices.</p><p>ANT+ ecosystem has a concept of device profiles to standardize sets of information that can be shared between different devices supporting the same profile. Each profile has some minimum certification requirements to ensure compliance between different manufacturers’ implementations. Data packet payloads, master and slave channel setup and other specifics are described in those documents.</p><p>Each profile also has standardized Activity Icons, to visually help customers understand what the device supports.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/920/1*3BucGozGkCXWnznNWr9VIQ.jpeg" /><figcaption>Some of ANT+ activity icons</figcaption></figure><h3>Test set up</h3><p>Initially, we wanted to set up the bare bones simple app to receive data from wireless shifting groupset and display it. During the preparations, we found out that the actual number of mobile phones that have ANT+ chipset on Android phones is quite small and growing obsolete, but even more concerning was that there is absolutely no support on the iOS side. At that point, from the mobile apps development team’s perspective, it was clear that we will not integrate with ANT+. Nonetheless, some knowledge of the tools and protocol is nice to have for other applications inside the company, so we proceeded with test setup to see how we might utilize it in QA and troubleshooting tasks.</p><h3>Environment, devices &amp; tooling</h3><p>To be able to confirm we can send and receive test telemetry in both ways — to and from devices, there are some prerequisites — test computer with ANT+ interface on which to create and monitor the telemetry, some devices with ANT+ enabled hardware to serve as telemetry sources or destinations, depending on the use case, and tools or scripts to prepare, send and receive data.</p><p><strong>ANT+ USB dongle</strong></p><p>Plugged in Lenovo T series laptop, this little piece of hardware contains the ANT transceiver and enables communication with other devices.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xiaa88iUAyjVtf2LFrP9Pw.jpeg" /><figcaption>ANT+ USB dongle</figcaption></figure><p><strong>SRAM ASX Force wireless groupset</strong></p><p>Modern mid to high-end groupsets from leading manufacturers always have a wireless shifting option. Usually, the internal control protocols for remote wireless shifting are proprietary, but they still expose some data over BLE and ANT+. We already had <a href="https://www.sram.com/en/sram/road/series/sram-force-etap-axs">ASX Force</a> on some of our test e-bikes, so decided to test with those.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C-gWFl-I2BeMLSKe3pLcHA.jpeg" /><figcaption>Slightly beaten up ASX Force derailleur, but still shifting perfectly</figcaption></figure><p>ANT+ available information from this system (Ant+ Shift profile):</p><ul><li>gear selection</li><li>number of shifts</li><li>battery status</li></ul><p><strong>Garmin Forerunner 45 watch</strong></p><p>Entry-level fitness tracker/smartwatch with the option to connect heart rate monitor, speed and cadence sensors over ANT+.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LjlDvl0QjG2-BOu3E0x9WA.jpeg" /><figcaption>Garmin Forerunner 45</figcaption></figure><p><strong>SimulANT+</strong></p><p>From the QA side of things, we were looking into scripting options, preferably in Python. As there were no actively maintained libraries available that suited our use cases, we chose <a href="https://www.thisisant.com/news/simulant-next-generation-ant-simulation-tool-now-available">SimulANT+</a> and the scripts that came with it. It is a GUI tool provided by Garmin, only available for Windows. It has a set of prepared scripts for the most common simulation scenarios, written in <a href="https://ironpython.net/">IronPython</a>. They can be easily adapted to suit the needs of particular testing scenarios and you can load and run them through the tool. SimulANT+ provides the option to trace ANT+ traffic between devices in raw format, as well as show the configuration and data in a human-readable format for easy interpretation and monitoring.</p><h3>Use cases</h3><p><strong>A.<em> Test how to observe the electronic shifter battery status and gear selection on the test laptop over ANT+.</em></strong></p><p>ANT+ device profiles often come in pairs. Profiles that are implemented in the devices that are the source of some data usually have <em>Sensor</em> in the name, while the devices which receive and show that data to the user use the word <em>Display</em>. In the case of wireless bike shifters, the profile that we are using in the SimulANT+ is Shifting Display.</p><p>Pre-requisites:</p><ol><li>Plug in ANT+ USB dongle in laptop.</li><li>Download and install ANT+ drivers if the device is not automatically recognized.</li><li>Download and install SimulANT+ tool.</li></ol><p>Steps:</p><ol><li>Open SimulANT+ and confirm ANT device is visible. In our case Dev0:USB2 in the screenshot below.</li><li>Load Shifting Display profile through Add Simulator.</li><li>Under Actions section click on TurnOn button.</li><li>Shift gears on the test bike and observe Current Gear — Rear values under Data Pages → Shift System Status section in Properties pane.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2ccZPfSGDdOOXedMEHlrOg.jpeg" /><figcaption>SimulANT+ interface. Shifting Display profile loaded, observing the gear changes from SRAM ASX Force system.</figcaption></figure><p><strong>B. <em>Test how to send the simulated telemetry information from the test laptop to Garmin watch over ANT+.</em></strong></p><p>With the same pre-requisites as in the previous example open the SimulANT+. This time it will serve as a source.</p><p>Steps:</p><ol><li>Open SimulANT+ and confirm ANT device is visible.</li><li>Load Heart Rate Sensor profile through Add Simulator.</li><li>Under Actions section click on TurnOn button.</li><li>On the Forerunner 45 navigate to Settings and <a href="https://www8.garmin.com/manuals/webhelp/forerunner45/EN-US/GUID-87B163D1-9CDD-4705-9E6F-0B4324C54950.html">pair</a> this simulated Heart Rate Sensor.</li><li>Under Script section, select hr_SensorSweep.py and click on Run. This script is sweeping from 45 to 200 and back. The values and intervals can be adjusted in the code. You can monitor the values in the Properties section, Configuration → Heart Rate (bpm).</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WI3nwGBO1xjjb_C4hpwFRQ.png" /><figcaption>Snippet from hr_SensorSweep.py script</figcaption></figure><p>6. Start the Activity on the watch and observe the simulated heart rate is showing properly.</p><h3>Conclusion</h3><p>Despite some pretty interesting choices from Garmin’s side (IronPython and Windows-only tools) we managed to mock / simulate different ANT+ devices quickly and without problems in both ways. Prospect of using ANT+ to expand the connectivity of our applications seemed like a good idea, but the lack of support in that domain was somewhat surprising.</p><p>As it currently stands, Garmin is no longer isolated as a top player in the segment and with the rise in popularity of BLE (pushed mostly by the mobile devices vendors) it seems that the future for ANT+ and direct communication with mobile phones is sealed. Available libraries for mobile development are almost non-existent, and the list of Android mobile phones with ANT-compatible chipsets is looking more and more obsolete. Most of the devices on that list are from Samsung, but even there we don’t see ANT+ hardware support in the devices coming to the market in the past 2 years. Apple never had any intention to natively support it. So if you are a developer or tester in the Android / iOS world, the chances are you will never see this protocol in your life. But if you are working on embedded systems in the fitness-related industry, you most likely will, so we hope you found some useful information here, to get you started.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=74bf1dc83d50" width="1" height="1" alt=""><hr><p><a href="https://medium.com/greypbikes/ant-in-mobile-software-qa-landscape-74bf1dc83d50">ANT+ in mobile software QA landscape</a> was originally published in <a href="https://medium.com/greypbikes">greypbikes</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We won at our first Fightbotics!]]></title>
            <link>https://medium.com/greypbikes/we-won-at-our-first-fightbotics-5be4bd4e81af?source=rss----f2d1bb7a0d0e---4</link>
            <guid isPermaLink="false">https://medium.com/p/5be4bd4e81af</guid>
            <dc:creator><![CDATA[Greyp Bikes]]></dc:creator>
            <pubDate>Thu, 24 Nov 2022 13:46:30 GMT</pubDate>
            <atom:updated>2022-11-25T07:33:45.900Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sWYs7K8FG4A3e4raJLiUgA.png" /><figcaption>Goran Krajnović &amp; Dinko Morović with their Penetrator6000</figcaption></figure><p>We sat down with <a href="https://www.linkedin.com/in/ACoAAAVNeP8BQp82ywcVAvKkX_FxxSiJhHSFOt0">Goran Krajnovic</a> a.k.a. Zed, our Prototype and Testing Lead Technician, and <a href="https://www.linkedin.com/in/ACoAADATF3IBkpiIxFThUpzYe8NwcsrgRk4-9xw">Dinko Morovic</a> a.k.a. Dinkec, our Mechanical Engineer and talked about something completely different and yet, so Greypy: ROBOTS!</p><p>Today Zed and Dinkec WON at the FightBotics event organized by the Faculty of Mechanical Engineering and Naval Architecture at @SKUC PAUK / Student Home Stjepan Radić!</p><p>Here’s what our world conquerors had to say.</p><p><strong>Describe yourself in a hashtag.</strong></p><p>ZED: <a href="https://www.linkedin.com/feed/hashtag/impossible">#impossible</a></p><p>DINKO: — decided he was too cool to be a hashtag –</p><p><strong>What is going on with this robot? What can it do? What can it not do?</strong></p><p>ZED: It cannot make coffee. It will be fixed in V2_final_final_majkemifinal.</p><p>DINKO: It can put a smile on people’s faces.</p><p><strong>Can you use the robot for work?</strong></p><p>ZED: It can bring you a cup of coffee or two. And if you’re not scared, you can use it for work, sure.</p><p>DINKO: Yes, we can! I can also use it to hide Zed’s favorite tools.</p><p><strong>And now, some work questions: so, are all of you bikers?</strong></p><p>ZED: Not as active as before, but I still like the name.</p><p>DINKO: was a biker.</p><p><strong>Other than building killer robots, what are some other things you are into that are not work-related?</strong></p><p>ZED: Tough question! Lots of stuff, mainly FPV drones/sim racing/RC drifting/other similar shenanigans.</p><p>DINKO: nothing as cool.</p><p><strong>How did you end up at Greyp? And why did you choose to apply?</strong></p><p>ZED: When I applied, Greyp almost didn’t exist (it was part of Rimac Automobili). I just wanted to do what I love and ended up here. 2 wheels &gt; 4.</p><p>DINKO: Nobody else wanted me.</p><p>(authors note: we believed in you all the way Dinko!)</p><p><strong>What are your teammates like? What is it like to work with them?</strong></p><p>ZED: Look at the first question hashtag! Just kidding, they are incredible!</p><p>DINKO: We make killer robots.</p><p><strong>Do you work with other teams/ departments?</strong></p><p>ZED: Of course, with every single one. That’s my job!</p><p>DINKO: When they make me to.</p><p><strong>What is the biggest challenge you’ve had so far working at Greyp?</strong></p><p>ZED: Not punching Dinko in the face when he broke in my 3D printing room. 😊</p><p>DINKO: Not working on a robot.</p><p><strong>What are three things you can’t work without?</strong></p><p>ZED: Greyp team, open mind and smiles. Lots of smiles…even if it means punching your colleague in the nuts.</p><p>DINKO: Mouse, keyboard, šubler*.</p><ul><li>for those who don’t know, a šubler is a caliper</li></ul><p><strong>Name another department that seems like it would be fun to work in and tell me why?</strong></p><p>ZED: Umm…no? Prototyping is the best. 😊</p><p>DINKO: Proto workshop so I can print something.</p><p><strong>What’s your worst bug?</strong></p><p>ZED: I get extremely lazy when I get a pointless task. Good thing is that I give it all when something makes sense.</p><p>DINKO: administration.</p><p><strong>Were there any moments when you’re working that make you think “wow, I love my job/field so much!”</strong></p><p>ZED: When I got a bunch of old equipment to destroy for testing purposes 😊</p><p>DINKO: when we blow out stuff.</p><p><strong>What is the best advice someone has given you?</strong></p><p>ZED: “Please put on your safety goggles.”</p><p>DINKO: Never go full retard.</p><p><strong>So, your Penetrator6000 won today, at Fightbotics?</strong></p><p>ZED: Looks like it, but here, see for yourself. ;)</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F1EJu8Zxnzg4%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D1EJu8Zxnzg4&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F1EJu8Zxnzg4%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/bb63cf9248359f594c577f6fe127c1f4/href">https://medium.com/media/bb63cf9248359f594c577f6fe127c1f4/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5be4bd4e81af" width="1" height="1" alt=""><hr><p><a href="https://medium.com/greypbikes/we-won-at-our-first-fightbotics-5be4bd4e81af">We won at our first Fightbotics!</a> was originally published in <a href="https://medium.com/greypbikes">greypbikes</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[IoT in e-bikes]]></title>
            <link>https://medium.com/greypbikes/iot-in-e-bikes-6a30fd21923f?source=rss----f2d1bb7a0d0e---4</link>
            <guid isPermaLink="false">https://medium.com/p/6a30fd21923f</guid>
            <category><![CDATA[greyp-tech]]></category>
            <dc:creator><![CDATA[Ivan Antolković ]]></dc:creator>
            <pubDate>Thu, 24 Nov 2022 12:11:08 GMT</pubDate>
            <atom:updated>2022-12-04T19:52:20.368Z</atom:updated>
            <content:encoded><![CDATA[<p>The general impression of Greyp as a company is that it’s a bike company producing e-bikes. But, if you scratch under the surface, there is much more to it. Nearly half of employees work in Research &amp; Development developing electrical and software components. One of R&amp;D’s departments is the Software Department and their main focus is on developing IoT platforms and Mobile Apps. The team consists of 10+ software experts working on features that enhance the riding experience for the user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*ZovfnBgmokH25ROkDmLKxA.png" /></figure><p>The brain of Greyp bikes is the Central Intelligence Module (CIM), an electrical component with a small display, embedded SIM card, various sensors, and two connected cameras — front and rear. The CIM presents basic riding info to the user, on display, but also collects and sends a lot of riding data to the IoT platform which saves and processes received data, and prepares it for usage on end applications.</p><p>Mobile apps — iOS and Android, show collected data to the user in a form of features. The app has two main modes of work, dashboard, and remote. In remote mode, the communication between the mobile app and the bike goes through an IoT platform. The app shows basic bike info like location, speed, range, and state of charge. Also, in remote mode, users can change bike settings, play with videos from their ride or lock the bike. In dashboard mode, the communication between the mobile app and the bike goes directly, through Wi-Fi connection. The app shows real-time telemetry data and video streams from the bike and enables turn-by-turn navigation.</p><p>All the things mentioned above, the bike (CIM), the IoT platform, and the mobile apps, make the complex IoT system that provides a lot of possibilities for developing cool and innovative features for end customers. In this process, we face many challenges and this is where the real innovation happens.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2KtRpffkuCq_E131YjMQzw.jpeg" /></figure><h3>Software Team</h3><p>The team responsible for developing Greyp system consists of multiple sub-teams — Backend, Mobile (Android/iOS) and QA.</p><h3>Backend Team</h3><p>The Backend Team is responsible for the development of the Greyp IoT platform. The platform acts as a central place for all the vehicles and users to interact with each other.</p><p>The platform has three main responsibilities:</p><ul><li>to provide safe remote communication between the vehicle and the mobile app user,</li><li>to collect/process/aggregate vehicle and user data in order to provide a better experience for the users and</li><li>to collect and provide better business insights to the Greyp company and its OEM partners.</li></ul><p>In order to carry out these responsibilities, we are using a bunch of technologies, like Java / Spring Boot / Hibernate for our backend app, AWS, which hosts our infrastructure, Firebase for real-time communication with mobile apps, MQTT and Protobuf for vehicle communication and many others.</p><p>The high-level schema of the platform architecture is presented below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vyVMqU37BvqMHswlgRfbxw.png" /></figure><h3>Mobile Team</h3><p>The Mobile App (Android/iOS) shows data from the bike to the user and enables him to control and interact with the bike. It communicates with the IoT platform and/or with the bike directly.</p><p>The communication between the mobile app and the IoT platform goes through Firebase database and through REST. Firebase real-time database is used only for reading real-time data. The IoT platform saves the data received from bikes to the real-time database and Mobile App just reads it from there. REST is used for all the other communication, like sending commands from the app to the bike.</p><p>The other way of communication between the Mobile App and the bike is through Wi-Fi. In this case, the Mobile App connects to bike’s Wi-Fi, establishes TCP connection, and exchanges messages, data and commands. Raw data is exchanged using “protobuf” and our internal protocol.</p><h4>Android Team</h4><p>The Android App is developed natively using Android Studio as a development IDE and Kotlin as a programming language. The whole project is divided into several modules that could be grouped in two layers: A presentation layer and a “greyp-api” — which is the core of the system.</p><p>The presentation layer is implemented using the MVVM architectural pattern and consists of views and view models. This ‘core’ module consists of three sublayers: service, use cases, and repository layer. The service layer is the only connection with the ‘outside world’ for communication with the presentation layer. Furthermore, we added use cases where core logic is located. And finally, a repository layer for communication with our data sources. For exchanging data between layers in the architecture, we use RxJava except within UI component → ViewModel, where we use LiveData from Android Jetpack libraries.</p><p>A scheme of the architecture is presented below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/792/1*IL0rC3LYi--qzdma3aEe1A.png" /></figure><p>We are using the Fastlane tool for automatising the publishing of apps to the Firebase app distribution and informing The QA about new app versions, and Google Play Store to distribute the app to our users.</p><h4>iOS Team</h4><p>iOS App is developed natively in Swift. Project architecture is similar to the Android app, with multiple modules, presentation and business layer, and MVVM architectural pattern. For exchanging data between layers in the architecture, we use RxSwift.</p><p>In the presentation layer, we have an additional component, the navigator, whose purpose is to encapsulate the logic of creating and presenting views. In the business layer, we also have an additional component — subscriptions. Its purpose is to run all the tasks that need to be active during the whole application session. The schema of the architecture is presented below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/738/1*kJKbpVDy1LRikTMGmzBigw.png" /></figure><p>As dependency manager, we use Swift package manager. Also, we use multiple external frameworks such as: RxSwift, RxCocoa, SnapKit, Mapbox, Firebase (Messaging, Database, GoogleSignIn, … )</p><h3>QA</h3><p>The QA team is responsible for testing the system and ensuring that everything works according to functional and non-functional requirements. The development process that we employ most closely resembles BDD (behavior-driven development), so the focus is on functional validation of acceptance criteria through documented tests. XRAY is the tool of choice for test management. As there are several interfaces between apps, bikes, and backend, the test automation approaches differ somewhat from what is the norm in the industry. A large part of the testing is focused on direct communication for which the team has to work directly with hardware and Linux-based software, employing MQTT and CAN protocol along with the previously mentioned internal GCP. Backend APIs are tested through Postman with the help of HTTPS proxy for troubleshooting and analysis. UI-driven tests are done with Appium on both iOS and Android. A good number of bugs on all layers are also prevented through exploratory testing sessions that the team is religiously employing for each new feature and on every release.</p><h3>Next steps</h3><p>During the last 5+ years of development of Greyp IoT platform, we faced a lot of challenges and technical problems we needed to overcome to get the system we currently have. Also, we are constantly working on new features and experimenting with new technologies. With that in mind, we would like to share some of the solutions with the community. This is the first of many articles that we will be sharing with the community, so stay tuned. New articles coming soon!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6a30fd21923f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/greypbikes/iot-in-e-bikes-6a30fd21923f">IoT in e-bikes</a> was originally published in <a href="https://medium.com/greypbikes">greypbikes</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[XML -> Jetpack Compose — should we migrate?]]></title>
            <link>https://medium.com/greypbikes/xml-jetpack-compose-should-we-migrate-99ba8c4a60f5?source=rss----f2d1bb7a0d0e---4</link>
            <guid isPermaLink="false">https://medium.com/p/99ba8c4a60f5</guid>
            <category><![CDATA[android]]></category>
            <category><![CDATA[kotlin]]></category>
            <category><![CDATA[greyp-tech]]></category>
            <category><![CDATA[android-app-development]]></category>
            <dc:creator><![CDATA[Alen]]></dc:creator>
            <pubDate>Thu, 24 Nov 2022 12:04:14 GMT</pubDate>
            <atom:updated>2022-12-05T08:30:26.291Z</atom:updated>
            <content:encoded><![CDATA[<h3>XML -&gt; Jetpack Compose — should we migrate?</h3><p>Since the dawn of time, Android apps have used XML notation to describe UI. In May 2019, Google announced Jetpack Compose, the first stable version (1.0) was released in July 2021 and the current stable version is 1.2. The first stable version (1.0) was released in July 2021 and the current stable version is 1.2.</p><p>Jetpack Compose is a relatively new way of building native UI on the Android platform. The idea is to simplify and accelerate development by describing UI rather than writing separate .xml layouts for each screen, or even multiple .xml files if you have to have a fragment with a recycler view. From Google documentation: “Compose is Android’s modern toolkit for building native UI.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ocyf19OK13JPnqHUJLS8zg.jpeg" /></figure><p>From this year, Compose 1.0 for wearables is out. You can read more about <a href="https://android-developers.googleblog.com/2022/07/compose-for-wear-os-10-stable.html">here</a></p><p>Some quotes from companies using Compose for some time now:</p><blockquote>Compose <strong>increased our productivity</strong> dramatically. It’s much <strong>easier and faster</strong> to write a Composable function than to create a custom view, and it’s also made it much easier to fulfill our designers’ requirements.<em> [Twitter]</em></blockquote><blockquote>There’s also a significant reduction for any screen built with a RecyclerView, which the majority of our screens are.<em> [Monzo]</em></blockquote><p>What prompted us to try Compose is that our application uses a lot of custom views and we don’t use predefined components for the UI from the material components library so we wanted to check if Compose could really fasten our development effort for building UI, reduce boilerplate code etc.</p><h3>Comparison and examples</h3><p>Compared to XML, Compose is Declarative UI which means that the state of the screen is pre-defined and the UI elements will reload upon any change made to this state. A really simple example is hiding the view. With the current UI toolkit, you would typically use a method like findViewById() to get a reference to the View you want to hide, then call setVisibility() on it. Instead, in a declarative UI, you describe the UI as being visible or not. When you want to change the visibility, you re-run the code describing the UI.</p><p>Our idea was to try Compose in a ‘Proof Of Concept’ project and then possibly decide whether we should start building UI for the new app with Compose or we should stick with XML. We have spent a few sprints ‘playing’ with Compose and will try to give examples of why we believe Compose is better alternative to the standard XML.</p><p>If we want to implement profile section as is shown in the picture below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/451/1*V6e5FjUeZt5RfpYzm5PsKw.png" /></figure><p>We could just write a @Composable function and within few lines of code describe UI to achieve design like in the picture above:</p><pre>Column(<br>    modifier = modifier<br>        .verticalScroll(rememberScrollState())<br>        .fillMaxSize()<br>        .padding(8.dp, 16.dp, 8.dp, 16.dp),<br>    horizontalAlignment = Alignment.CenterHorizontally<br>) {<br>    SettingsCard(<br>        title = &quot;Account&quot;,<br>        subtitle = &quot;Antonio&quot;,<br>        items = listOf(<br>            Item(<br>                title = &quot;Change email&quot;,<br>                endItem = EndItem.Icon(R.drawable.ic_arrow_right),<br>                action = {}<br>            ),<br>            Item(<br>                title = &quot;Change password&quot;,<br>                endItem = EndItem.Icon(R.drawable.ic_arrow_right),<br>                action = onClickChangePassword<br>            ),<br>            Item(<br>                title = &quot;Subscription Membership&quot;,<br>                subtitle = &quot;Monthly&quot;,<br>                endItem = EndItem.Icon(R.drawable.ic_arrow_right),<br>                action = {}<br>            )<br>        )<br>    )<br>  }</pre><p>One of the biggest improvements to reducing boilerplate code is when it comes the need to use RecyclerView. Instantiating RecyclerView in XML had a lot of boilerplate code. We needed to have a layout for the item, the ViewHolder and the Adapter and the configuration in the Activity/Fragment. The old way of doing this is:</p><ul><li>Declare your RecyclerView in XML.</li><li>Create your custom views which will be shown in your RecyclerView cell.</li><li>Create an adapter, add OnCreate, OnBind, and other methods to display your cell.</li><li>Finally, bind your RecyclerView with an adapter in your .kt/java file.</li></ul><p>With Jetpack Compose, the need for the boilerplate code is no longer required.</p><pre>@Composable<br> fun SampleContent() {<br>     val data = remember { DataProvider.dummyList }<br>     LazyColumn(<br>         contentPadding = PaddingValues(horizontal = 16.dp, vertical = 8.dp)<br>     ) {<br>         items(<br>             items = data,<br>             itemContent = {<br>                 SampleListItem(it)<br>             })<br>     }<br> }</pre><ul><li>LazyColumn composable is a replacement for RecyclerView and with LazyColumn params we can define padding.</li><li>items() function of LazyColumn Composable takes our data list as first param, and a composable itemContent that takes our list item composable to populate with each item in the list. We just need to create SampleListItem Composable function:</li></ul><pre>@Composable<br> fun SampleListItem(data: SampleData) {<br>     Row {<br>         Column {<br>             Text(text = data.title, style = typography.h6)<br>             Text(text = &quot;VIEW DETAIL&quot;, style = typography.caption)<br>         }<br>     }<br> }</pre><h3>Interoperability</h3><p>It is easily possible to start working with Compose even if the whole project is written in XML. <a href="https://developer.android.com/jetpack/compose/interop/adding">Adding Jetpack Compose to your app | Android Developers</a></p><p>To create a new, entirely Compose-based screen in your activity/fragment call the setContent() method in onCreate() / onCreateView() method, and pass whatever composable functions you like.</p><p>Also, you can add XML views in Composable methods. Add AndroidView() to your composable method and define factory and update parameters. Those define how the XML view behaves.</p><p>More on: <a href="https://developer.android.com/jetpack/compose/interop/interop-apis">Interoperability APIs | Jetpack Compose | Android Developers</a></p><p>Even if you don’t want to start with Compose from the ground up, it is even possible to try to compose on screens that are already written in XML. All we need to do is to insert androidx.compose.ui.platform.ComposeView in the XML layout. Add id to that view and after that find it in your activity/fragment and apply setContent() method.</p><h3>Conclusion</h3><p>Two notes to summarise this story:</p><ul><li><strong>Single source of truth ℹ️ </strong>In Jetpack compose, you can pass the state to your composable functions, and it will observe and update itself accordingly. You don’t need to make any changes to the UI.</li><li><strong>Kotlin friendly 😃 </strong>Jetpack Compose uses Kotlin. So with the help of it, you can easily create your own UI. You can simply decide what to display using if/else or display a list of filtered users using advanced functions of collections. Also, it becomes easier to learn and understand the process.</li></ul><p>Personally, we don’t think XML will be deprecated, but since Google introduced UI toolkit to run just in Kotlin, most likely, within a few years, Compose will be the preferred way of dealing with the UI. Furthermore, Google’s public roadmap for developing Compose is quite positive. In focus for the next release is performance, tooling improvement (such as preview and live edit), etc. Find more information here: <a href="https://developer.android.com/jetpack/androidx/compose-roadmap">Jetpack Compose Roadmap | Android Developers</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=99ba8c4a60f5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/greypbikes/xml-jetpack-compose-should-we-migrate-99ba8c4a60f5">XML -&gt; Jetpack Compose — should we migrate?</a> was originally published in <a href="https://medium.com/greypbikes">greypbikes</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[No Going Backwards]]></title>
            <link>https://medium.com/greypbikes/no-going-backwards-b762f7efae98?source=rss----f2d1bb7a0d0e---4</link>
            <guid isPermaLink="false">https://medium.com/p/b762f7efae98</guid>
            <category><![CDATA[greyp-life]]></category>
            <category><![CDATA[greypers]]></category>
            <dc:creator><![CDATA[Vlado Karmelic]]></dc:creator>
            <pubDate>Tue, 22 Nov 2022 09:23:00 GMT</pubDate>
            <atom:updated>2022-12-06T09:19:57.850Z</atom:updated>
            <content:encoded><![CDATA[<p>We are Greyp — a tech brand that designs, engineers, and produces high-end electric bicycles with amazing technology and performance. From our humble beginnings in 2013 up until now, we have grown exponentially.</p><p>Today we are a (wild) bunch of bikers, gadget geeks, and outdoorsy types, and we incorporate all those passions into each product we create. We aim to imagine, construct, develop, and deliver the finest riding experience. While we recreate the future of biking, our goal is to have as much fun as we can along the way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xwBDXjQgINB9_Wr-CtiVOQ.jpeg" /><figcaption>GREYP BIKES</figcaption></figure><p>On one hand, we are focused on the design and production of <em>premium</em> <em>smart</em> and <em>connected</em> e-bikes, and on the other: we’re developing complete e-bike systems that are always connected to the Internet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*Sv4x4IdcMJAbDRyAXeVEMg.jpeg" /><figcaption>Greyp iOS Workshop</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*C7dBaNrkQstsXsk1wHlz_Q.jpeg" /><figcaption>Working on the new e-SUV bike</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MmtTsHqrYSMIlUQl5F8vnQ.jpeg" /><figcaption>Greyp Warehouse during a Townhall Meeting</figcaption></figure><p>For more spicy info about us take a ride through the Greyp hallways and check out what you see when you look „under the hood“ of a Greyp bike?</p><p>The cutting-edge tech…or the first-class engineering? <br>The time put into R&amp;D…or the endless hours spent on details?</p><p>We see… the future of bike riding. <br>And once you see the future — there’s <strong><em>No Going Backwards.</em></strong></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FrQv5O6InPfo%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DrQv5O6InPfo&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FrQv5O6InPfo%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/3d168a317571ad7af16576351da7ed65/href">https://medium.com/media/3d168a317571ad7af16576351da7ed65/href</a></iframe><p>Discover more about what we’re up to, get to know the humans of Greyp, and take a look at Greyp’s open positions: <a href="https://www.youtube.com/redirect?event=video_description&amp;redir_token=QUFFLUhqbnVpVFppZkJ6WGIzU2NzUG51M25ONG0welhPQXxBQ3Jtc0ttbVhhcjR3X1h2MnlWUjEtSGxJMVVzX3ZseExobDV3VG9QbGRkQ3NBOERSb2lwNVRJN2hpaTBOUXY5Nkxsa2g2Rmd0dGpvV3VEdHFWVmlycXFhQnZOR2lVRzhDbGIzOXhNTVp2T2IwbXQ4WlFUR2hvbw&amp;q=https%3A%2F%2Fgreyp.me%2Fabout-greyp&amp;v=rQv5O6InPfo">https://greyp.me/about-greyp</a></p><p>Feel free to connect with Greyp through social media:</p><ul><li><a href="https://www.facebook.com/GreypBikes">https://www.facebook.com/GreypBikes</a></li><li><a href="https://www.linkedin.com/company/greyp-bikes/">https://www.linkedin.com/company/greyp-bikes/</a></li><li><a href="https://www.instagram.com/greyp_bikes/">https://www.instagram.com/greyp_bikes/</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b762f7efae98" width="1" height="1" alt=""><hr><p><a href="https://medium.com/greypbikes/no-going-backwards-b762f7efae98">No Going Backwards</a> was originally published in <a href="https://medium.com/greypbikes">greypbikes</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bikes, Beers & Bits]]></title>
            <link>https://medium.com/greypbikes/bikes-beers-bits-21add7cbd095?source=rss----f2d1bb7a0d0e---4</link>
            <guid isPermaLink="false">https://medium.com/p/21add7cbd095</guid>
            <category><![CDATA[greypers]]></category>
            <category><![CDATA[greyp-life]]></category>
            <dc:creator><![CDATA[Greyp Bikes]]></dc:creator>
            <pubDate>Mon, 14 Nov 2022 10:27:15 GMT</pubDate>
            <atom:updated>2022-11-21T08:30:02.018Z</atom:updated>
            <content:encoded><![CDATA[<h4>Engineering, connectivity, and smart e-bikes!</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6S-0vMrvH7_qdH0BW46FRw.jpeg" /><figcaption>Greyp Bikes Team</figcaption></figure><p>Alongside our regular “biking” activities and events, we like to throw some local meetups of our own, we call them “Bikes, Beers &amp; Bits” and they serve as an excellent opportunity for attendees to hear more about what we do and how we do it, but also a chance to meet &amp; greet, and enjoy many mutual passions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r9TZ1wOZ1ucnKsKJKOEbJg.jpeg" /><figcaption>Greyp Bikes Team</figcaption></figure><p>So, if you’ve ever wondered what software has to do with bikes, this is where you’ll get your answers. We try to cover a wide range of topics from development and design to project management.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Pgi1MyYfBuLj1zN1qexiag.jpeg" /><figcaption>Bikes, Beers &amp; Bits session @Maksimir</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MlRwGyBhYZY0ZQS7tgGOOw.jpeg" /><figcaption>Bikes, Beers &amp; Bits session @SwankyMonkeyGarden</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HyKNJfiESVH6mXpqSHHV8w.jpeg" /><figcaption>Bikes, Beers &amp; Bits session @BikersBeerFactory</figcaption></figure><p>With every new meetup, we will delve deeper into engineering topics, mobile development, cloud connectivity, IoT devices, and much more.</p><p>As our final product is an actual bike, we will also include the entire team responsible for its uniqueness, ranging from Embedded Software to Backend Developers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rVhS1uorhoCfPwHauSCmWQ.jpeg" /><figcaption>Bikes, Beers &amp; Bits session @Maksimir</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-Og_Vx3dc_Jfx75mkxb5jA.jpeg" /><figcaption>Greyp Bikes Team</figcaption></figure><p>Join us at the next BBB meetup, grab a cold one and find out what makes us ping. Meet you there!</p><p>In the meantime, check out former events:</p><p>Sess 1: Swanky Monkey: <a href="https://myalbum.com/album/wS4mcigPRNtehk/">https://myalbum.com/album/wS4mcigPRNtehk/</a></p><p>Sess 2: Maksimir: <a href="https://myalbum.com/album/9BKwNazszzRj8G/">https://myalbum.com/album/9BKwNazszzRj8G/</a></p><p>Sess 3: Bikers Beer Factory: <a href="https://myalbum.com/album/kP7fiWA8HocfaB/">https://myalbum.com/album/kP7fiWA8HocfaB/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=21add7cbd095" width="1" height="1" alt=""><hr><p><a href="https://medium.com/greypbikes/bikes-beers-bits-21add7cbd095">Bikes, Beers &amp; Bits</a> was originally published in <a href="https://medium.com/greypbikes">greypbikes</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>