Jump to content

Alfred Remote for Android?


Recommended Posts

Hi there,

 

Hi Evelio, 

 

As I said earlier today in my response to your email, it's unlikely that we'll create an Android app, as there are only two of us (Andrew and myself) and, at this point, focusing on OS X and iOS alone allows us to ensure we can give our users the highest quality on the most compatible platforms.

 
Cheers,
Vero
Link to comment

ok guys, took a look at it today and Alfred Remote is indeed OS X/iOS oriented, uses Bonjour for discovery and then transfers serialized data in forms like NSMutableDictionary and NSKeyedArchiver, which of course both can be supported on Android, has been a while since I tried reverse engineering a protocol and doing this for fun so please bear with me on schedule ;)

 

@Vero / @Andrew any chance you guys can provide me with some info around the data exchange, that could save me a lot of time and get this out sooner :)

Edited by eveliotc
Link to comment

Just to manage your expectations on this, Alfred Remote is still really new and the protocol is likely to evolve and change in the coming releases. I won't be encouraging or supporting reverse engineering.

 

Having said that, once Remote settles and becomes established in the future, I may provide a more published and open way to interact with Alfred which will allow for 3rd party integrations.

 

Cheers,

Andrew

Link to comment
  • 2 weeks later...
  • 1 month later...
  • 1 month later...
  • 4 weeks later...
  • 3 weeks later...
  • 3 weeks later...

Created an account to firstly say +1 and to secondly lend my support.  I'm an Android developer (currently working at Mozilla on Firefox for Android) and would love to contribute to an open source version of version of Alfred Remote for Android.

Link to comment
  • 4 weeks later...

Powerpack user here, would love the integration with Android and seem not to be alone as the more than 2000 views on this topic show.

[emphasis mine]

To be fair, views are meaningless. I have no interest in Android and still viewed the topic, as I’d bet most other workflows developers (who realised the topic exists) did as well, just to gather what the response was.

I won’t speak for Alfred’s team, but as an open-source maintainer, repeated +1ing of a topic that was already given a clear answer is useless and serves only to counter-productively drown out the important parts of the discussion. It has already been shown there is interest; continuing to +1 serves no further purpose. As Vero said, there are only two on Alfred’s team, and I’m not even sure both of them code (Vero is way more active with the community, so I’m guessing she takes care of most — often way more demanding — non-coding matters). Investing on a platform they don’t use (including learning it, and all the time that comes with doing so) likely won’t pay off.

As Andrew said, they won't be encouraging or supporting reverse engineering, and only once Remote settles and becomes established, they may provide solutions for third-party integrations. This all means: don’t count on an official Android client1, and if you want to work on a third-party solution, you’ll have to wait until steps are done that will make that possible, if ever.

Locking the topic, as it’s effectively been answered. If things change, Vero and/or Andrew can unlock it and give further news, or (more likely) make an official announcement somewhere else. Either way, we all want for continued posts to be informative, instead of a repetition what has been asked over and over.

——————————

1 It may happen, but it’s extremely unlikely and there are no plans in that direction as of now.

Link to comment
Guest
This topic is now closed to further replies.
×
×
  • Create New...