I think Dr. Blaze specifically excluded the app store listing. He left that up to the community because it requires doxing. So not sure how this process could be any better.
I’m just here doing small parts to achieve the goal as time permits. We have a track record of delivering.
In my opinion, the taproot bridge is a far more interesting project to focus a high degree of scrutiny. They could be working on something that is expecting many AZs and from what I can tell they are looking to expand the functions of Sentinels and it’s not clear if they are willing to submit a ZIP.
Sure taproot deserves scrutiny but that is a separate topic. Everything deserves scrutiny.
You ever present a technical topic to a non-technical board? It is not the boards job to understand the tech and it is not their job to do mental gymnastics to determine if there is a real plan in place. It is their job to review the information presented and make decisions that uphold their fiduciary responsibilities.
Like it or not, the more we start thinking like this the more efficient AZ will become. I also think this mindset will be required to boost pillar participation especially for things like supermajority votes. Better to start building the muscle now.
Yes I totally understand that, I have been eagerly waiting for it too. Looking through some of the forums, it looks like I came in during a little bit of a turbulent time as well with AZ submissions, but I had no idea. I am just looking to provide value and push things forward.
I have several things I want to build, but being able to use Syrius on mobile with a QR scanner is necessary. I’ve been checking in on the mobile project every few months and started asking why it hasn’t launched to other members. That led to this AZ. I plan to have a call later today with @0x3639 and get the mobile app for IOS ready for TestFlight within the org account. From there, technically anyone that wants to dox their email should be able to download it to their IOS device.
In my experience, the first Apple approval (the actual release) always takes the longest, taking a couple of weeks usually for Apple to review. Further deployment/approvals usually take 1-2 days for the review process. Android is much simpler, the initial release can usually be pushed within 24 hours to the Google Play Store.
The approval process for Apple usually goes much quicker if we have an official website with support links, terms and conditions, and privacy policy to support the app.
@tortcher and I had a phone call to discuss expanding his scope to include leading the charge on getting the mobile wallet submitted and listed in the App & Android stores. In addition, he will help setup windows signing so the desktop binary does not issue security warnings. We are able to sign macOS binaries today.
I will need to stay involved so we can insert the appropriate secrets into github to automatically sign and publish the apps, but Torcher will take the lead.
He will include @jovi and @aliencoder in this expanded scope to cover their work to date in these areas.
@tortcher Sultan would like to see a roadmap and schedule to deliver this work with the AZ. Let’s also get buy in from @jovi and @aliencoder before you submit it.
After my conversation today with @0x3639, I put together a Roadmap for an official launch date for the Syrius Mobile app (with this AZ included as well). I am posting it here to get feedback and then I will create an AZ for the additional deployment work left off by Blaze.
Official Launch Date: April 1, 2025
While I would love to get it out sooner (obviously) there is a fair bit of coordination between myself, DeezNutz, Jori, and just working through the configuration and launch. I also want to be realistic and I truly believe we can hit this deadline 100%.
Here is a Gannt breakdown of how I propose getting the work completed in this timeframe:
I dont see anything from @john.maxwell or @CryptoFish in there. So we can assume there is not a dependency here and all that work is refactoring and no bug fixes i.e., the apps work fine now?
I told torcher to exclude the work being done to Syrius (the desktop app), It’s part of a separate AZ - not coordinate here. When syrius (desktop) is merged into main the goal is to sign the binaries.
John and CF are working together on their own schedule
To @sultanofstaking point though of any bugs within the app, I submitted an in-depth review of the app and tested all features (sending/receiving/delegating/staking/AccZ). Everything was functional except the QR code scanning with the camera active. I submitted that into the Syrius SIG channel. If no one picks that work up in February, I will cover that work as well - they are honestly minor edits. They shouldn’t take longer than a days work and I can do that in parallel on the feedback week for the website design review.
Thanks - So does this change scoping / sequencing of your payout phases? Are those last 3 steps in this AZ or @0x3639 will that be included in the AZ you mentioned earlier?
I’ll include the bug fixes into the new AZ which will include some funds for 0x (Prepping app store, managing work, etc), my work (IOS/Android deployments and bug fixes to the Mobile app), Jori’s work on the assets (and any modifications necessary), and Aliens work on verifying/approving the deployment code since he has done that for most of the other repos.
I’ll add the bug fixes into the Gannt chart prior to submitting it in the AZ. Excited to kick these projects off and get this thing over the finish line. It’s been a long time coming.
agree. What ever I need to do to get the app listed on the app / android stores are included here. Also include reimbursement for my LLC and apple developer account.
I will be asking for a fraction of the time I’ve spent - and it will be included in Torcher’s new AZ to coordinate this work.
@jovi how much you like to request for your work to date? Logos, forum logos, app store headers?
@aliencoder how about the work you have done with GhA to sign the macOS binary? We would like to include that in Torcher’s AZ also.
wanted to share this image from X. I think we should avoid partial payouts. We need to simply deliver. That is how most of the devs here do it. And no one has been rugged.
@tortcher are you willing to delay payment on the website AZ until all work is complete and we meet the criteria in the image above? If so, I’m going to vote yes on the AZ.
First of all, congratulations on your first proposal and welcome! It’s refreshing to read such a well written proposal again. The project is well thought out, has a reasonable budget, and a realistic schedule.
You seem to have the experience needed to develop the website. While having the website does not guarantee the approval of the iOS application, it will significantly enhance the project’s impact. It’s worth noting that the initial proposal does not include handling the iOS application process, but this has been added to the roadmap based on community feedback.
With this in mind, can we assume that this proposal includes your commitment to overcoming all hurdles until the iOS application is approved? Clarifying this would provide the community with greater confidence in the overall deliverables and project goals.
Additionally, be aware that the time frame for Phase 2 is dependent on feedback from the community. This process may take longer than expected. It would be helpful to establish clear guidelines for gathering feedback, so the community can respond efficiently and in a focused manner.
Another point to consider is whether the website will contain text. If so, who will be responsible for creating specific content, such as legal texts (e.g., Terms & Conditions, Privacy Policy) and technical documentation?
Finally, I suggest giving some thought to listing the functionalities of both the desktop and mobile applications. While web pages often showcase these through descriptions or screenshots, it’s important not to make them overly dependent on a specific version. This is particularly relevant if the application is likely to undergo significant changes in the near future.
Wishing you the best of luck with the project and looking forward to seeing the results! If you need any information or help, feel free to contact me anytime on Matrix in the Syrius SIG room.
Yes, the additional scope will handle all of the deployment and assistance with launch to IOS/Android. I am not expecting to receive any funds on either AZ until all aspects of both are fully completed so there is no risk to the community.
Bug Fixes for the app:
I did an in-depth review (linked further up in the thread) of the app on my phone and nearly everything is functional. Most of the bugs I found are simple things that were overlooked (adding decimal points to input fields, the camera view not reading a QR code). As I am sure people are aware, bug fixes are a very difficult thing to put an exact estimate on because you can fine-tune software indefinitely. My primary focus with this AZ is to make sure everything is functional and not a bad experience (things like “copy” button doesn’t work, QR code doesn’t scan etc). I did notice in the app that Push notifications are not configured and that is not something that will be included to add as it is not 100% necessary and requires quite a bit of configuration. As new features are identified, I recommend we add them to Github issues on the project and I would love to support the app on an ongoing basis, which we can all chat about when the time comes. All of my focus is on delivering a launched product that is stable and documented with the website.
Here is a breakdown of the new AZ I will be submitting for the additional scope based on community feedback:
- Tortcher: 1500ZNN, 20,000 QSR (Github Deployments IOS/Android, Critical Bug Fixes, Assistance with IOS/Android submission)
- DeezNuts 1000ZNN (Submission for app stores, managing IOS developer account, LLC setup)
- Jori: 500ZNN (logos, header, app assets)
- Alien: 500ZNN (Review Github actions for IOS/Android)
In regards to the content for the terms/conditions and privacy policy, I will be deriving them from standard language on other sites and making sure it is in alignment with how the app actually stores and manages data. You are right to point out that we will need feedback from the community on content and that could take longer than expected. My recommendation with that (and I’ll outline it when we are ready for feedback) is that any content changes just stay within the “structure” of the design (IE: not trying to add a paragraph of text to a headline). This allows me to charge forward with development and just swap text/image resources without slowing down the deliverables.
The desktop and mobile applications on the website will for the time being just link to the existing structure we have in place until work is completed on the merge. When those are ready, they should be trivial to update.
