Get started with App.net.

  Sign up now  
scruffyfox
    I've pushed a commit that updates Robin for the latest gradle/android studio version. Just import (settings.gradle) and hit run.
    scruffyfox
      @sevan they might do what amazon do and sign with their own cert though
      scruffyfox
        @sevan it stops people from creating malware and passing it off as another app as an 'update'
        scruffyfox
          @sevan you need to sign an apk to install on Android, and you need to sign with the same certificate to do updates, thats not a google play limitation, thats an android limitation
          scruffyfox
            @sevan apks on github. its not officially maintained anymore, so there will be no signed APKs from me, but theres nothing stopping you from forking and submitting (as long as you abide by the license ;)
            scruffyfox
              @cn try uncommenting the && taskName.contains("release"). Then it should only prompt when you call ./gradle assembleRelease via console to make a production apk
              scruffyfox
                @cn only when you call assembleRelease. you have to provide a keystore path, password and key name, password. Obviously all have been removed
                scruffyfox
                  @echodunk best use v1 codebase then
                  scruffyfox
                    Also check out the image gallery [imgur.com] of the different versions of Robin through out the development!
                    scruffyfox
                      I have updated the repository to include APK builds of both versions of the apps. Version 1 [github.com] and Unreleased version 2 [github.com]. Version 2 is an alpha, but has some cool features. Both can be installed at the same time.
                      scruffyfox
                        If anyone does fork robin, please please please use the v2 codebase. It's SO much nicer than the v1 codebase. Probably the nicest code i've ever written
                        scruffyfox
                          @schmidt_fu @duerig the app then gets woken up via receiver and displays a notification
                          scruffyfox
                            @schmidt_fu @duerig when a new object comes in, it looks up that user in the database and sends out a payload to GCM which then delivers it to the app
                            scruffyfox
                              @schmidt_fu @duerig the apps hit the notification API to store its push token, user id and settings (also access token for muted), the notification worker runs standalone as a service which connects to the streaming API from adn and the database
                              scruffyfox
                                @akulbe I always wanted to, but not at that time as I was unsure if I was going to continue working on it or not, and dont worry, i was already thinking about it before you asked
                                scruffyfox
                                  @duerig Sorry, not willing to give out the database with 3k+ user device push tokens :/
                                  scruffyfox
                                    @akulbe I literally thought about doing it this week, but my laptop was left at work :)