ecency / ecency-mobile Goto Github PK

• #4 will require comments component to display all comments, build efficient initial comment component, check steemit/busy for examples of this.
• we should paginate just like Surfer to allow UI to stay light, we don't want to fetch all 100 or 1000 comments in one go because displaying/rendering that will take time while user's mobile screen might only able to show 10 comments max
• of course comment details (votes, comments, rewards, etc.)

Ionic

Pros

• Fast development-testing cycle.
• It cross-compiles to iOS and Android.
• You can use TypeScript to develop applications for all platforms.

Cons

• There could be performance issues if you need to use a lot of callbacks to the native code.
• If your users prefer the native UI look, the same UI look in all the devices could put them off.
• Development of advanced graphics or interactive transitions will prove difficult.
• Working on Webview is slow and it guaranteed low app ratings because of performance.

Ionic is a good choice for prototyping, or projects which have fast development needs.

React

Pros

• It cross-compiles to iOS and Android.
• Learn once, write anywhere (still native)
• React Native is meant for powerfull apps where performance is essential.
• In React Native you use the Native features of the device without needing any plugin. React Native does not use a web layer over the platform, rather makes use of the device’s core features which gives your users the feeling of a native app.
• React Native is more stable and feels like a native app.
• You can use the same code-base to develop applications for Android, iOS. Better performance than Ionic, since the processing of hardware functionalities, are by the specific platform, and not Cordova.

Implement Pin code pages and structure.

Light mode: https://zpl.io/Vkn6WXK
Dark mode: https://zpl.io/VKlz6jJ

AC (acceptance criteria)

• All below points are only for light mode, theming will be separate issue. But please keep in mind theming while structuring components.
• When app first time launched on any device and user attempts to login, setting pin code will be required and first asked from user to setup.
• After login is successful and user already has set pin code, password/privateKey will be encrypted on device storage with chosen pincode
• Pin code setting should ask for Confirm pin code to be sure before saving pin code on device storage
• Reset pin code page (access it from Settings page)
• Unlock app page (when application comes from background or opens, user will be prompted to enter pin code when they try to vote/transfer/comment/post/etc. any action that requires use of privateKey/password needs pin code to decrypt password)
• Cache privateKey/password until next background/close of app, so it won't ask pin code every time to decrypt while using app

PS: Service/component should be customizable so that we can whitelist some operations that will require pin code only once after app restarts, but some operations that will require pin code every time.

Need animation or UI (sketch) design.

We have styles folder, let's put all styles with screen_name.styles.js so that style changes could be done on separate files, it would help @fildunsky to test with different variations and come up with final tweaks. I have started example here: 97e8ce9

PS. Theming should also be kept in mind when implementing screens along with multi-language support!

Fields should auto adjust or auto scroll when keyboard is open... now there is no way to enter password

The dSteem or SteemConnect functionalities will be triggered according to the user's auth type.

• Vote
• Comment
• Post
• Wallet Operations

As per mockup, add support to login with additional accounts

AC

• Adding another account support, which will add new account to local db with keys encrypted with known pin code
• Plug it into #23

In order they are presented, includes functionality and UI.

Create branch each PR description should reference this issue # and number of task from below:
Example: Issue #12-1

NPA - not priority alpha all rest is priority and we should try to include as many of them as possible.

