Huawei is sending developers requests to publish on its app store
Late last month, news that Google had revoked Huawei’s Android license shook the tech community. Since then, we’ve seen hardware suppliers, chip designers, standards organizations, and other companies pull out of deals with Huawei.
Huawei’s growing pains have forced the company to speed up development on its Android OS and Play Store alternative. If the company wants to survive without Google, then they need to ensure that their smartphones have access to a flourishing app ecosystem. To that end, the company is continuing to send out requests to developers of popular Play Store applications to get them to publish their apps on EMUI‘s pre-installed AppGallery app store.
A trusted developer, who wished to remain anonymous, reached out to us this morning with an email they received from Huawei. The email was an invitation to join AppGallery, an app store that the company says has “270 million monthly active users” on over “350m phones,” about half of which are sold outside of China.
The email promises that developers will be provided with “full support” to help them publish their app on AppGallery, but it’s unclear exactly what kind of support will be provided to developers. Lastly, the email mentions a free invitation to a developer community of over “560k”, though we don’t know how active this community really is.
https://www.xda-developers.com/huawei-request-developers-publish-appgallery/
#huawei #AppGallery #AppStore #developer #apps
📡@cRyPtHoN_INFOSEC_DE
📡@cRyPtHoN_INFOSEC_EN
📡@cRyPtHoN_INFOSEC_ES
Late last month, news that Google had revoked Huawei’s Android license shook the tech community. Since then, we’ve seen hardware suppliers, chip designers, standards organizations, and other companies pull out of deals with Huawei.
Huawei’s growing pains have forced the company to speed up development on its Android OS and Play Store alternative. If the company wants to survive without Google, then they need to ensure that their smartphones have access to a flourishing app ecosystem. To that end, the company is continuing to send out requests to developers of popular Play Store applications to get them to publish their apps on EMUI‘s pre-installed AppGallery app store.
A trusted developer, who wished to remain anonymous, reached out to us this morning with an email they received from Huawei. The email was an invitation to join AppGallery, an app store that the company says has “270 million monthly active users” on over “350m phones,” about half of which are sold outside of China.
The email promises that developers will be provided with “full support” to help them publish their app on AppGallery, but it’s unclear exactly what kind of support will be provided to developers. Lastly, the email mentions a free invitation to a developer community of over “560k”, though we don’t know how active this community really is.
https://www.xda-developers.com/huawei-request-developers-publish-appgallery/
#huawei #AppGallery #AppStore #developer #apps
📡@cRyPtHoN_INFOSEC_DE
📡@cRyPtHoN_INFOSEC_EN
📡@cRyPtHoN_INFOSEC_ES
microG developer will be back in 1-2 weeks
https://gist.github.com/mar-v-in/c8254168c63361c5094de13a7afea344
Hello everyone,
As many of you have noticed there had been very little involvement of me with microG over the last months.
tl;dr: I'll be back for microG work in 1-2 weeks.
I am mostly unemployed since beginning this year. There are several reasons for that and things not working out as expected, but I am not completely unhappy about that.
Another open-source project I am maintaining had it's first release. This was originally planned to happen by end of last year, but that didn't work out as expected and thus took most of my time in January.
As I need to have some income, I worked intensely for two weeks in early February as a freelancer. This worked, but turned out to be more exhausting than expected, so the fourthcoming week I wasn't actually productive.
Due to reasons™ (not to be named or speculated on) I wasn't able to work productively in most of March.
I did work on several smaller and mostly independant things. For example I contributed to the advancement of OMEMO protocol (the end-to-end-encryption protocol of XMPP), including the first implementation of the new version.
These things were collaborative efforts and often long planned in advanced, so I handled them with priority.
Another open-source project I am maintaining is preparing for it's first release. This didn't happen yet, but hopefully will happen very soon.
I do have several things done for microG that never made it into any repository:
Major changes in UnifiedNlp (planned to become a 2.0 release).
Major refactor of GMS repositories (#859)
Various fixes for applications crashing.
As there is potential for these changes to conflict with pending PRs, I didn't felt comfortable with merging them just now to reduce the overall workload.
Now I heard that several people are working on forks of microG. That's great to see. But please do create pull requests and/or document in any other way what you changed, so I can merge/catch up as soon as I have the time to do so.
I'd also like to mention again that I am very open to grant contributor rights to the main microG repository to more people. "Requirements" are you are willing to contribute more than once, review and merge pull requests and fix issues arised through the changes you introduced. Please let me know through any means if you fit in here.
Marvin
Here are some ways to support microg development economically:
https://t.me/NoGoolag/2479
📡@NoGoolag
#microg #developer #marvin
https://gist.github.com/mar-v-in/c8254168c63361c5094de13a7afea344
Hello everyone,
As many of you have noticed there had been very little involvement of me with microG over the last months.
tl;dr: I'll be back for microG work in 1-2 weeks.
I am mostly unemployed since beginning this year. There are several reasons for that and things not working out as expected, but I am not completely unhappy about that.
Another open-source project I am maintaining had it's first release. This was originally planned to happen by end of last year, but that didn't work out as expected and thus took most of my time in January.
As I need to have some income, I worked intensely for two weeks in early February as a freelancer. This worked, but turned out to be more exhausting than expected, so the fourthcoming week I wasn't actually productive.
Due to reasons™ (not to be named or speculated on) I wasn't able to work productively in most of March.
I did work on several smaller and mostly independant things. For example I contributed to the advancement of OMEMO protocol (the end-to-end-encryption protocol of XMPP), including the first implementation of the new version.
These things were collaborative efforts and often long planned in advanced, so I handled them with priority.
Another open-source project I am maintaining is preparing for it's first release. This didn't happen yet, but hopefully will happen very soon.
I do have several things done for microG that never made it into any repository:
Major changes in UnifiedNlp (planned to become a 2.0 release).
Major refactor of GMS repositories (#859)
Various fixes for applications crashing.
As there is potential for these changes to conflict with pending PRs, I didn't felt comfortable with merging them just now to reduce the overall workload.
Now I heard that several people are working on forks of microG. That's great to see. But please do create pull requests and/or document in any other way what you changed, so I can merge/catch up as soon as I have the time to do so.
I'd also like to mention again that I am very open to grant contributor rights to the main microG repository to more people. "Requirements" are you are willing to contribute more than once, review and merge pull requests and fix issues arised through the changes you introduced. Please let me know through any means if you fit in here.
Marvin
Here are some ways to support microg development economically:
https://t.me/NoGoolag/2479
📡@NoGoolag
#microg #developer #marvin
Gist
microg-away.md
GitHub Gist: instantly share code, notes, and snippets.