• 1. Login (Steemconnect and traditional)
• 2. Pin code
• 3. Posts view, proper markdown parsing (check https://github.com/esteemapp/esteem-surfer)
• 4. Post view with comments
• 5. User/Author Profile view
• 6. Settings (Light/Dark theme, notifications, server selection, language selection, currency selection, pin code)
• 7. Theme changing
• 8. NPA: Multi language support, for alpha we need structure and en.json file to start translations after alpha
• 9. Currency selection
• 10: Search, integration of https://search.esteem.app very customizable (for alpha basic filters should be sufficient)
• 11: Voting
• 12: Commenting
• 13: Posting
• 14: Image uploads
• 15: Drafts (Save, List, Edit, Delete)
• 16: Follow/Unfollow
• 17: Bookmarking (Add, Remove, List)
• 18: Favorite authors (Add, Remove, List)
• 19: Scheduling (Add, Edit, Remove, List)
• 20: Push notifications + Activities (check Surfer source code, ask @talhasch )
• 21: Transfer tokens
• 22: (Un)Delegate
• 23: Power up/down
• 24: NPA: Savings operations
• 25: NPA: Escrow transfers
• 26: Simple Pointing system, backend is in process

the text is write again or enter pincod...

Wallet details steem count invalid

at pic:

• Design of the page
• Navigation setup so that logic authorized user can have access to some particular pages and authorization type (Steem or Steemconnect) can also change navigation rules.
• Authentification via Steem
• Auth via Steemconnect

• One of the most important components because users will spend most of their time composing and publishing posts/photos/videos/etc.
• Let's have one of the best editors for mobile, discuss or suggest different libraries below in the comment section of this issue.

• Voting button or component will have slider, so have efficient component to handle this so it can be plugged in into everywhere
• Slider will have percent and reward amount estimation (check Surfer)

Storage persistency is really important before we go too deep into development. eSteem v1 uses localstorage and newer devices iOS/Android cleans localstorage of apps when device is running low on memory, causing issues for user. For instance, user has to login again because their credentials are wiped out without they knowing it, etc.

From what I see, Realm is persistent and improvement over current storage solutions.
https://github.com/realm/realm-js

Let's build component or service that uses realm to handle data storage and database logic should be isolated so that if in future we decide to change it, we can do so without major refactoring.
@talhasch, @hsynterkr any feedback, questions?

alternative: https://github.com/andpor/react-native-sqlite-storage

AC

• Pin code redesign, same as recent mockups
• Plug to steemconnect login as well, note: it doesn't need to encrypt anything but just get confirmation from user via pin code only to save access_token, pincode should also popup if app is relaunched or came from background
• Ask pin code screen for operations [no whitelisted ones (transfer, account update, etc. which requires active key)]

• Fix top navigation to fetch proper lists
• Add real post details to post cards
• Post Card icons and design discuss with @fildunsky
• Post card add card extra menu on top right corner of each post card (Bookmark, Reblog, Share, etc.)
• Feed page for now can only have middle text saying Login to setup your custom Feed points to #2

This way is more secure and right way for environment variables. https://12factor.net/config

We can use https://github.com/luggit/react-native-config this library for that

Version 2.0

Stacktrace

Reason

SIGABRT

Link to App Center

• https://appcenter.ms/orgs/eSteem/apps/eSteem-iOS/Crashes/Groups/2f81bf780c4195c6c93c86342664de1fbd5c86d8

Version 2.0

Stacktrace

Reason

SIGABRT

Link to App Center

• https://appcenter.ms/orgs/eSteem/apps/eSteem-iOS/Crashes/Groups/0b958a7e7f5c9424935d8ad3c290d2aad185bd31

Obviously most of them will be just navigation to specific page (home, profile, wallet, notifications pages) but one Submit Story.

When user tap and hold Submit story button, it will show small popover or slider to select type of content user wants to submit, by default it will be post

Shown only once for new users right after splash screen....

We have this on legacy Mobile and Surfer apps,
http://api.esteem.ws:8080/media/welcome.json

We should improve it if we get enough time before steemfest

We want to have switcher/component that can formulate transactions depending on authentication type: Steemconnect or Auth
This task is to start working on structure that will allow just that.

AC (acceptance criteria)

• Make sure steemconnect access_token stored and fetched properly (example Surfer)
• Have flag that indicates user logged in with steemconnect or ordinary auth.
• Have example of usage for simple operation vote for both cases

• first step the function call lookupAccount data coming as array
• then we are loking is includes the username then its turn boolean.
• if it turn true the state goes update to true but border color still red.

as per mockup prepare side menu for adding multiple accounts

AC

• make sure side menu design looks exact like mockup, coloring, spacing, etc.
• show added users list if there is more than 1 account logged in

https://app.zeplin.io/project/5b8e99a7a17775345311f7cc/screen/5bf5dceed0bcdb4d8f87cc6f

navigation.navigate('Main') instead navigation.navigate(ROUTES.SCREEN.MAIN);

therefor all screen manageable with a file.

• Post screen missing post title, add this
• Fix formatting of markdown
• Markdown parser improvements copy from (priority: Surfer and last check: Busy, Steemit as well)
• Improve styling of the page, add padding
• Post details, footer (votes, comments, reward, author, etc.)
• Reward details component to see pending reward, promoted amount, payment due time, etc.
• Voters info component/page to see who has voted, what percent, when, how much reward it was, etc. (see Surfer for more details)

Please use the loop for render per button.

create a function for rendering per item and render it according to numbers.

We can implement codepush library to project for easy update after release.